![]() ![]() 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. Once connected to a server, you can interact with files and folders anywhere on the remote filesystem. 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. The Visual Studio Code Remote - SSH extension allows you to open a remote folder on any remote machine, virtual machine, or container with a running SSH server and take full advantage of VS Code's feature set. 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.Here you can see that the Java extension is using SymbolTag.Deprecated to show source code that references deprecated types or members with a strike-through line. Open terminal in custom working directory - Add keyboard shortcuts for specific folders. being able to launch code -term for example (see Extract the integrated terminal #34442 (comment) for details) See what is new in the Visual Studio Code September 2019 Release (1.39). dont launch R by typing R from a terminal prompt in VS Code. This issue is tracking making the terminal "stand alone", ie. Ive only used VS Code for a short time so am not an expert, but here is a quick summary.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 |