Re: PgUp/PgDown ! tree key shortcuts

On Tuesday, February 21, 2017 at 8:52:29 PM UTC-5, Edward K. Ream wrote: > > ​ > This would be a big project. I don't think it is worth doing now. I have > in mind a few baby steps, but even these don't seem all that important > compared to other possible projects. > > Agreed. I think once

Re: PgUp/PgDown ! tree key shortcuts

​​ On Tue, Feb 21, 2017 at 3:24 PM, john lunzer wrote: As Edward alluded to, keybindings feel complex. This is probably an area of > code that could use some eventual simplification and cleanup. > ​True, but much of the complexity is inherent.​ ​The fact that Leo uses Tk

Re: PgUp/PgDown ! tree key shortcuts

I usually use the quicksearch.py to quickly get an idea for where things are, activating the "Show Parents" option gives more context to the search results. I initially just used the search string "prior" and this gave me a ton of results, I looked through all of them and eventually I found

Re: New Qt geometry error

Here's the log window information from the offending PC: Leo 5.4, build 20170221043749, Tue Feb 21 04:37:49 CST 2017 Git repo info: branch = master, commit = f860468937d5 Python 3.4.3, PyQt version 5.4.1 Windows 8 AMD64 (build 6.2.9200) For some reason, it reports as Windows 8, but it's Windows

Re: PgUp/PgDown ! tree key shortcuts

On Tuesday, February 21, 2017 at 6:49:15 PM UTC, john lunzer wrote: > > I've set these key shortcuts: > > goto-next-n-visible ! tree = PageDn > goto-prev-n-visible ! tree = PageUp > > > Here is my @command goto-next-n-visible node: > > @language python > N=12 > > def getVisNextN(n): >

Re: can't get parse-body to do anything...

Hi Edward On Tuesday, February 21, 2017 at 5:37:10 PM UTC, Edward K. Ream wrote: > > On Tuesday, February 21, 2017 at 9:18:17 AM UTC-6, Edward K. Ream wrote: > > > parse-body should warn if @language python is not in effect. > > Done at dedcc73. Actually, parse-body warns if there is no parser

Re: New Qt geometry error

On Tue, Feb 21, 2017 at 11:07 AM, Largo84 wrote: > On another computer (Windows 7, Python 3.3.2, PyQt version 4.8.4), I > don't see this error message. The PC that has the error is Windows 10. They > may also have different PyQt installations, will have to check when I get >

Re: PgUp/PgDown ! tree key shortcuts

On Tue, Feb 21, 2017 at 12:49 PM, john lunzer wrote: Any ideas on why my new set of bindings is glitching? > ​Please file a bug report. Key bindings are mind-boggling. A good starting point is to assume there is a bug somewhere. Edward -- You received this message because

Re: can't get parse-body to do anything...

On Tue, Feb 21, 2017 at 11:37 AM, Edward K. Ream wrote: At present, parse-body will crash if the to-be-parsed node contains > children: > ​Rev 5f572d fixes this. parse-body will issue a message and do nothing when run on a node with children. This is the only thing to do,

PgUp/PgDown ! tree key shortcuts

I've set these key shortcuts: goto-next-n-visible ! tree = PageDn goto-prev-n-visible ! tree = PageUp Here is my @command goto-next-n-visible node: @language python N=12 def getVisNextN(n): current = c.p for ind in range(n): forward = current.getVisNext(c) if

Re: can't get parse-body to do anything...

On Tuesday, February 21, 2017 at 9:18:17 AM UTC-6, Edward K. Ream wrote: > parse-body should warn if @language python is not in effect. Done at dedcc73. Actually, parse-body warns if there is no parser for the present language. That is, parse-body will work for any language for which there is

Re: New Qt geometry error

On another computer (Windows 7, Python 3.3.2, PyQt version 4.8.4), I don't see this error message. The PC that has the error is Windows 10. They may also have different PyQt installations, will have to check when I get back home. Rob. On Tuesday, February 21, 2017 at 9:29:36 AM UTC-5,

Re: Marketing, features and newbies

I hope that pointing to other software with similar intents or features as inspiration looks more like "let's make Leo great again", instead of a "a lot veiled empty threats". I have never seen such vigorous discussion on other software on this list until recently and I think that's good for

Re: can't get parse-body to do anything...

On Tue, Feb 21, 2017 at 8:35 AM, john lunzer wrote: parse-body needs some way to tell it which lanugage it is parsing. The @lan > ​gu​ > age directive can be present in *any* parent, all the way up to a top > level node. > ​ First, there is clearly a bug here. Parse-body

Re: This may not be related to Leo, but just in case...

​​ On Tue, Feb 21, 2017 at 6:29 AM, Edward K. Ream wrote: Imo, Leo should open a web page only when it is clear that it is about > to do so. > ​Fixed at 48cb76b. From the checkin log: QQQ Fixed a horrible bug in g.handleUrl that opened a file browser by mistake. All

Re: can't get parse-body to do anything...

parse-body needs some way to tell it which lanugage it is parsing. The @lanugage directive can be present in *any* parent, all the way up to a top level node. My guess is that in your previous attempt when it worked there was a @language directive hiding somewhere. This probably needs to be

Re: New Qt geometry error

The message comes up in the terminal window before any of the tabs open. Subsequent resizing of the windows doesn't trigger the warning. HTH Rob On Monday, February 20, 2017 at 5:00:43 PM UTC-5, Edward K. Ream wrote: > > On Mon, Feb 20, 2017 at 2:32 PM, Largo84 >

Re: can't get parse-body to do anything...

Hi John On Tuesday, February 21, 2017 at 1:01:26 PM UTC, john lunzer wrote: > > I tried this code too. Once without @language python, in which it failed, > and once with @language python, in which it was successful. So please > make sure that this directive is included in a parent of the branch

Re: can't get parse-body to do anything...

I tried this code too. Once without @language python, in which it failed, and once with @language python, in which it was successful. So please make sure that this directive is included in a parent of the branch you're trying to parse-body on. On Tuesday, February 21, 2017 at 6:05:12 AM UTC-5,

Re: This may not be related to Leo, but just in case...

On Tue, Feb 21, 2017 at 6:29 AM, Edward K. Ream wrote: This is weird enough that I want to single-step through > copy_to_my_settings. I put g.pdb() just after g.es(unl). > ​Er, actually, I put the g.pdb() in ​SF.find_setting, which contains the offending call to

Re: FreeMind and MindJet imports ready for testing

Freemind 1.0.1 Invalid FreeMind file a.mm.html Please ref attachment file a.mm.html. Could you help me how to import freemind file? Thanks! 在 2016年5月4日星期三 UTC+8下午6:20:39，Edward K. Ream写道： > > This completes #32

Re: This may not be related to Leo, but just in case...

​​ ​​ On Mon, Feb 20, 2017 at 9:03 PM, tscv11 wrote: First I must say that I am a big fan of Leo! Before this happened I used it > for python (and reST, of course), HTML, CSS, Asciidoc, and Markdown. > ​Thanks. This is clearly a problem in Leo. Imo, Leo should open a web

This may not be related to Leo, but just in case...

First I must say that I am a big fan of Leo! Before this happened I used it for python (and reST, of course), HTML, CSS, Asciidoc, and Markdown. Unfortunately I now need to report a bizarre issue that's been coming up repeatedly. After trying all available installer/setup packages and then

Re: Marketing, features and newbies

On Mon, Feb 20, 2017 at 8:03 PM, john lunzer wrote: I think every time we have one of these impromptu "let's make Leo great > again" brainstorming sessions I think the core users (which are represented > on these forums) are end up being really hard on Leo (and by proxy you >

New: reload-settings and reload-all-settings (including abbreviations!)

Rev f86046893 adds two important commands: reload-settings and reload-all-settings. The first reloads settings in the present outline, the second reloads settings in all tabs. This completes #340, Enhancement: reload-abbreviations . Please

Re: can't get parse-body to do anything...

Hi Edward On Tuesday, February 21, 2017 at 10:46:03 AM UTC, Edward K. Ream wrote: > > On Tue, Feb 21, 2017 at 3:39 AM, jkn > wrote: > > >> ​[I tried this code...]​ >> >> >> ''' Test parse-body command ''' >> >> class MyFirstClass(): >> def __init__(self): >>

Re: can't get parse-body to do anything...

On Tue, Feb 21, 2017 at 3:39 AM, jkn wrote: > ​[I tried this code...]​ > > > ''' Test parse-body command ''' > > class MyFirstClass(): > def __init__(self): > pass > > def newFunc(self): > pass > > class MySecondClass(): > def __init__(self):

Re: can't get parse-body to do anything...

Hi Edward On Monday, February 20, 2017 at 10:02:37 PM UTC, Edward K. Ream wrote: > > ​​ > On Mon, Feb 20, 2017 at 2:43 PM, jkn > wrote: > ​ > ​> ​ > I cannot get > ​[parse-body to do] anything! > > ​The body pane must contain classes or functions. > > Edward > Well,