Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I did the same thing a few years ago. Terminal.app has had tab support for years now. What's the killer feature of iTerm these days?

I also recall finding Terminal.app to have lower CPU consumption, matching postit's experience.



The killer feature for me was setting an "alarm" on a currently running process and getting a notification when it finished. It's not something I've seen in any other terminal. (Using Ubuntu now and missing it.)


I believe Elementary OS's terminal has this in-built.


Fedora has this, too.


Quake-style console. I'm too addicted to it unfortunately.


Literally the only reason why I use iTerm 2 over Terminal.app as well. Though I'm tempted to see if I can't replicate a similar "show over anything when a hotkey is pressed" in Terminal.app with some cute AppleScript...


1. When you exit a terminal it dumps irrelevant stuff rather than just closing the tab.

    ~ % 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.


There certainly are some advantages of iTerm2 but the ones you stated are very easily done in Terminal.app:

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 Preferences

3. Settings > New window with profile: Pro


Probably not a big feature for most, but I work with URLs in the terminal a lot and ⌘+click to immediately open them in the browser is convenient.

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.


Terminal.app does that too


You have to double-click and pressing ⌘ gives no visual feedback. That explains why I didn’t find it before. Thank you for the tip.


scoff how dare you use a mouse. In urxvt I have it mapped to ctrl+u


> What's the killer feature of iTerm these days?

Panes.


I don't use panes much, but Terminal.app seems to have panes too.


- Bafflingly, they split horizontally. I have a 4x4 pane setup, but my default is 2x1.

- 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.


Thanks! I feel the same about "tmux vs screen": tmux panes are just so much easier to use and more flexible than in screen, even though screen can split windows).


I really like the tmux integration.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: