Re: rev b0f5e55 adds support for command history

On Sunday, November 9, 2014 9:12:34 PM UTC-6, Matt Wilkie wrote: > > yay! thank you Edward :) > You're welcome. It was good to add something new after futzing with so many bugs :-) Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsu

re bug 1292207: Disabling Plugins disables menu actions

https://bugs.launchpad.net/leo-editor/+bug/1292207 This bug is invalid. Disabling plugins disable the mod_scripting plugin, so the @command nodes given in the example do nothing. HTH. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To u

Re: rev b0f5e55 adds support for command history

yay! thank you Edward :) On Sun, Nov 9, 2014 at 4:42 AM, Edward K. Ream wrote: > After Alt-x puts you in the minibuffer, you can now use UpArrow and > DownArrow keys to cycle through previous "complex" commands, that is, > commands entered via Alt-x. > > For example, Alt-x UpArrow is roughly equ

Re bug 1286909: Settings in file A propogate to file B when editing A and B is opened

https://bugs.launchpad.net/leo-editor/+bug/1286909 Again, this is more of a request for help than a bug. > When I'm editing Leo-Editor file A and I open Leo-Editor file B, it seems wrong that the settings in file A affect the editing of file B. It may seem wrong, but this is the way Leo works a

Re: Re bug 1286914 A custom menu that seems correct, but does nothing

On Sunday, November 9, 2014 8:58:35 PM UTC-6, Edward K. Ream wrote: I forgot the link to the original bug report: https://bugs.launchpad.net/leo-editor/+bug/1286914 -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group

Re bug 1286914 A custom menu that seems correct, but does nothing

This is an old, old bug. It might have gotten my attention sooner if it was a request for help instead. But likely not. In any case, the custom menu in settingsCreep01.leo isn't correct. I'm not sure that Leo could give an error in such situations, and I have no interest in doing so. The pr

Advices for a newbie who want to turn Leo flexibility to the simplest Sphinx editor

Hi, I'm starting python programming for few months and just beginning to use Leo. I first got attracted by Leo for its way to handle ReST documents structure (just perfect!) and live preview. Then, I was quite disturb and very surprised by its level of complexity, (so many "hidden" implemented

Advices for a leo cub - Want to turn Leo into basic Sphinx editor

Hi, I'm starting python programming for few months and just beginning to use Leo. I first got attracted by Leo for its way to handle ReST documents structure (just perfect!) and live preview. Then, I was quite disturb and very surprised by its level of complexity, (so many "hidden" implemented

Re: GTD checkin messages and workflow

On Sun, 9 Nov 2014 05:05:58 -0800 (PST) "Edward K. Ream" wrote: [snip] > And here is a surprisingly useful workflow tip related to GTD. This > will be prewriting for a FAQ entry. > > You may have noticed that ideas "intrude" while you are busy with > something else. When that happens to me, I

Rev 1f1a110: fixed ancient open-with bug: be aware of settings

This bug has been around since early 2013 https://bugs.launchpad.net/leo-editor/+bug/1159490 It's embarrassing that I did not investigate until now. Strictly speaking, you could say it's invalid, but somehow many people became confused, so that's neither fair nor helpful. In any case, the sol

At last: how to make changes to the body pane persist

I have just added to the repo (but not yet on the web site) the following addition to the FAQ entry called:: Modifying the body pane directly QQQ **Important**: The changes you make below **will not persist** unless your script calls c.frame.body.onBodyChanged after making those changes. Th

GTD checkin messages and workflow

Starting now, the checkin log for commits involving the to-do list and project notes will start with GTD (Getting Things Done), and *maybe* some additional explanatory comments. You will have noticed that there have been *many* checkins re to-do and project notes recently. Imo, they are essent

Recent revs handle apostrophes properly during spell checking

Previously, when checking "didn't" the spell checker would complain that "didn" wasn't in the dictionary. Now it checks (and accepts) "didn't". We have all been putting up with this annoyance for *far* to long. Changing just two lines of code was all that was required. Sometimes I think the b

rev b0f5e55 adds support for command history

After Alt-x puts you in the minibuffer, you can now use UpArrow and DownArrow keys to cycle through previous "complex" commands, that is, commands entered via Alt-x. For example, Alt-x UpArrow is roughly equivalent to Ctrl-p. This completes one of the top four wishlist items at: https://github

Re: Leo 5.0 alpha 2 released to the wide world

On Sun, Nov 9, 2014 at 5:01 AM, Edward K. Ream wrote: > On Sun, Nov 9, 2014 at 4:42 AM, Edward K. Ream > wrote: > >> On Sat, Nov 8, 2014 at 8:19 PM, lewis wrote: >> >>> >>> Leo installs and opens workbook.leo by default but it won't open files >>> via Help>Open CheatSheet, LeoDocs or quickstart

Re: Leo 5.0 alpha 2 released to the wide world

On Sun, Nov 9, 2014 at 4:42 AM, Edward K. Ream wrote: > On Sat, Nov 8, 2014 at 8:19 PM, lewis wrote: > >> >> Leo installs and opens workbook.leo by default but it won't open files >> via Help>Open CheatSheet, LeoDocs or quickstart. >> Same result via File>Open C:\Program Files\Leo-5.0-a2\leo\doc

Re: Leo 5.0 alpha 2 released to the wide world

On Sat, Nov 8, 2014 at 8:19 PM, lewis wrote: > > Leo installs and opens workbook.leo by default but it won't open files via > Help>Open CheatSheet, LeoDocs or quickstart. > Same result via File>Open C:\Program Files\Leo-5.0-a2\leo\doc > Recent Files are there but they don't open. > There are no m