That worked great, thanks.
Today was the day I decided to rip out myLeoSettings.leo and allow the
latest version to create a new one for me. I started by enabling the
plugins I had enabled with the old settings file, which included a
seriously edited version of @data qt-gui-plugin-style-sheet.
On Sun, Sep 21, 2014 at 6:42 PM, Edward K. Ream wrote:
> pylint originally flagged the statement "fg = Qt.black". The only
> recent change was to disable the pylint warning. It looks like that
> was bogus.
Fixed (with real code, not by messing with pylint) at rev 026bd86.
Tested the changed s
Hello to everybody.
Sorry for my limited English.
Today is my most important question:
Is there a way now to have / get a version of Leo in German language, a
localization one's?
If yes, how is the way to get it?
Xoogle would not help in this.
If you can do,
that would be great and ver
On Sun, Sep 21, 2014 at 6:16 PM, Chris George wrote:
> The latest rev nets me this with a default myLeoSettings.leo file. The only
> change I have made is to enable the following plugins:
> backlink.py
> hook failed: after-create-leo-frame, ,
> leo.plugins.backlink
[snip]
> File "/home/chris/Wo
The latest rev nets me this with a default myLeoSettings.leo file. The only
change I have made is to enable the following plugins:
backlink.py
nodetags.py
plugins_menu.py
contextmenu.py
nodewatch.py
leo_to_html.py
mod_scripting.py
quicksearch.py
viewrendered2.py
markup_inline.py
bibtex.py
bookmark
On Thursday, September 18, 2014 9:05:48 AM UTC-5, Edward K. Ream wrote:
> Several recent revs today have updated about 20 plugins.
I have continued to update plugins for the last several days. As of today,
all plugins pass pylint without complaints (some checks are disabled).
Rev ce43a43 moved
On Sat, 20 Sep 2014 23:25:33 -0700 (PDT)
lewis wrote:
> Hi Edward,
>
> A minor improvement would be useful to ensure after a Ctrl-F the
> focus always lands in the field.
> Open cheatsheet.leo , Ctrl-F, focus correctly lands in the pattern
> here> field
> But when I open LeoDocs.leo or quicks
This plugin used ancient coding technology, created menu items instead of
minibuffer commands, did not report progress and was probably not thread
safe.
All these defects have now been remedied. It could be quite useful in some
situations.
For example, suppose node P has this body text::
Just to sum up, in case Edward ends up jumping to the pool and swims inside
the "find code", the other recent issue that we talked about would be fixed
if this were to happen:
- The user press "enter" inside the text input =>> this
should unconditionally be equivalent to doing a new search, wit
