4 ms·

0) It sabotages your scrollback (just like screen), no more mouse-wheel scrolling. Showstopper for me.

by moe 14y ago

calpaterson 14y ago
Just in case you didn't know, you can access screens scrollback by hitting Control-a [ (exist with escape).
vacri 14y ago
Screen doesn't 'sabotage' it. You're running a program called Screen. It has its own scrollback.
- saurik 14y ago
  Even more: screen doesn't even always do that... I'm always in a screen, and if I scroll in iTerm2 (yes: using my trackpad as a mouse-wheel) it usually works the way I'd expect (I can naturally scroll back through the recent history of my shell session), and I can additionally scroll in screen (which will have weird ramifications, of course, on my local terminal scroll-back). (I have found this offers "best of both worlds", as I can get my recent scrollback locally and gracefully, but can dig through the history to get things I may have typed from different machines.)
  - mh- 14y ago
    Mess with the two checkboxes here: http://cl.ly/image/0K1A1w2m3X2c http://cl.ly/image/0K1A1w2m3X2c Those are located in the Terminal tab of your Profile. Also, go to the docs and see the following sections: - Save lines to scrollback when an app status bar is present - Disable save/restore alternate screen Those contain the respective explanation for the two options. http://www.iterm2.com/#/section/documentation/preferences http://www.iterm2.com/#/section/documentation/preferences
geofft 14y ago
That's somewhat on purpose -- terminal rendering is on the server-side, so that if there's a lot of changes to the screen (a long terminal command, a full-screen curses app that did several updates, etc.), and the connection was bad during that, then the client only needs to see what's currently on the screen. If you're ever used a curses app over a bad connection, and seen it slowly update itself over the course of several seconds to catch up, you can understand why this is useful. As other folks have mentioned, if you run screen on the server-side, then you can ask screen for its scrollback. Also, see this open ticket: https://github.com/keithw/mosh/issues/2 https://github.com/keithw/mosh/issues/2
- moe 14y ago
  Yup I know the reasons and implications (have written my own terminal emulators in the past). I just felt the list is not complete without the biggest(?) annoyance of them all. I wish someone would write a "dumb screen" that simply plays back the last n kb when I re-attach and otherwise doesn't try to emulate a terminal inside my terminal. screen and tmux (which I use heavily) are terrible crutches from a distant past that do way more (and poorly) than most people actually want. I know mosh tries to fill a different niche (high latency links) so take this less as a stab against mosh but more as a general rant about the fact that it's 2013 and my laptop, which can render photo-realistic 3d videogames in realtime, is still not able to seamlessly resume a handful of text-mode terminal sessions without resorting to one of the above kludges. Well, first world problems, shoemakers son always goes barefoot, etc...

0) It sabotages your scrollback (just like screen), no more mouse-wheel scrolling. Showstopper for me.

by moe 14y ago

0) It sabotages your scrollback (just like screen), no more mouse-wheel scrolling. Showstopper for me.

calpaterson 14y ago

Just in case you didn't know, you can access screens scrollback by hitting Control-a [ (exist with escape).

vacri 14y ago

Screen doesn't 'sabotage' it. You're running a program called Screen. It has its own scrollback.

saurik 14y ago
Even more: screen doesn't even always do that... I'm always in a screen, and if I scroll in iTerm2 (yes: using my trackpad as a mouse-wheel) it usually works the way I'd expect (I can naturally scroll back through the recent history of my shell session), and I can additionally scroll in screen (which will have weird ramifications, of course, on my local terminal scroll-back). (I have found this offers "best of both worlds", as I can get my recent scrollback locally and gracefully, but can dig through the history to get things I may have typed from different machines.)
- mh- 14y ago
  Mess with the two checkboxes here: http://cl.ly/image/0K1A1w2m3X2c http://cl.ly/image/0K1A1w2m3X2c Those are located in the Terminal tab of your Profile. Also, go to the docs and see the following sections: - Save lines to scrollback when an app status bar is present - Disable save/restore alternate screen Those contain the respective explanation for the two options. http://www.iterm2.com/#/section/documentation/preferences http://www.iterm2.com/#/section/documentation/preferences

geofft 14y ago

That's somewhat on purpose -- terminal rendering is on the server-side, so that if there's a lot of changes to the screen (a long terminal command, a full-screen curses app that did several updates, etc.), and the connection was bad during that, then the client only needs to see what's currently on the screen. If you're ever used a curses app over a bad connection, and seen it slowly update itself over the course of several seconds to catch up, you can understand why this is useful. As other folks have mentioned, if you run screen on the server-side, then you can ask screen for its scrollback. Also, see this open ticket: https://github.com/keithw/mosh/issues/2 https://github.com/keithw/mosh/issues/2

moe 14y ago
Yup I know the reasons and implications (have written my own terminal emulators in the past). I just felt the list is not complete without the biggest(?) annoyance of them all. I wish someone would write a "dumb screen" that simply plays back the last n kb when I re-attach and otherwise doesn't try to emulate a terminal inside my terminal. screen and tmux (which I use heavily) are terrible crutches from a distant past that do way more (and poorly) than most people actually want. I know mosh tries to fill a different niche (high latency links) so take this less as a stab against mosh but more as a general rant about the fact that it's 2013 and my laptop, which can render photo-realistic 3d videogames in realtime, is still not able to seamlessly resume a handful of text-mode terminal sessions without resorting to one of the above kludges. Well, first world problems, shoemakers son always goes barefoot, etc...