vim.py and location of @enabled-plugins node

Ubuntu 8.10 revno 1387

The IPython plugin seems to behave inversely, it's ok if the
@enabled-plugins node mentioning it is in <cwd>/myLeoSettings.leo
not if in <config>/leoSettings.leo

The presence of @enabled-plugins in <cwd>/myLeoSettings.leo
prevents plugins enabled in <config>/leoSettings.leo from working

On Fri, Jan 9, 2009 at 7:07 AM, Kent Tenney <email address hidden> wrote:

>
> The presence of @enabled-plugins in <cwd>/myLeoSettings.leo
> prevents plugins enabled in <config>/leoSettings.leo from working

Correct. That is (mostly) by design.

Edward

On Sat, Jan 10, 2009 at 8:50 AM, Edward K. Ream <email address hidden> wrote:
> On Fri, Jan 9, 2009 at 7:07 AM, Kent Tenney <email address hidden> wrote:
>
>>
>> The presence of @enabled-plugins in <cwd>/myLeoSettings.leo
>> prevents plugins enabled in <config>/leoSettings.leo from working
>
>
> Correct. That is (mostly) by design.

This leaves me in the position of having to choose between
ipython.py working and vim.py working, since they each
need to be enabled in different locations.

I have yet to have both working at once.

I consider Leo's configurability to be it's greatest strength, but
I find myself spending lots of time fiddling with different combinations
trying to get things to work.

I know I've advocated always more flexibility, maybe the flexibility
has been pushed to the point of breaking, and flexibility needs to
take a back seat to simplicity and predictability.

>
> Edward
>
> --
> vim.py and location of @enabled-plugins node
> https://bugs.launchpad.net/bugs/314403
> You received this bug notification because you are a member of The Leo
> editor team, which is subscribed to leo-editor.
>
> Status in Leo: a programmer's editor and more: New
>
> Bug description:
> If the vim.py plugin is enabled via
> @settings -> @enabled-plugins
> which is in the main leoSettings.leo file, it works as expected.
>
> If it is enabled via <cwd>/myLeoSettings.leo, dclick on the node icon opens the node for
> editing, but upon save and exit the changes to not appear in Leo.
>
> There are other inconsistencies involving plugins and what config files
> contain @enabled-plugins nodes, hopefully fixing this bug will address them as well.
>

On Fri, Jan 9, 2009 at 9:08 AM, Kent Tenney <email address hidden> wrote:

>
> This leaves me in the position of having to choose between
> ipython.py working and vim.py working, since they each
> need to be enabled in different locations.

I don't know how you have gotten yourself into this mess. Why can't you
enable both in both locations?

I'm really not sure I can help. It seems to me you are asking for oodles of
trouble by having so many init files.

Would customizing with @if-platform help?

Edward

On Sat, Jan 10, 2009 at 9:31 AM, Edward K. Ream <email address hidden> wrote:
> On Fri, Jan 9, 2009 at 9:08 AM, Kent Tenney <email address hidden> wrote:
>
>>
>> This leaves me in the position of having to choose between
>> ipython.py working and vim.py working, since they each
>> need to be enabled in different locations.
>
>
> I don't know how you have gotten yourself into this mess.

I don't know either.

> Why can't you
> enable both in both locations?

What is your configuration which enables both the ipython and vim plugin?

>
> I'm really not sure I can help. It seems to me you are asking for oodles of
> trouble by having so many init files.

I want to have 2, the versioned <config>leoSettings.leo, and one which
lives in the directory which the Leo file is in.

Is this too much to ask?

>
> Would customizing with @if-platform help?
>
> Edward
>
> --
> vim.py and location of @enabled-plugins node
> https://bugs.launchpad.net/bugs/314403
> You received this bug notification because you are a member of The Leo
> editor team, which is subscribed to leo-editor.
>
> Status in Leo: a programmer's editor and more: New
>
> Bug description:
> If the vim.py plugin is enabled via
> @settings -> @enabled-plugins
> which is in the main leoSettings.leo file, it works as expected.
>
> If it is enabled via <cwd>/myLeoSettings.leo, dclick on the node icon opens the node for
> editing, but upon save and exit the changes to not appear in Leo.
>
> There are other inconsistencies involving plugins and what config files
> contain @enabled-plugins nodes, hopefully fixing this bug will address them as well.
>

The comments re @enabled-plugins nodes in leoSettings were out-of-date and highly misleading.

Kent and I suspect that this is the source of the confusion.

I'm going to close this bug.