What I discovered is something called triggers, which is a built-in feature within iTerm2. If you don’t want to, well I guess this post wouldn’t make much sense to read then :). First of all, if you don’t use iTerm2, I highly recommend it. I’d like to share something with you all that I’ve been using for about 5ish years now. I’d have to say, typing in my password over and over and over gets pretty annoying, especially if my password takes some time to type (it does). Doing this tends to prompt me for my password quite often, since much of my work requires to run things as sudo either on my Mac on Linux systems accessed with SSH. The paid alternative mentioned by the OP - application ShellTo - also supports iTerm2 in principle, but as of this writing doesn't support the current version, v3+.Working in tech requires me to pretty much live in the command line.While the Go2Shell app that prompted the OP's question does have a configuration dialog that supports iTerm2 ( open -a Go2Shell - config, the application doesn't seem to work at all as of OSX 10.11.6 (on clicking the toolbar button as of v2.23, the only thing that ever happens is that the configuration dialog comes up, even after having clicked Install Go2Shell to Finder). Therefore, applications must be configured INDIVIDUALLY to use iTerm2 instead of Terminal, IF they support that: iTerm2 itself somewhat misleadingly offers a menu item named iTerm2 > Make iTerm2 Default Term (as presented in halfcube's answer), but the only thing that does is to make Finder run shell scripts opened from it in iTerm2 (more specifically, it assigns the shell role of UTI public.unix-executable to Finder) - which is not a typical use case.See Daniel Beck's helpful answer for background information.MacOS (OS X) does NOT support the concept of a default terminal. To provide a pragmatic summary of the existing answers: This will often require substantial changes to the programs or scripts doing that. If Terminal is used via its AppleScript API, there is no way to just replace it with iTerm in all cases, as their APIs are quite different. using Automator and/or AppleScript to replace these. You need to create your own Services e.g. The association with Terminal.app is hard-coded. Terminal.app also provides the following Services for other applications: Screenshot of Xcode 4 showing the result of changing x-man-page in Default Apps preference pane: You can of course edit it in a suitable editor yourself. You can also use it as an alternative method of changing the file type associations.Īll of these settings are user specific and stored in ~/Library/Preferences/. For the URL schemes, you can download and install the preference pane Default Apps and change the association there. terminal.įor the file types, just open the Get Info dialog and associate all files of this kind with iTerm. ITerm is capable of handling all of these except the Terminal.app specific. It's just an application that can handle URL schemes and file types. Other than that, there is no default terminal in OS X. command (scripts), and itself as an editor/viewer for these. Terminal.app declares itself a handler of the ssh, telnet and x-man-page URL schemes.
0 Comments
Leave a Reply. |