I also recall finding Terminal.app to have lower CPU consumption, matching postit's experience.
I also recall finding Terminal.app to have lower CPU consumption, matching postit's experience.
~ % exit
[Process completed]
2. Cmd + Arrow doesn't doesn't move to the next or last tab. (Cmd + number does work however, but it doesn't show numbers on the tab list like iTerm)3. Comes with terrible defaults like the screen color.
1. Settings > Profiles > Shell > When the shell exits: [Close the window|Close if the shell exited early|Don’t close the window]
2. macOS standard for all applications is the following.
- next tab: ⌃⇥ or ⌘⇧]
- previous tab: ⌃⇧⇥ or ⌘⇧[
If you really want to change that, you can do so in System Preferences3. Settings > New window with profile: Pro
I prefer to open a new Terminal only when I need it instead of keeping one open all day (even if that sometimes happens) and I’ve never noticed an increase in CPU usage that’d made me want to check.
Panes.
- Cmd-W closes the window, not the pane. (I get why they do this. I feel that it is wrong.)
- I can't send input to all panes, which is a pretty useful feature I probably use once a week.
- iTerm2 happily maps my panes to tmux. This is by itself perhaps a killer feature.