Thanks for the detailed explanation.
The tmux server crashes with a [lost server] message as soon as I send a
mouse cursor escape sequence IF terminal-overrides option is defined in
.tmux.conf--no matter what I add, remove, or set.
For example, in .tmux.conf, I'll add this basic line: set -g
term
Unfortunately, in xterm "0 q" is not the sequence to reset cursor style
to what you configured. It always resets it to "blinking block". Which
IMO is silly but I guess it probably matches the DEC behaviour and it's
the way it is.
Anyway, in tmux we do need some way to reset to the actual default,
Hi Nicholas,
I've been playing around with various escape code using echo -ne and here
are my observations:
1. The CORRECT mintty escape code to reset cursor style back to the default
vertical line is: '\e[0 q'. Tmux is swallowing this specific escape
sequence, and not passing it on to the termin
Hi
What commands are you doing that regularly exceed 2048 bytes and why
can't you put them in a temporary script or something and run that
instead?
On Thu, May 30, 2013 at 08:49:05AM -0700, Jack Bates wrote:
> I keep getting an error, "command too long" when I run:
>
> $ tmux new-session ..
I keep getting an error, "command too long" when I run:
$ tmux new-session ...
I wish that the tmux COMMAND_LENGTH was more than 2048.
If tmux could handle commands of arbitrary length, up to something like
the maximum argument length for the system (ARG_MAX), that would be
cool. But even
It was merged. If you use the DCS \ePtmux;...\e\\ escaping then it won't
work, that makes tmux pass the cursor sequences through without
tracking them.
On Fri, May 31, 2013 at 05:45:39PM -0700, simfox3 wrote:
>Hi All,
>In VIM, my normal mode cursor is a block, like most of you I presume.
