-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Open .command
files with kitty on macOS
#3366
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
Not sure what you are asking for. What is kitty supposed to do with a |
It's possible to add |
On Fri, Mar 05, 2021 at 02:49:28AM -0800, Luflosi wrote:
It's possible to add `MimeType` definitions to the `.desktop` file, perhaps this is what he's asking for?
This is macOS so there are no .desktop files. I could certainly add
.command as a handled filetype in info.plist but I dont really get the
use case. This would require the .command file to be executable, and in
any case after running it, kitty would instantly exit, so you would not
be able to see the output.
|
Please look at this issue react-native-community/cli#303, and especially this comment react-native-community/cli#303 (comment) It explains the use case |
Sorry, I dont follow. There are people that want to run shell scripts by |
boom. done. |
I've tried to look a bit more in depth at the problem. When using react native, at one point the script is trying to execute a file named The react-native cli opens the script by opening a new window with the default terminal application. It's similar to opening the script from the Finder. When trying to setting kitty as the default app for this kind of file as @klooj explained, I get this error: I can execute shell scripts by opening files in the finder with Terminal.app and iTerm, but it doesn't work with kitty. |
It's not possible to open
.command
fille with kitty, whereas it's possible with most other terminal apps.It's common for script to use .command file to run a terminal script. Until kitty doesn't support this feature, it means that we have to set another terminal application as the default app for
.command
filesThe text was updated successfully, but these errors were encountered: