On Tue, Sep 3, 2019 at 7:33 PM Robert Cholette <[email protected]> wrote:
(in case someone's trying some kind of vscode integration) > Just a note about 'force open' a particular file when writing a vscode > extension: I just spent time reading about vsCode's definition and > behaviour of what it considers a 'workspace', and also, a project's root > folder. > > Turns out that by default, they are the same, the root folder you've > opened, lets say a project's folder, is what it considers its workspace and > that there can only be one workspace at a time in an opened instance of > vscode. > > But most importantly, when [the workspace is] changed it *restarts* all > extensions! oops! Goes to show i'm pretty new to vscode! > Thanks for this. There is no substitute for experience. 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/CAMF8tS1UdGXkbZgTd4Lu8EGmB-hKhXYj-UcrA86cZp-YJRrwiA%40mail.gmail.com.
