Replies: 3 comments 3 replies
-
Converted to a discussion since this isn’t really an actionable issue report but a kind of collection of ideas My personal view is that trying to make Code’s Terminal plugin behave exactly like the Terminal app is probably not a great use of resources and would end up in either a lot of code duplication or complicating the Terminal app a lot to try to make it into some kind of library. It just doesn’t sound like a great thing to pursue. I think it would probably be more scalable to actually remove the Terminal plugin and instead build in better git and meson features which probably accomplishes what you’re actually using the plugin for anyways |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Another idea is to retain some sort of "Terminal" functionality by having a button that opens the current project in the Terminal app. It would be pretty simple implementation-wise, but might serve that want for "I want a button that opens a Terminal in this project", and would also hammer home the idea that our IDE is Code + Terminal, not just one or the other. This could be in addition to better Git, Meson, Flatpak, etc. support directly in Code itself. |
Beta Was this translation helpful? Give feedback.
-
Problem
I personally feel that it is annoying to have to switch between 2 different brain modes when I'm either using the Terminal app, or Code's terminal. It doesn't copy and paste the same way and doesn't have at least a toggle for that behaviour. The terminal widget also doesn't look too great, and apart from the colour scheme looks to be the VTE widget crammed in a box.
Proposal
I think that the actual behavour of the terminal should be the same as the Terminal app
It should:
And yes, I could just use Terminal but that doesn't integrate with a code editing workflow.
Beta Was this translation helpful? Give feedback.
All reactions