-
-
Notifications
You must be signed in to change notification settings - Fork 364
Allow using third party Terminals (Shell Plugin) #3243
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
Comments
Hello, can #3225 help? |
it looks like it could work, i just don't know how to implement it or download and replace the modified files |
If you need this update urgently, you can download the latest build of Flow Launcher here: https://ci.appveyor.com/project/JohnTheGr8/flow-launcher/builds/51529514/artifacts. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 60 days.\n\nAlternatively this issue can be kept open by adding one of the following labels:\nkeep-fresh |
Issue closed. Please wait for 1.20.0 release. |
Is your feature request related to a problem? Please describe.
I currently use a command line terminal that's in Beta, but have also used one called Hyper before and noticed that currently there is no way to specify which terminal you want to use and instead can only use the default one that Windows prefers
Describe the solution you'd like
Add a method to add the location of the terminal exe file that it will use when launching commands
Describe alternatives you've considered
Using the Plugin Runner to launch the terminal I use with the command as an argument rather than use the Shell plugin
The text was updated successfully, but these errors were encountered: