-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Add a explorer context menu entry to let the user pick the profile they want to "open here" #6111
Comments
Hiya! This is an issue I found after creating my own personalized context menu for windows terminal using a registry edit. It seems that the current implementation uses a different approach to populating the context menu, through a shell extension via appxmanifest. To me, an implementation involving directly adding registry keys directly through a .reg or .bat script seems to have several solid pros, namely:
Additionally, I do not think that this implementation would have to wait for the internal bug-fix mentioned in Issue 6414, though that may be a moot point as that may be resolved before any context menu changes go through. Admittedly, I can see one flaw of such an implementation, newly added profiles may have very poor discoverability. A cascading menu listing all profiles may need to be manually refreshed - this seems like an option that could be quite accessible within the planned gui settings, but with the current settings.json it might be a hassle ( { "refreshContextMenu": true } ? ). Similarly, deleted profiles may linger unwantedly - again something that might be easily addressed within gui settings in which profiles are removed by pressing a button, but with settings.json it would be tricky. Diffing for removed profiles doesn't seem like a good idea, and simply deleting all keys that do not match a profile may have the unwanted side effect of removing any of the user's custom added keys. If this approach does seem to be beneficial it would be something I'd be interested in contributing to, though there may be some benefits to the current implementation that I am unaware of. Thanks and kind regards!! |
Very needed feature. I was thinking that after open from explorer context menu every new tab will preserve current dir, but no :( |
Stumbled upon this project while searching this topic: https://github.com/lextm/windowsterminal-shell |
Notes:
|
Are there any plans to implement this in the near future? Please consider the following scenario: I have multiple profiles in the terminal. The default is Ubuntu (WSL), because I usually want that to open when I simply launch the Terminal application. I feel perhaps the default profiles for normal launch of Terminal and for context menu use - should be a separate setting. The above feature for a list of profiles in the context menu would also suffice. |
To work around the lack of options, I created my own explorer context menu options for different profiles (I'm using Windows 10). The basic command I use to open a new tab is You can add your own icon and export those registry entries to reuse later. This command can be added to the whole system in:
Or for a single user in:
I also use similar commands to make context menus for specific file types (like py and ps1 scripts) Edit: |
Thanks @WagnerGFX for the suggestions. Actually when I was writing my comment above, I had forgotten that it's possible to just type |
Follow up from #6100
We should add another entry to the explorer context menu to let the user select which profile.
This is the only other option I'm considering at this time, I don't want to clutter that UI too badly.
notes:
startupActions
in the specified directorystartingDirectory
#9991 maybe also relevantThe text was updated successfully, but these errors were encountered: