You are not logged in.
Normally, :set mouse=a does the trick. But not anymore. It looks like there were a bunch of mouse-related changes in 328. Would anyone be so kind as to reproduce before I submit a bug report?
(The utility I use to enable scrolling in man pages, less-mouse, also broke.)
Last edited by chikinn (2017-07-18 08:11:18)
Offline
The latest version is 330, and scrolling in vim works here with :set mouse=a parameter.
Offline
Thanks for checking. I tried 330 just now, still getting the same issue.
I wonder what's different about my system. Here's my Xresources.
!--------XTERM-----------------------------------------------------------------
XTerm*faceName: xos4 Terminus
xterm*saveLines: 4096
xterm*allowsends: true
XTerm.vt100.allowSendEvents: true
!--------XTERM COLORS (from Xterm page on Arch Wiki) --------------------------
*background: #111111
*foreground: #ffffff
*color0: #000000
*color8: #555753
*color1: #ff6565
*color9: #ff8d8d
*color2: #93d44f
*color10: #c8e7a8
*color3: #eab93d
*color11: #ffc123
*color4: #204a87
*color12: #3465a4
*color5: #ce5c00
*color13: #f57900
*color6: #89b6e2
*color14: #46a4ff
*color7: #cccccc
*color15: #ffffff
!--------XDVI------------------------------------------------------------------
xdvi*background: white
xdvi*foreground: black
xdvi*margins: 5
xdvi*zoom: 7
Offline
I have no Xressources file, xterm runs with default configuration.
In the xterm window I get:
$ echo $TERM
xterm
Offline
Why do you allowSendEvents and can you scroll the linebuffer (ie. bash output)?
Online
Thanks guys. I ditched allowsends and allowSendEvents and I can scroll again. I guess the behavior of these options changed around xterm 328; I don't remember why I had them enabled in the first place.
(To answer Seth's other question: yes, I could still scroll the linebuffer.)
Cheers, marking solved.
Offline