4 ms·
Sucks that it doesn't work in iTerm2.
by beshrkayali 13y ago
Sucks that it doesn't work in iTerm2.
- eddieroger 13y agoYes it does - I just tried it. Worked like a dream.
- beshrkayali 13y agoDon't know why it's not working in mine then: http://d.pr/v/mgsi http://d.pr/v/mgsi
- jkbr 13y agoIt does for me. iTerm2, build 1.0.0.20140112
- jsilence 13y agoIt does in mine.
- sgt 13y agoDoesn't work in mine either (Build 1.0.0.20130319). So it appears that we just need to upgrade, as others report that it works in more recent versions.
- jimhart3000 13y agoFor some reason when I try this in iTerm2, it jumps to a different command in my history. No idea what's going on there...
- kshay 13y agoI saw this too... It looks like when you opt-click above the current line, it jumps back in your history by... the same number of lines as your cursor is above the current line? Sort of an unusual feature. Nevertheless, when I'm careful to actually click on the current line, it works as described.
- gnachman 13y agoTerminal does the same (for me). It's because opt-clicking above the line sends some up arrow keystrokes, which the shell interprets as moving back in history. In iTerm2 nightly builds (which are less stable than the betas) you can disable opt-click to move the cursor in prefs>profiles>pointer. What's more interesting is the possibility of using the new shell integration features (https://code.google.com/p/iterm2/wiki/ShellIntegration https://code.google.com/p/iterm2/wiki/ShellIntegration) to turn off this feature just at the shell prompt. I'll open a feature request for that :)
- jacobr 13y agoTry alt instead of cmd.