how to run a script when Leo starts

I want a script to run every time I start Leo. How can I do this? Thanks, Phil -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: Cleaning imported javascript headlines

many (most?) problems with imports can be fixed by hand in the generated > @clean tree. Yes, I am aware of this. But it turned out quite often for me that amount of work needed for that manual fixing exceeds the amount of work needed to split file by hand in the first place. I would not

Re: @rclick in myLeoSettings.leo not generating commands in work files

On Fri, Feb 23, 2018 at 9:59 AM, Kent Tenney wrote: > @rclick buttons defined in myLeoSettings.leo work fine in work files, > and <@rclick command name> works fine in the myLeoSettings.leo > file, but in the work files, <@rclick command name> is unknown. > > Before

Re: How did I came across Leo?

On Fri, Feb 23, 2018 at 11:35 AM, Offray Vladimir Luna Cárdenas < off...@riseup.net> wrote: ​> ​ So, my path was Python -> Zope -> Leo -> Outlining for Literate Programming -> Writing -> Pharo, Roassal -> Reproducible research and data storytelling and visualization -> Grafoscopio. ​It's been

Re: Cleaning imported javascript headlines

On Friday, February 23, 2018 at 10:22:55 AM UTC-6, vitalije wrote: Cleaning generated headlines is just a part of the problem. More serious > problem is choosing what should go in to single node. > I agree completely. > As far as I am concerned, I would much prefer to have a toolbox with >

Re: How did I came across Leo?

Hi, I came about Leo because I was interested in Learning Python and some forum said that Leo, not Zope, was a superb showcase for this language and then I found that it supported a form of literate programming, which I was already interesting into. I started to use it almost exclusively for

Re: Cleaning imported javascript headlines

There are problems assigning lines to nodes. > > Edward > Precisely -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com.

Re: Cleaning imported javascript headlines

On Friday, February 23, 2018 at 10:32:59 AM UTC-6, Edward K. Ream wrote: I am working on improvements [to . Please hold suggestions for a bit. > Rev 0deba52 completes the present round of work on this project. There are no problems that I can see with the *headlines* when importing leovue/src.

Re: Joe, building LeoVue fails for me on Windows and Ubuntu

OT: Critical Linux filesystem permissions are being changed by latest version · Issue #19883 · npm/npm https://github.com/npm/npm/issues/19883 god bless NPM user On Tue, Feb 20, 2018 at 6:56 AM, Edward K. Ream wrote: > On Monday, February 19, 2018 at 11:42:11 AM UTC-6,

Re: Cleaning imported javascript headlines

On Friday, February 23, 2018 at 9:42:24 AM UTC-6, Edward K. Ream wrote: > The javascript importer now defines [clean_headline] this way: I am working on improvements. Please hold suggestions for a bit. Edward -- You received this message because you are subscribed to the Google Groups

Re: Cleaning imported javascript headlines

Cleaning generated headlines is just a part of the problem. More serious problem is choosing what should go in to single node. As far as I am concerned, I would much prefer to have a toolbox with several commands to help me importing files on my own. I wrote about that idea here

@rclick in myLeoSettings.leo not generating commands in work files

@rclick buttons defined in myLeoSettings.leo work fine in work files, and <@rclick command name> works fine in the myLeoSettings.leo file, but in the work files, <@rclick command name> is unknown. Before submitting a bug/enhancement request, can anyone else comment on whether they also see

Cleaning imported javascript headlines

Leo's import system has many strengths. The most important is that code will almost always import correctly even if the resulting nodes aren't even close to optimal. This is particularly important for javascript, where coding styles vary so widely. After generating nodes, the import system

Re: ENB: Serious doubts about embedding Leo

On Friday, February 23, 2018 at 3:37:32 AM UTC-6, Edward K. Ream wrote: > leoBridge.py is a small module, but it has generated continuing and difficult issues. Vitalije has just fixed multiple issues, including two issues related to the leo bridge: #716: LeoBridge not explicitly closing the

Re: ENB: Serious doubts about embedding Leo

On Friday, February 23, 2018 at 4:05:36 AM UTC-6, Zoom.Quiet wrote: > WoW soo quickly conform these points ;- just 2 week, EKR rebuild IDE world idea, Sayeahoo! Hehe. Two weeks of prototyping, building and playing with other editors is a small price to pay for a wider view of the world.

Re: ENB: Serious doubts about embedding Leo

On Fri, Feb 23, 2018 at 6:05 PM, Zoom.Quiet wrote: > On Fri, Feb 23, 2018 at 5:37 PM, Edward K. Ream > wrote: > >> The process of *considering* embedding Leo in another IDE has been one >> of the most useful things I have ever done. I feel as if I

Re: ENB: Serious doubts about embedding Leo

On Fri, Feb 23, 2018 at 5:37 PM, Edward K. Ream wrote: > The process of *considering* embedding Leo in another IDE has been one of > the most useful things I have ever done. I feel as if I have awoken from a > deep slumber. Atom, VSCode, eric6 and Pycharm/Intellij are all

ENB: Serious doubts about embedding Leo

The process of *considering* embedding Leo in another IDE has been one of the most useful things I have ever done. I feel as if I have awoken from a deep slumber. Atom, VSCode, eric6 and Pycharm/Intellij are all superb tools. Building and using them, even briefly, has been eye opening. But