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 syntax. As he mentions I would expect '/' to be workable everywhere, for example. Regards, J^n On Saturday, April 8, 2023 at 2:28:13 AM UTC+1 [email protected] wrote: > 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 Windows and the external files could be found. That's helpful for me > because I use so many Linux VMs, and I can't make many of the external > files work between Linux and Windows. One obstacle to my using them more > is that they are not very readable. > > There's no need to use {{sep}}-style steps because Leo wants to see > forward slashes in headlines and converts them as needed when running on > Windows. > > With regard to #2, 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.* I don't want to hear how I should be using > some other directory structure on Windows. My drive organization has some > 30 years of history behind it, going back to Windows 95, and I don't plan > to change it all now. If I had the experience then that I have now I would > probably have done it differently. Not that I have many external files > with adaptable file paths, but at least it can be done. > > One time this became a practical matter was a period of about 10 days when > I had to do without my Windows laptop. It seemed to be having memory > problems. I went to my backup machine - it ran Linux - moved my > Thunderbird email files over and some key Leo outlines. The email worked > great, but I had to be careful about handling external files I cared about > and wanted to work on. Of course I had backed up the laptop. > > On Friday, April 7, 2023 at 5:55:26 PM UTC-4 Edward K. Ream wrote: > >> #3260 <https://github.com/leo-editor/leo-editor/issues/3260> suggests >> removing >> support for Leo's path expressions >> <https://leo-editor.github.io/leo-editor/directives.html#path-expressions> >> by removing all calls to c.expand_path_expression in Leo's core and >> plugins. My reasons: >> >> 1. Path expressions are a serious security concern. >> 2. Path expressions are not necessary. There are easy workarounds. >> 3. vs-code will never allow such expressions. leoJS can not possibly >> ever support them. >> >> *Note*: c.expand_path_expression will still exist should someone need >> it. >> >> Your comments, please. >> >> Edward >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/57f662c1-2d85-4947-8aa1-2c049d0f3eb4n%40googlegroups.com.
