heh - see from a closer reading of the code and
https://github.com/leo-editor/leo-editor/pull/3264 that
${ENVNAME} should already be supported, via os.path.expandvars().
I'm still having a little trouble getting the new form(s) to work as I
expect,
i will experiment a bit more and report back.
On Tuesday, January 9, 2024 at 7:14:33 PM UTC jkn wrote:
> did the work that got done here ever get documented? I am looking at some
> nodes with old-style path expressions and I am a bit confused what the
> current state of the art is.
> Path expressions don't seem to be discussed in the current documentation.
>
> FWIW, in relation to the posting above this, I would suggest that
> ${ENVNAME} works in a similar way to $ENVNAME - like in bash scripts, for
> instance.
>
> Happy New Year!
> Jon N
>
>
> On Sunday, April 9, 2023 at 12:46:47 AM UTC+1 Edward K. Ream wrote:
>
>> On Saturday, April 8, 2023 at 5:52:20 PM UTC-5 tbp1...@gmail.com wrote:
>>
>> Excellent! And if Leo were to export, say, LEODIR, which would be the
>> *leo* directory, then there would not be a need for {leoDir} since one
>> could write something like
>>
>> @file $LEODIR/themes/vr3/rst-dark.css
>>
>> I like it.
>>
>>
>> So do I. The new code will be ready later this evening.
>>
>> 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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/leo-editor/ac9560f5-315b-4b47-9099-ff22b2d0df8dn%40googlegroups.com.
