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

On Sat, Apr 8, 2023 at 5:33 AM jkn wrote: > I haven't looked at c.expand_path_expression, at least recently - it may > be too capable for its own good. But I would definitely want a way to > navigate to a given file under different environments, similar to Tom's > example. > > I could live with t

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

On Fri, Apr 7, 2023 at 9:10 PM Thomas Passin wrote: > 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 wo

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

On Fri, Apr 7, 2023 at 8:29 PM Félix wrote: 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. available in the scope of the running > scripts. Many years ago Pau

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

On Fri, Apr 7, 2023 at 8:28 PM Thomas Passin wrote: I'd like to know an easy workaround for *@file > c:\Tom\devel\leo\some-file.py* on Windows but, say, *@file > ~/Leo/outlines/some-file.py.* > Create an @button node that adjusts your @file nodes. Edward -- You received this message because

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

I haven't looked at c.expand_path_expression, at least recently - it may be too capable for its own good. But I would definitely want a way to navigate to a given file under different environments, similar to Tom's example. I could live with the headline having to be changed to accommodate a new

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