Live data from Hacker News

ITerm2 2.0

iterm2.com

81–90 of 237 posts

Re: ITerm2 2.0

#81
post #72

Earlier quoted context omitted.

One problem I have with this is that its a massive security hole. Where does the output get stored? If its in an encrypted file, okay .. but if not: deal breaker.

You can disable it system wide. But it also works on a per-app basis: if you don't want the UI state restored, then just quit the app with Cmd+Option+Q (instead of the regular Cmd+Q) and OS X will not save the application state.

I wish that there would have been a setting in the program options ("Preferences"... I don't know why, but that word annoys me in this context) so that the user wouldn't always have to do cmd-opt-q. Maybe the best option would be to have a checkbox that swaps the behavior ("don't save the output unless I press cmd-opt-q").

THANKS for letting us know about cmd-opt-q! I'll have to start using that all the time since it does seem like a potential security hole.

Re: ITerm2 2.0

#82

Earlier quoted context omitted.

tmux doesn't help you in this scenario, because the tmux process is lost during a system reboot. I concur with the parent - Terminal.App's ability to restore the previous sessions output after a system crash (which on my macbook Air ranges from daily to weekly - FTDI USB Drivers and Display Port cable being to the two major reason) really make me appreciate that feature.

"FTDI USB Drivers", if it's the VCP ones the very latest ones have been reasonably stable for me. I've not had a system crash for quite a while now, whereas I was having them weekly with an older version.

Nope - I'm on the latest 2.2.18 drivers still flakey as can be - This has been an ongoing issue for me for about two years - it's a pain when you are working on a Cisco Router, and you unplug the cable and kernel panic. I guess on the (weirdly?) pro side, it's at least fairly consistent - about 20% of the time, the Macbook (two generations now for me, 2010, and 2013) kernel panics.

This is where Terminal.app (or possibly OS X 10.9 + Terminal.app) ability to show you your terminal history on recovery from Kernel Panic is really appreciated.

If only there was a reliable USB-Serial cable/controller/interface for the Mac. Unfortunately, RS-232 is so rare (except for consoling into Cisco Routers?) that there is no incentive for any vendor to actually write a half stable driver.

Re: ITerm2 2.0

#84
post #81

Earlier quoted context omitted.

You can disable it system wide. But it also works on a per-app basis: if you don't want the UI state restored, then just quit the app with Cmd+Option+Q (instead of the regular Cmd+Q) and OS X will not save the application state.

I wish that there would have been a setting in the program options ("Preferences"... I don't know why, but that word annoys me in this context) so that the user wouldn't always have to do cmd-opt-q. Maybe the best option would be to have a checkbox that swaps the behavior ("don't save the output unless I press cmd-opt-q"). THANKS for letting us know about cmd-opt-q! I'll have to start using that all the time since it…

You can disable window restoration system wide (System Preferences -> General -> "Close windows when quitting an app").

So you don't have to use the shortcut at all in that case.

Personally I prefer getting used to using it on a case-by-case basis. For example, when I leave work I tend to quit most apps on my laptop with Cmd+Option+Q, so that when I get home they don't re-open with work and I can start working on personal projects.

Re: ITerm2 2.0

#85

to HN: What changed you from "terminal.app is good enough" to "I prefer iTerm"? Because that's what I'm asking myself.

I really wish iTerm would include the Terminal.app OSX-style keyboard shortcuts as a ready-made selectable profile

Every time I install it on a new computer I have to google a bunch of places and set up the key bindings again

Re: ITerm2 2.0

#86
post #80

ITerm is great. It really is. But I wish more time was spent on optimizations. People these days seem to forget that terminals are often used for displaying huge amounts of rapidly scrolling text and that speed is of paramount importance. To put this in perspective, my computer has two CPUs with 4 cores each, 24GB RAM, a graphics card with 1600 Stream Processing Units (engine running at 850MHz) and 1GB of RAM, and ye…

Not just fast scrolling text. For some reason there is a noticeable delay when just typing text into a shell in iTerm. I didn't notice it until one day I started Terminal.app for no reason at all, and typing in it gave me that feeling that it was predicting my keystrokes, meaning of course that my brain expected a lag that wasn't there.

Re: ITerm2 2.0

#88

One feature I really wish iTerm2 2.0 would have introduced was better session restoration support. With Terminal.app, you can issue a command like 'ls' and then quit and re-open Terminal.app and the previous output from 'ls' shows up. This is incredibly useful when you have to restart or if your system crashes and you have some output that you wanted to preserve. I see from the changelog that some type of restoration…

> One feature I really wish ... It's open source. Why don't you add it yourself? I wanted a borderless terminal and as I couldn't find one I hacked the functionality into iTerm: http://i.imgur.com/jOc04sf.jpg /edit: Wow, being downvoted for suggesting to hack something yourself on Hacker News ... that's a new one. I guess I'll take a time out.

I agree with your sentiment and it is depressing to see you downvoted. On HN I would have hoped your comment would stimulate those familiar with the code base to offer hints of where to start hacking, rather than rapid down arrow clicks.

Re: ITerm2 2.0

#89
post #47

Earlier quoted context omitted.

I use Terminal almost exclusively in full-screen mode, and iTerm allows me to do just that. And no, Terminal.app does not have full-screen mode that is useful. Lion-style fullscreen apps are absolutely useless to me, since you can't bind them to ctrl-[1-9] hotkeys to switch between spaces.

paulrov (sibling to this comment): you seem to be hellbanned.

(and he's also wrong: you can't bind "App Desktops" or whatever the full-screen app windows are officially called, to ctrl-[1-9] key combo.)

Re: ITerm2 2.0

#90
post #80

ITerm is great. It really is. But I wish more time was spent on optimizations. People these days seem to forget that terminals are often used for displaying huge amounts of rapidly scrolling text and that speed is of paramount importance. To put this in perspective, my computer has two CPUs with 4 cores each, 24GB RAM, a graphics card with 1600 Stream Processing Units (engine running at 850MHz) and 1GB of RAM, and ye…

i had the same beef with it and i went back to using xquartz with dwm and urxvt.

The reason why it's so slow is very simple. It's basically an nstextview derivate.

To be fast it needs to fill the buffer and render it offscreen in fixed intervals. a lot of osx programs share this problem. there was an ancient vnc viewer called vncthing that easily beats every osx vnc viewers performance, because of that.

Post reply on HN