On Wed, Feb 04, 2015 at 05:59:37PM +, Nicholas Marriott wrote:
This is from the xterm clipboard escape sequence which tmux will use
when the set-clipboard option is on and TERM is xterm (or, more
accurately: when it sees Ms in terminfo, which we add for xterm in
terminal-overrides).
You can
Yes it will use @0 from session 0, if you try to move from another
session to the current one using the window id, it will fail.
On Mon, Feb 09, 2015 at 10:55:50AM -0500, Ben Boeckel wrote:
> On Mon, Feb 09, 2015 at 15:53:59 +, Nicholas Marriott wrote:
> > Hmm weird it doesn't work for me, oh
On Mon, Feb 09, 2015 at 15:53:59 +, Nicholas Marriott wrote:
> Hmm weird it doesn't work for me, oh well...
Maybe because my test case was:
tmux
# in another terminal
tmux
tmux movew -s @0 -t 1:1
and it just grabbed *session* 0 instead?
--Ben
--
Hmm weird it doesn't work for me, oh well...
On Mon, Feb 09, 2015 at 10:39:33AM -0500, Ben Boeckel wrote:
> On Mon, Feb 09, 2015 at 12:37:26 +, Nicholas Marriott wrote:
> > (I think what you were trying would not work at the moment, we should
> > probably make cmd_lookup_window pass @foo thro
On Mon, Feb 09, 2015 at 12:37:26 +, Nicholas Marriott wrote:
> (I think what you were trying would not work at the moment, we should
> probably make cmd_lookup_window pass @foo through cmd_window_session if
> it isn't in the current session...)
Hmm. It *does* work, but it also hasn't crashed s
Hmm. The windows list can contain NULL, so window_find_by_id is probably
wrong here, but I'm not sure how you got to that codepath in the first
place. Clearly it is possible though.
(I think what you were trying would not work at the moment, we should
probably make cmd_lookup_window pass @foo thro
Thank you for your help! I will report it as a bug on the libevent bug
tracker.
On 09/02/15 14:05, Nicholas Marriott wrote:
> Thanks. Either a bug in libevent or they have changed behaviour in a way
> that negatively impacts tmux. It doesn't sound reasonable for SIGCHLD to
> be deferred for so lo
Thanks. Either a bug in libevent or they have changed behaviour in a way
that negatively impacts tmux. It doesn't sound reasonable for SIGCHLD to
be deferred for so long so it is probably a bug.
On Mon, Feb 09, 2015 at 01:33:43PM +0200, Aleksandrina Nikolova wrote:
> Thanks for the explanation!
Thanks for the explanation!
Indeed the libevent was the problem - I checked and it turned out that
it was one of the packages updated right before the problem occurred. It
was updated to version 2.1.5 which is still not marked as stable on
amd64 (my platform). Reverting back to stable 2.0.22 mak
