I'll be moving on with splitting soon which is kind of a prerequisite to this anyway, we wouldn't want a stand alone terminal that couldn't show more than one instance at once. I doubt I'll have the time to do this any time soon though. This would be useful to get some buy in and to show it's a compelling proposition. We could try put together a proof of concept in some branch which hacks together the terminal and necessary services, launching via code -term or something. Without that, it's hard to think of smaller steps we could take as everything is a pretty big task that might be throw away if the team doesn't like it. It would be a lot easier if something like this landed in Electron electron/electron#11501, that would allow sharing all the services across multiple windows. Tabs for integrated terminal #10546 tracks adding tabs to the terminal, combined with Allow for floating windows #10121 this would ideally allow terminal tabs to be pulled into a separate window.Allow for floating windows #10121 tracks being able to pull the terminal view/ panel out of the window.Is it possible to do a similar thing with SSH I.e., if I am SSHed into a remote host, is it possible to set things up so that running code file. From another StackOverflow answer, I learned that if you open an integrated terminal and find the VSCODEIPCHOOKCLI environment variable, and set it to the same value in the non-integrated terminal, then run code from the code server install directory /.vscode-server, it will work. being able to launch code -term for example (see Extract the integrated terminal #34442 (comment) for details) Something I love about VS Code is that when I am using a terminal in WSL, I can run code file.txt, and it will open that file with VS Code on my local using the WSL remote extension. This issue is tracking making the terminal "stand alone", ie.Both could be able to leverage a common configuration so that whether a terminal leveraging such a theoretical common component is spawned within VScode or standalone, they behave the same.Įdit from is some confusion about the scope of this issue, here is the clarification as the thread is long: Obviously if such a situation were to unfold, the shared component (not entirely dissimilar to VTE) should be jointly developed and shared with VScode. I'm only a casual VScode user (using vim most of the time), but I would definitely be interested in a well-behaved, consistent, reactively-configurable, multi-platform terminal not tied to the editor. The integrated terminal grows in functionality, to the point that it could soon become very useful standalone, as its own app.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |