[screen-devel] [bug #50208] paste . command acting strangely without setsid

2017-02-01 Thread Min Xu
URL: Summary: paste . command acting strangely without setsid Project: GNU Screen Submitted by: minxu Submitted on: Thu 02 Feb 2017 07:36:00 AM GMT Category: Program Logic

[screen-devel] [bug #37206] Support for newer terminal mouse modes

2017-02-01 Thread Ryan
Follow-up Comment #5, bug #37206 (project screen): Odd, I wonder what would cause that... emacs user here, so I don't mouse around on the bottom row much. However, I can confirm that clicking on the emacs mini-buffer indeed sends "ESC [" (according to M-x view-lossage). Maybe an off-by-one error s

[screen-devel] [bug #37206] Support for newer terminal mouse modes

2017-02-01 Thread Amadeusz Sławiński
Follow-up Comment #4, bug #37206 (project screen): Thanks! I've tested it with vim and mc. It seems to mostly work, but one thing I've noticed is that in mc I can't use bottom row buttons it just writes '[' character to prompt. ___ Reply to

[screen-devel] [bug #50197] out of bounds write when dimensions are still 0, 0

2017-02-01 Thread Amadeusz Sławiński
Update of bug #50197 (project screen): Status:None => Fixed ___ Follow-up Comment #2: Thanks for detailed bug report and analysis. Apparently it was already "fixed" on master branch

[screen-devel] [bug #37206] Support for newer terminal mouse modes

2017-02-01 Thread Ryan
Follow-up Comment #3, bug #37206 (project screen): Attaching the latest version of my patch, for 4.3.1. I've been using it on every copy of screen I have, without problems, for over a year now. I use the SGR mode almost exclusively, though, so YMMV on the other modes. (file #39640) __

[screen-devel] [bug #37206] Support for newer terminal mouse modes

2017-02-01 Thread Amadeusz Sławiński
Update of bug #37206 (project screen): Status:None => Confirmed ___ Follow-up Comment #2: If we want to support big terminal windows we should do this. There is also https://lists.gnu.o

[screen-devel] [bug #50197] out of bounds write when dimensions are still 0, 0

2017-02-01 Thread anonymous
Follow-up Comment #1, bug #50197 (project screen): More investigation yielded some more insights: - rows/cols is zero because of an earlier escape sequence (\E[?1;3;4;6l) which is "column mode" and is supposed to initialize to either columns of 80 or 132, see e.g. http://vt100.net/docs/vt220-rm/ch