Re: Discuss: remove support for Leo's path expressions

I was thinking the same. After all, leointeg or leojs could parse headlines and do something with the results. What might make sense - both for security and for both Leo and leojs - would be to write a small number of methods that would be the only ones that could be used in path expression

Re: Discuss: remove support for Leo's path expressions

I just checked the path expressions in Leo's docs. Pretty cool feature i didn't even know existed. That being said, I don't see why vscode would not allow me to evaluate parts of those strings as expected by this feature, as I already have support of scripting , including offereing g, c, p etc.

Re: Discuss: remove support for Leo's path expressions

I'm a little conflicted about this suggestion. I haven't used path expressions much, but I did experiment with using them to work on both Linux and Windows, where the difference was more than just the meaning of "~". By "work", I mean that the same outline could be moved between Linux and Win

Discuss: remove support for Leo's path expressions

#3260 suggests removing support for Leo's path expressions by removing all calls to c.expand_path_expression in Leo's core and plugins. My reasons: 1. Path expressi

VR3 can now be opened in a tab

The VR3 plugin can now optionally open in a tab in the log pane instead of in its own panel in the main Leo window (also referred to as a pane in the splitter). I have attached a screen shot that shows the panel layout that I like when using VR3 in a tab. There are two new commands to control

Re: How To Install Leo Dependencies From a Git Clone

Keeping it up to date would be the question. On Friday, April 7, 2023 at 5:14:35 AM UTC-4 Edward K. Ream wrote: > On Thu, Apr 6, 2023 at 11:45 PM Thomas Passin wrote: > >> I just installed Python 3.11.3. I of course wanted to install Leo right >> away. I normally run Leo from my clone. With

Re: How To Install Leo Dependencies From a Git Clone

On Thu, Apr 6, 2023 at 11:45 PM Thomas Passin wrote: > I just installed Python 3.11.3. I of course wanted to install Leo right > away. I normally run Leo from my clone. With an ordinary requirements.txt > file one can install the requirements using pip -r requirements.txt. But > Leo uses a tr