dscho / mintty-from-googlecode

Automatically exported from code.google.com/p/mintty
GNU General Public License v3.0
0 stars 1 forks source link

Roll the mouse wheel up and down in `screen' command. #135

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.run `screen' command
2.roll up the mouse wheel
3.go the previous command

What is the expected output? What do you see instead?
scroll up the command history.

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by tianlij...@gmail.com on 13 Oct 2009 at 1:11

GoogleCodeExporter commented 9 years ago
Mintty has no access to screen's scrollback buffers, hence it can't display 
them.

What's happening is that screen switches to the so-called alternate screen. 
When on
that, mousewheel events are sent as cursor keys by default, to enable mousewheel
scrolling e.g. in 'less'. But of course with bash running in screen, the cursor 
keys
access the history instead.

One thing you could do is stop screen from switching to the alternate screen, by
putting this into your .screenrc:

termcapinfo xterm|xterms|xs|rxvt ti@:te@

That's not a very good solution, however, because the output from different 
screen
sessions will get mixed up in mintty's scrollback buffer and you still wouldn't 
be
accessing screen's own scrollback buffers.

Therefore, a better solution would be to enable mintty 0.5's "application 
mousewheel
mode", where the mousewheel sends different keycodes from the cursor keys, and 
to map
those keycodes to access screen's scrollback buffers. I'm no screen expert 
though, so
I don't know how to do that. But see the mintty manual for details on 
application
mousewheel mode.

Original comment by andy.koppe on 13 Oct 2009 at 7:30