-
Notifications
You must be signed in to change notification settings - Fork 29.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Terminal Configuration #45326
Comments
I think that integrating my extension into VSC itself, and possibly making it more powerful, would certainly improve the lives of some people. But I would rather prefer if VSC took the opposite approach, instead of integrating extensions into core, write every non-core functionality as an extension. |
I agree 💯 that it should be done as an extension, but there seem to be a slight difference as to how things that are considered part of the "core experience" are treated, as opposed to other features. Another use case I thought of, is having terminals start with different values for environment variables. Using my example above, in the terminal for testing, I want |
I think this is a duplicate of #44302, there is actually a that was added which kind of does this now @fabiospampinato you should probably sub and drop your thoughts on that issue, maybe this is something that should be left to an extension (by making the terminal API more powerful). I was actually going to tackle that in March but put it on hold as I need to do some thinking about it, how it interacts with tasks and debug and how to prevent annoying situations, for example: create 5 terminals against a folder, work on some other project for a week, open the folder and get 5 terminals restored. But it would be good to have some basic restoring if it won't get in the way, we certainly wouldn't want to add the complexity that this extension allows. @fabiospampinato I definitely want to hear your thoughts on restoring splits, not sure if you've created an issue yet? |
I would love to be able to store terminal configurations on a per project/global basis
As an example of where it can be useful, the current project I am working on contains a graphql api and frontend sites.
On startup of vscode, I always open at least three terminals to run: tests, the api, and the frontend.
This extension by @fabiospampinato works very well, and could possibly be a base to build on in order to get something like this into the core
The text was updated successfully, but these errors were encountered: