Live data from Hacker News

ITerm2 2.0

iterm2.com

71–80 of 237 posts

Re: ITerm2 2.0

#71
post #56

Earlier quoted context omitted.

Does tmux integrate with itself? That is, does this solve the problem of needing different prefix keys when nesting tmux sessions (whether using iTerm2, or using a terminal emulator that doesn't itself integrate with tmux)?

I thought that, when nesting tmux instances, you just press the prefix key a number of times depending on how deep you need you need your next keystroke to propagate? For me personally, I use ctrl-a instead of ctrl-b so I have this line in my ~/.tmux.conf: #send prefix to nested sessions with C-a bind-key C-a send-prefix Lastly, iterm2 uses it's own keystrokes for it's tmux integration. (i.e.: cmd-D to split vertical…

I have tmux set up so that pressing the prefix key twice switches to the previously selected window. I don't remember whether it was like that out of the box, or whether I had to configure that when I switched from gnu screen.

I take it with nested tmux sessions, cmd-D would split the outer tmux window? How would you split the inner tmux window?

Re: ITerm2 2.0

#72

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

Re: ITerm2 2.0

#74
post #71

Earlier quoted context omitted.

I thought that, when nesting tmux instances, you just press the prefix key a number of times depending on how deep you need you need your next keystroke to propagate? For me personally, I use ctrl-a instead of ctrl-b so I have this line in my ~/.tmux.conf: #send prefix to nested sessions with C-a bind-key C-a send-prefix Lastly, iterm2 uses it's own keystrokes for it's tmux integration. (i.e.: cmd-D to split vertical…

I have tmux set up so that pressing the prefix key twice switches to the previously selected window. I don't remember whether it was like that out of the box, or whether I had to configure that when I switched from gnu screen. I take it with nested tmux sessions, cmd-D would split the outer tmux window? How would you split the inner tmux window?

> I don't remember whether it was like that out of the box, or whether I had to configure that when I switched from gnu screen.

It's worth checking your config file out.

And I'm not sure how to answer your question because the way iterm integrates with tmux is that it allows you to create split panes with their own bash sessions. If you want to run tmux in those sessions, it would be tmux running in that pane, but textually instead of graphically. Here's a screenshot to make things more clear: http://i.imgur.com/0hmw62I.png

cmd-D would just create another pane to the left.

Re: ITerm2 2.0

#75

I like the idea of triggers. auto-highlighting the following regex's makes life a bit better whille reading logs and traces. . [eE](rror|xception). highlight error lines :\d+ highlight line numbers in ruby (captures bits of time stamps though...) [lL]ine \d highlight line numbers in python I bet there are more creative uses. please enlighten me.

I tried to use it with terminal-notifier[1], but couldn't get it to work :( Would've been awesome though. (Notifications after build completes, etc.)

[1]: https://github.com/alloy/terminal-notifier

Re: ITerm2 2.0

#76

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

1. Good, working fullscreen support on multiple monitors.

2. Problems with displaying my favorite font, ProggyClean, in Terminal.app.

Re: ITerm2 2.0

#77
post #72

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

Re: ITerm2 2.0

#78
post #42

Earlier quoted context omitted.

You can get session management by using tmux integration. Terminal.app almost certainly does not do what you're describing by default.

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.

I'm thrilled to hear that I'm not the only one! My MBA always crashes after I remove a Cisco console cable...

Re: ITerm2 2.0

#79

The tmux integration is a really interesting piece of work. https://docs.google.com/document/d/1ABI0kqUUxoAjxhWW3AsWFis6... http://code.google.com/p/iterm2/wiki/TmuxIntegration

I had trouble using it.

It appears that once you've created a tmux session you need to manually add tmux commands in a dialogue box.

Re: ITerm2 2.0

#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 yet it scrolls text in a terminal slower than my 386 machine 20 years ago.

Post reply on HN