On Tue, Jul 14, 2020 at 6:21 PM Félix <[email protected]> wrote:
> Thank you for bringing up this issue Edward, You're welcome. I'm glad you're making progress on it. > ...vscode, itself, will *always* consider a .leo file a normal xml file, because well, that's what it is! So for vscode, the vanilla 'open file' concept will always be "open it as xml text in an editor". (Actually, I hope I'm wrong and that I can just plug my OpenLeoFile to replace the 'openFile' for .leo files! I'l revise the docs later to be sure.) This was the motivation for my suggestion to allow programmatic access to vs code's notion of a recent file. > nothing prevents us to define an 'openLeoFile command, taking a string parameter (path+filename string) and assiging this to a "right-click" context menu item to normal explorer files. (which is easy to do.) That openLeoFile(p_fileName) command can be reused as-is to open files that were opened when vscode was closed, etc... Sounds like a good plan. The svg preview plugin shows that opening and rendering can be done automatically when selecting a file in the explorer. leoInteg doesn't have to go this far :-) So much more things are possible, when trying to integrate opening '.leo' > files integration and automation, in regards to the action of actually > opening a leo file with leoInteg instead of opening as an xml text file. > Good to hear. > ...in conclusion there's many options to help and provide the user with the concept of opening files at startup, offering 'recent Leo files' list to instantly open files with a mouse click, etc. Thanks for the discussion. There seems to be no urgent need to ask the vs code devs for an enhancement to the vs code api. 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/CAMF8tS0ozxpCQdyPVJCH%3DsvdXLu2Vxp2gB2HVe1Uc%3DQ7oNkUmg%40mail.gmail.com.
