-
Notifications
You must be signed in to change notification settings - Fork 10
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
Homebrew cask #2
Comments
Hi @ealeksandrov, Yeah, I'm maintaining it. I'll push the update for 2.8 shortly. I don't think there is a good way to allow selection of the specific plugin variant. Homebrew formula have a good way which would work: adding options like Like you say, this will be solved by the in-app selector (for 3.0), so I'd suggest for now that people stick to manual installation of variant they need if they're not using Terminal.app. I'll get back on getting my WIP implementation of the in-app selector pushed soon so that we can work on it. I've just been a bit busy lately. :-) |
Cool, thanks. No hurry with 3.0, that's not a blocker. I added you as a collaborator to this repository, feel free to push your branch in here. |
awesome stuff here! |
Use this issue to express my appreciation to the work you've done for this project. Very useful! Thanks! |
First of all, thank you for continuing support for this helpful project. Unfortunately, the currently available version in brew cask is not really useful. Is there any information/progress on the aforementioned version 3.0 to add the in-app selection of preferred terminal application? I cannot seem to find anything. For the time being, would it be an option to add each of the individual flavors of this app as separate casks? Similar to Homebrew/homebrew-cask#52000 and Homebrew/homebrew-cask#52051 |
Thanks for reminder I'll check in a week or two for in-app selection feature, maybe it won't require much time. |
Hey, @tghs - are you maintaining homebrew casks for this fork? I'm not a pro in this and we need to add ability to select specific plugin to use (@dimitrieh suggestion).
Or maybe we should go ahead and implement it as in-app feature - selector of specific console emulator?
The text was updated successfully, but these errors were encountered: