On Feb 15, 9:19 am, Edward K. Ream edream...@gmail.com wrote:
Again: this post will be of interest only to those with a deep
interest in Leo's implementation. Feel free to ignore.
Rev 4985 completes the first draft of the new_config code.
Init code will never be easy, but this new code is
On Tue, Feb 14, 2012 at 8:53 PM, Edward K. Ream edream...@gmail.com wrote:
Rev 4984 contains the new code that computes the global finalized
dicts. The code is pretty much as envisioned in the post: look for
the g.new_config switch if you are interested in the details.
Rev 4985 completes the
This post will be of interest only to those with a deep interest in
Leo's implementation. Feel free to ignore.
At present, Leo's configuration code is a wretched mess. You can see
several aspects of this mess by looking at g.app.config.get:
1. This g.app.config.get searches several weird and
I have no idea if this is relevant, but in looking over @settings recently,
I remembered the issue with plugins wherein it was difficult (impossible?)
to de-activate a plugin appearing in leoConfig/leoSettings.leo.@enabled-plugins
Was that ever resolved?
If not maybe instead of bare names in
On Tue, Feb 14, 2012 at 12:10 PM, Kent Tenney kten...@gmail.com wrote:
I have no idea if this is relevant, but in looking over @settings recently,
I remembered the issue with plugins wherein it was difficult (impossible?)
to de-activate a plugin appearing in
On Feb 14, 11:11 am, Edward K. Ream edream...@gmail.com wrote:
In another thread, I summarized the planned new process as follows:
QQQ
Rather than the baroque code in g.app.config.getX, each c.config
[object] will contain two finalized
settings dicts, one for shortcuts and one for all
