Re: Please hold all commits to master

On Mon, Feb 26, 2018 at 8:12 PM, Matt Wilkie wrote: > > Oops. I just pushed 9500ea9ba694041e368f8a320bc13d04fa628351. It is a doc > update about the new commands for launching Leo after installing with pip. > It should be harmless? > ​Thanks for this. It is a much needed

Re: Matt, how do I review your docs?

On Mon, Feb 26, 2018 at 8:18 PM, Matt Wilkie wrote: > > What is the status of your install-docs branches? >> > > I believe these branches have now past their best-before date and it's > time to turn them into compost. If you have no further use for them I'll > delete them now?

Re: Matt, how do I review your docs?

> What is the status of your install-docs branches? > I believe these branches have now past their best-before date and it's time to turn them into compost. If you have no further use for them I'll delete them now? Matt -- You received this message because you are subscribed to the Google

Re: Please hold all commits to master

> I shall be releasing Leo 5.7 today or tomorrow. Until then, please commit > nothing to the master branch. > Oops. I just pushed 9500ea9ba694041e368f8a320bc13d04fa628351. It is a doc update about the new commands for launching Leo after installing with pip. It should be harmless? matt --

Re: Leo 5.7b2 on PyPi - please test

Thanks for the testing Lewis and Viktor! I'm gratified the only evident problem is missing documentation. The only *small* surprise on my side was that 'leoc.exe' is no longer > available. > - leo - Leo with default graphical interface - leo-c, leo-console - Leo with console interface

Re: Tip: using match-brackets effectively

On Mon, Feb 26, 2018 at 1:28 PM, Terry Brown wrote: Took longer than I anticipated, but I've just changed the way the > match-brackets command works :-) On the 5.8-dev branch ;-) > > Previously it looked either side of the insert point for a bracket, and > acted on that

Re: Tip: using match-brackets effectively

On Mon, 26 Feb 2018 07:00:20 -0800 (PST) "Edward K. Ream" wrote: > Leo's match-brackets command is an essential tool when trying to make > sense of javascript files. Took longer than I anticipated, but I've just changed the way the match-brackets command works :-) On the

Tip: using match-brackets effectively

Leo's match-brackets command is an essential tool when trying to make sense of javascript files. Here are two tips relating to this command. 1. Bind a keystroke to match-brackets. I use Ctrl-comma. It's too clumsy to use Ctrl-P, repeat-complex command. 2. Executing match-brackets *twice*

Tip: don't do repetitious things

For me at least, it's really easy to do more work than necessary during development, when just a bit of forethought would have paid off handsomely. For example, I recently tweaked the clean_headline method for the javascript importer. Here is a list of my mistakes: *Mistake 1:* Thinking that

Two great git documentation pages

I stumbled across these today. Imo they should be much more widely known: Every day git . `git help everyday` shows this page. Describes daily work flows for various kinds of git users/admins. Git tips repo . A long list of

Add branch.md to .gitignore?

It's too late to do anything like this for Leo 5.7. An ongoing irritation: GitHub's branch pages shows *only* the readme.md file, but this is a *global* file, not a branch-specific file. This means there are problems merging. See the discussion here

Re: how to run a script when Leo starts

On Sun, Feb 25, 2018 at 11:38 AM, Phil wrote: Actually, the security risk would be higher if a Leo file could turn on > @script by itself. > ​Happily, it can't. Only myLeoSettings.leo can set @bool scripting-at-script-nodes = True Security concerns exist for *any*

Re: how to run a script when Leo starts

On Sun, Feb 25, 2018 at 10:45 AM, Phil wrote: ​> ​ it would appear that there could be an outline-local version of the flag, so that the global flag in myLeoSettings.leo could be set to False for default behavior. There would still be a security risk for a specific Leo

Please hold all commits to master

I shall be releasing Leo 5.7 today or tomorrow. Until then, please commit nothing to the master branch. The 5.8-dev and proto branches remain open. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop