I don't know if you got around to thinking about it yet (you've got so much 
else going on!), but the command I wrote to run external files is in 
LeoPyRef and it's called *execute-external-file*.  It has some trickiness 
because it has to run on Linux as well as Windows, and the terminal 
commands to launch programs differ among the distros. The code has to try 
some empirical hacks to figure it all out. But it ought to port to TS 
pretty easily, I would think.

On Saturday, March 9, 2024 at 9:46:57 PM UTC-5 Félix wrote:

> I'm still working on this! Thanks for your patience :) 
>   
> (The latest LeoJS 0.2.12 release is the result of trying to capture many 
> features for that video tutorial, and realizing that they needed a bit of 
> polishing!)
>
> Félix
>
> On Wednesday, January 3, 2024 at 7:18:33 PM UTC-5 [email protected] wrote:
>
>> Yay!
>>
>> On Wednesday, January 3, 2024 at 7:12:26 PM UTC-5 Félix wrote:
>>
>>> I'm going to take a coding break by doing a tutorial exactly about that!
>>>
>>> On Wednesday, January 3, 2024 at 4:56:12 PM UTC-5 [email protected] 
>>> wrote:
>>>
>>>> Now That leoJS is getting into pretty good shape - and Felix must need 
>>>> a month's vacation! - I am thinking about plugins and scripts that can do 
>>>> things that are easy to do from within Leo. Specifically, scripts that can 
>>>> read and write files from the file system, and files that do the 
>>>> equivalent 
>>>> of subprocess.run() or subprocess.Popen().  In addition (or maybe it's in 
>>>> the same group), scripts that launch a web browser on a specified file.
>>>>
>>>> Is there somewhere we can read up on these things, that is, how a leoJS 
>>>> script can do them in javascript/typescript?
>>>>
>>>

-- 
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/1d5176ef-3bc9-4175-97e5-7bc8f5606da2n%40googlegroups.com.

Reply via email to