Re: [textadept] Modifications to language modules

From: Robert <>
Date: Thu, 9 Jun 2011 10:23:44 +0200


On Wed, Jun 8, 2011 at 10:24 PM, mitchell <> wrote:

>> Changing _HOME to _USERHOME leads to not being able to do a simple 'hg
>> pull' to update and the name of user api/tags files needs to be
>> changed as well. (I actually use these additonal tag files).
> Really? I cloned a module, replaced all instances of _HOME with _USERHOME,
> removed the original "if lfs.attributes(_USERHOME...) then" for tags and
> api, made a change in the original module and committed it, and then pulled
> that module's changes into my modified module. Everything merged just fine.
> In my experience, hg is pretty good at merging changes with 'hg pull'.
> Resolving these conflicts manually should be pretty easy though since you're
> just keeping local path changes.

you're right, these are indeed quite only local changes that should
merge easily.

>> Some modules (like mine) are installed in _USERHOME, the official ones
>> and Brian's Javascript in _HOME. That confused me at least once :-),
>> probably others as well.
> There is no 'one size fits all' solution. Comfortable ta hackers can use
> _HOME and handle themselves just fine when updating to a new release so
> there is no need for them to write _USERHOME modules. The nature of ta is
> customization so it's not surprising that some might be necessary when
> adopting others' modules.
> I am not big on imposing module "standards", but I am big on documentation.
> Non-official modules should definately include some comments on how and
> where their module should be installed. For those writing _HOME modules,
> having _USERHOME paths commented out would probably be a good idea for other
> users who don't want to install in _HOME.

Thanks for looking into it. I understand your points, there is likely
no 'one size fits all' solution.

Received on Thu 09 Jun 2011 - 04:23:44 EDT

This archive was generated by hypermail 2.2.0 : Thu 08 Mar 2012 - 12:08:28 EST