Hello Edward,
is there a specific reason that the plugin 'leoOPML.py' exists/ is
referenced twice in the sources? - Once in leoOPML.leo and a
second time in leoPluginsRef.leo ...
With kind regards,
Viktor
--
You received this message because you are subscribed to the Google Groups
leo-editor
Leo's core uses c.config.getX to get almost all settings. This is as
it should be: such settings include those in the local file, the
file being loaded.
In contrast, Leo's core (and the mod_http plugin) use
g.app.config.getX to get *global* settings. Global settings include
only settings in
On Sat, Feb 25, 2012 at 2:15 AM, Viktor Ransmayr
viktor.ransm...@gmail.com wrote:
Hello Edward,
is there a specific reason that the plugin 'leoOPML.py' exists/ is
referenced twice in the sources? - Once in leoOPML.leo and a
second time in leoPluginsRef.leo ...
I don't see it anywhere in
I have been using the clone-find-all command frequently as I refactor
the code. The present operation includes nodes only once: if a
node's ancestor appears in the list, the node is not include again in
the top-level list.
Some may prefer this way of working, but there are times when I find
it
Can i change global settings in random .leo file?
On 25.2.2012 11:21 Edward K. Ream wrote:
Leo's core uses c.config.getX to get almost all settings. This is as
it should be: such settings include those in the local file, the
file being loaded.
In contrast, Leo's core (and the mod_http plugin)
On Sat, Feb 25, 2012 at 3:54 AM, vivai...@gmail.com wrote:
Can i change global settings in random .leo file?
Yes, if you really want to. In the new config world,
lm.globalSettingsDict and lm.globalShortcutsDict are all you would
need to change. The entries of lm.globalSettingsDicts are
I was thinking the oberall conceptual problem, do users of leo know what
settings are global?
Typically, settings for normal apps out there are always global. In ides etc,
exception are 'project settings' (e.g. Build directory), but in leo these kinds
of settings are mostly local key bindings,
Hello Edward,
On 25 Feb., 10:24, Edward K. Ream edream...@gmail.com wrote:
On Sat, Feb 25, 2012 at 2:15 AM, Viktor Ransmayr
viktor.ransm...@gmail.com wrote:
Hello Edward,
is there a specific reason that the plugin 'leoOPML.py' exists/ is
referenced twice in the sources? - Once in
Hello Edward,
On 25 Feb., 20:42, Viktor Ransmayr viktor.ransm...@gmail.com wrote:
Hello Edward,
On 25 Feb., 10:24, Edward K. Ream edream...@gmail.com wrote:
On Sat, Feb 25, 2012 at 2:15 AM, Viktor Ransmayr
viktor.ransm...@gmail.com wrote:
Hello Edward,
is there a specific reason
Leo Log Window
Leo 4.9.1 devel, build 5016, 2012-02-25 18:01:01
Python 2.7.2, qt version 4.7.3
linux2
When running my 'session' script which opens a list of leo files::
exception executing script
Traceback (most recent call last):
Traceback (most recent call last):
File
Today's work fixed a recent reversion, and made some important
progress.
1. The ancient, and extremely annoying scrolling bug appears to have
been fixed in a very simple way. The culprit was the
setSelectionAreas method. This is supposed to just set the range of
selected text. In fact,
I've been coming across a few anomalies lately, but haven't reported them
since I've held off updating since mid-January or so, due to the major
reworking going on lately and their attendant cautionary postings here, and
the fact that my issues may well have been fixed in the meantime.
Would
Hello Edward
On 25 Feb., 20:55, Viktor Ransmayr viktor.ransm...@gmail.com wrote:
To be precise: In my environment ( rev. 5060) I see the following
references:
oops, yesterday was definitely not a good day. The revision number
should have been rev. 5016.
In order to ensure that I did not have
13 matches
Mail list logo
