Yeah. I think it also causes it to respect -t better in certain
contexts, when -t specifies the session (and the window is in multiple
sessions), because it had been ignoring the session from -t, using the
one from the client instead.
-mjc
On 05/22/2010 10:03 AM, Nicholas Marriott wrote:
> This l
This lets enter work from outside because otherwise ctx->curclient is
NULL, yes?
Looks fine and works good for me, go for it.
On Fri, May 21, 2010 at 01:17:59AM -0700, Micah Cowan wrote:
> On 05/20/2010 08:17 PM, Micah Cowan wrote:
> > Okay, I now understand why that is: copy-selection needs to
On 05/20/2010 08:17 PM, Micah Cowan wrote:
> Okay, I now understand why that is: copy-selection needs to know which
> session's paste buffers should be affected, and it gets this information
> from the passed-in instance of "struct client", which of course is NULL
> for direct shell commands. So I
On Thu, May 20, 2010 at 08:17:57PM -0700, Micah Cowan wrote:
> Okay, I now understand why that is: copy-selection needs to know which
> session's paste buffers should be affected, and it gets this information
> from the passed-in instance of "struct client", which of course is NULL
> for direct she
Okay, I now understand why that is: copy-selection needs to know which
session's paste buffers should be affected, and it gets this information
from the passed-in instance of "struct client", which of course is NULL
for direct shell commands. So I need it to get it the session
information from else
I've been playing around with scripting certain actions in copy-mode,
and have run into what I believe to be a bug in recent CVS tmux.
If I run the command:
tmux copy-mode \; send-keys 0 Space e Enter
(which in vi bindings should jump to the start of the line, start
selection, move to the end
