-
Notifications
You must be signed in to change notification settings - Fork 101
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
Support for windows terminal #701
Comments
Please note that for the current approach we have We can keep this approach and do not have to copy the linked powershell script solution but just get some inspirations from there. |
TDB: Maybe if we rather recommend to use git-bash and get used to it, we should focus on that. The context-menu with sub-menu-entries appears nice in the first place but requires additional attention/selection each time so a single flat entry might still be the best option for power-users. Also we should add a small devonfw icon for our menu entry to make it fancy. |
See also microsoft/terminal#7452 |
I have installed Windows the Terminal and created registry keys for the context menu. Applications can be started in different tabs, and now the correct directory has to be given and the devon configuration file has to be executed at start. |
#701 Support for Windows Terminal corrected the path to the reg files
As a devonfw-ide user on windows, I want to make use of microsoft Terminal app so that I get all my shell sessions as tabs in one window.
Therefore devonfw-ide should notice if Terminal app is installed on windows and if so instead of installing the regular context menu entries like "open devonfw CMD here" install something like this but with full devonfw-ide integration setting up the environment:
https://github.com/lextm/windowsterminal-shell
So as a result in Windows Explorer I would have additional options in the context menu "Open devonfw «Shell-Type» in Windows-Terminal here".
The first step is to implement this for CMD.
For GitBash we created #692
For PowerShell we created #786
The text was updated successfully, but these errors were encountered: