On Mon, Sep 15, 2014 at 2:15 AM, Matt Wilkie map...@gmail.com wrote:
My two:
(a) Drag and drop target is smaller than the visual cursor indicates. Only
existing nodes in the tree are targets, however the whole tree panel uses
the [+] indicator. (this part is a bug) Suggestion: when a file is
On Mon, Sep 15, 2014 at 1:08 PM, Fidel N fidelpe...@gmail.com wrote:
Hi, just retested with latest Leo, and still get the same bug.
In future, please send text tracebacks, not pictures.
Rev a616add, Leo build: 20140919061341 appears to fix this bug.
It works for me on Windows and Ubuntu.
On Mon, Sep 15, 2014 at 1:27 PM, Fidel N fidelpe...@gmail.com wrote:
In the Find tab, check the suboutline only
Select an outline, and search for any text on its subtree, for instance a.
This outline shouldnt have a within its text.
Now select another outline (that should have a within its
Hi Edward
selfishly, I'd be keen for my wishlist bug
ability to specify numeric keypad keys in bindings
to be looked at:
https://bugs.launchpad.net/leo-editor/+bug/1207421
(though I appreciate it might be a pain...). Shall I migrate it to github?
Cheers, Jon N
--
You received this
Edward, I send pictures when copy/paste is not allowed, since the reports
happen on the un-responsive console that appears in Windows when I open leo
from a .bat file.
Is there a way to copy that text??
Just updated from a very recent version and this Leo version has something
wrong with the
On 9/19/2014 10:04 AM, Fidel N wrote:
Edward, I send pictures when copy/paste is not allowed, since the
reports happen on the un-responsive console that appears in Windows
when I open leo from a .bat file.
Is there a way to copy that text??
It's well hidden, but yes:
On Fri, 19 Sep 2014 06:21:25 -0500
Edward K. Ream edream...@gmail.com wrote:
But I disable some truly weird code at the end of lqlw.tab_callback:
setting the c.k.autoCompleter.klass ivar.
Is it anything to do with @bool use_qcompleter = True ?
Probably not - I know there was a launchpad bug
On Wednesday, September 17, 2014 3:03:27 PM UTC-5, Fidel N wrote:
it works great here, thanks for this Edward
Oops. It appears to be impossible to cut or delete text from large nodes.
It's on my urgent list, but in the meantime I recommend setting::
@int max-pre-loaded-body-chars = 0
lol thanks Jake, next time it will be text hehe. Its way more comfortable
to share on this side too!
On Fri, Sep 19, 2014 at 4:15 PM, Jacob Peck gatesph...@gmail.com wrote:
On 9/19/2014 10:04 AM, Fidel N wrote:
Edward, I send pictures when copy/paste is not allowed, since the
reports happen
On Fri, Sep 19, 2014 at 9:15 AM, Jacob Peck gatesph...@gmail.com wrote:
Not sure why Microsoft in their infinite wisdom decided that the console
wouldn't ever have a valuable bit of text to copy...
It's easy to copy text from a console: Alt-space e s return
Every Windows programmer should be
On Fri, Sep 19, 2014 at 9:25 AM, 'Terry Brown' via leo-editor
leo-editor@googlegroups.com wrote:
Is it anything to do with @bool use_qcompleter = True ?
That's my default assumption. Having said that, I have not yet been
able to reproduce the bug.
Edward
--
You received this message because
On Fri, 19 Sep 2014 10:30:57 -0500
Edward K. Ream edream...@gmail.com wrote:
On Fri, Sep 19, 2014 at 9:25 AM, 'Terry Brown' via leo-editor
leo-editor@googlegroups.com wrote:
Is it anything to do with @bool use_qcompleter = True ?
That's my default assumption. Having said that, I have
Hi,
Unfortunately I have an issue with delayed loading:
https://github.com/leo-editor/leo-editor/issues/58
and I could not disable it by:
@int max-pre-loaded-body-chars = 0
On Friday, September 19, 2014 6:05:47 PM UTC+3, Edward K. Ream wrote:
On Wednesday, September 17, 2014 3:03:27 PM
Edward, I also get, whenever I open a new Leo file (control+n), this
conveniently copied log from the windows console:
Could not parse stylesheet of widget 0x27db690
I guess we narrowed the options a bit :D
--
You received this message because you are subscribed to the Google Groups
On Fri, Sep 19, 2014 at 12:08 PM, Fidel N fidelpe...@gmail.com wrote:
Edward, I also get, whenever I open a new Leo file (control+n), this
conveniently copied log from the windows console:
Could not parse stylesheet of widget 0x27db690
I guess we narrowed the options a bit :D
Ctrl-N works
On Fri, Sep 19, 2014 at 11:02 AM, 'Terry Brown' via leo-editor
leo-editor@googlegroups.com wrote:
I didn't mean does the bug have anything to do with @bool
use_qcompleter = True, but does the weird klass code you found have
anything to do with @bool use_qcompleter = True, but I suspect not.
On Fri, Sep 19, 2014 at 8:48 AM, jkn jkn...@nicorp.f9.co.uk wrote:
Hi Edward
selfishly, I'd be keen for my wishlist bug
ability to specify numeric keypad keys in bindings
to be looked at:
https://bugs.launchpad.net/leo-editor/+bug/1207421
(though I appreciate it might be a
The focus goes to the log, but nothing is reported when I do
print-style-sheet
On Fri, Sep 19, 2014 at 9:14 PM, Edward K. Ream edream...@gmail.com wrote:
On Fri, Sep 19, 2014 at 12:08 PM, Fidel N fidelpe...@gmail.com wrote:
Edward, I also get, whenever I open a new Leo file (control+n), this
On Friday, September 19, 2014 10:05:47 AM UTC-5, Edward K. Ream wrote:
Oops. It appears to be impossible to cut or delete text from large nodes.
Fixed at rev 80e5693, Leo build: 20140919143910
The fix was simple, setting w.leo_big_text = None in two places, so perhaps
the code is solid now.
On Friday, September 12, 2014 10:34:14 AM UTC-5, Edward K. Ream wrote:
I plan to release Leo 5.0a1 in a week (more likely two) from today.
We can expect 3 to 5 releases, one per week, until 5.0 final, which means
that we can expect 5.0 final in late October. My, how time flies...
After a
I'm travelling right now, limited connectivity, will do best can now and
polish/extend later.
-matt
On Fri, Sep 19, 2014 at 4:02 AM, Edward K. Ream edream...@gmail.com wrote:
On Mon, Sep 15, 2014 at 2:15 AM, Matt Wilkie map...@gmail.com wrote:
My two:
(a) Drag and drop target is smaller
Just pushed a revamp of the large body text delayed load UI.
I intended to preserve two commits, one where I moved the UI stuff to a
class, and another where I manually applied the can't edit large body
text fixes in 80e5693, but I git gaffed and merged both commits into
master as one commit.
On Fri, Sep 19, 2014 at 5:06 PM, 'Terry Brown' via leo-editor
leo-editor@googlegroups.com wrote:
Just pushed a revamp of the large body text delayed load UI.
I think you forgot to add /qt_big_text.py
Edward
--
You received this message because you are subscribed to the Google Groups
On Fri, Sep 19, 2014 at 5:06 PM, 'Terry Brown' via leo-editor
leo-editor@googlegroups.com wrote:
I think the default value of @int max-pre-loaded-body-chars is probably too
low,
although I guess on a slow / heavily loaded machine it might need to be.
Happily, I have just set it to zero
On Fri, Sep 19, 2014 at 5:06 PM, 'Terry Brown' via leo-editor
leo-editor@googlegroups.com wrote:
Any response from Qt on that bug?
No. And even if there were a response, we are on our own until *all*
Leo users upgrade to a version of Qt that fixes it.
Clearly the bug exists. We don't need Qt
My expectation, after reading doc, and settings information in
leoSettings.leo,etc, is that after making sure that i have
@settings
@boot enable-abbreviations = True
@data abbreviations
stuff;;=stuffing
was that typing stuff;; would result in stuffing appearing where stuff;;
had
On Fri, Sep 19, 2014 at 2:28 PM, Fidel N fidelpe...@gmail.com wrote:
The focus goes to the log, but nothing is reported when I do
print-style-sheet
The command prints to the console. Please run Leo from a console and try again.
Edward
--
You received this message because you are subscribed
On Fri, 19 Sep 2014 17:17:17 -0500
Edward K. Ream edream...@gmail.com wrote:
On Fri, Sep 19, 2014 at 5:06 PM, 'Terry Brown' via leo-editor
leo-editor@googlegroups.com wrote:
Just pushed a revamp of the large body text delayed load UI.
I think you forgot to add /qt_big_text.py
Sheesh, so I
Just ran commit cdf3b9d59d74.
Here is the traceback:
Leo Log Window
Leo 4.11 final, build 20140919173856, Fri Sep 19 17:38:56 CDT 2014
Git repo info: branch = master, commit = cdf3b9d59d74
Python 3.4.1, PyQt version 4.8.6
Windows 7 AMD64 (build 6.1.7601) SP1
[snip]
reading settings in
On Fri, Sep 19, 2014 at 6:05 PM, lewis lewisn...@operamail.com wrote:
Just ran commit cdf3b9d59d74.
Here is the traceback:
Thanks for this. It's good to know somebody is using this plugin.
I'll fix it immediately.
Edward
--
You received this message because you are subscribed to the Google
On Fri, Sep 19, 2014 at 5:45 PM, 'Terry Brown' via leo-editor
leo-editor@googlegroups.com wrote:
Perhaps a higher value, like 5 would be better, so it won't kick in
in typical use (like it did for Zoltan), but might get between the user
and the data loss in the cases where the data loss
On Fri, Sep 19, 2014 at 6:16 PM, Edward K. Ream edream...@gmail.com wrote:
On Fri, Sep 19, 2014 at 6:05 PM, lewis lewisn...@operamail.com wrote:
Just ran commit cdf3b9d59d74.
Here is the traceback:
Fixed, I think, at rev 2647e83.
Edward
--
You received this message because you are
On Fri, 19 Sep 2014 14:34:38 -0700 (PDT)
bobS rjshanle...@gmail.com wrote:
My expectation, after reading doc, and settings information in
leoSettings.leo,etc, is that after making sure that i have
@settings
@boot enable-abbreviations = True
It's bool, not boot, short for boolean,
Thanks for the quick fix.
I know you aren't the author of bigdash plugin (Ville I think) but I've
just been reminded of some usability aspects of some plugins in Leo.
With leo running the only documentation in Leo is via Pluginsbigdash.py
which displays:
Leo.plugins.bigdash
Global search
Help-for-command provides the docstrings of alt-x commands, not the
plugins. So, /Alt-x global-search enter/ would give you the docstring
of global-search (if it had one defined).
Unfortunately, the docstrings are the only documentation for many (all?)
plugins, so the plugin authors really
35 matches
Mail list logo
