That fixes the issue.
-FR.
On Sun, Feb 16, 2014 at 3:12 PM, Thomas Adam wrote:
> On Sun, Feb 16, 2014 at 07:39:27AM -0800, Felix Rosencrantz wrote:
> > I saw it when setting a colour option to a bogus value "none".
>
> So why not send a patch through?
>
> Nicholas, see below. I can't say I li
hi
are you very sure you have latest git?
are you sure its that commit and not one of the ones to fix xterm-keys
partials recently?
what seq do ctrl arrows send now that modifyOtherKeys is off?
also what is TERM outside tmux?
probably the keys look like the start of something else so tmux is
w
should it show an error?
On Sun, Feb 16, 2014 at 11:12:06PM +, Thomas Adam wrote:
> On Sun, Feb 16, 2014 at 07:39:27AM -0800, Felix Rosencrantz wrote:
> > I saw it when setting a colour option to a bogus value "none".
>
> So why not send a patch through?
>
> Nicholas, see below. I can't say
Hi,
It does show an error when the command is parsed. Or were you wanting
something explicit here?
Thomas Adam
On 17 Feb 2014 13:49, "Nicholas Marriott"
wrote:
>
> should it show an error?
>
> On Sun, Feb 16, 2014 at 11:12:06PM +, Thomas Adam wrote:
> > On Sun, Feb 16, 2014 at 07:39:27AM -0
On 2014-02-14 13:22, Nicholas Marriott wrote:
> Why not just let them both through always?
Note that your patch has a slight behavior change: Originally any mouse
event would change the current pane as long as the current one is not
copy mode. In the new one we can only use DOWN and WHEEL but in a
Nicholas Marriott writes:
> Thanks
>
> Where did tmux.el come from? Did you write it?
>
> Can you add either a public domain declaration (look at vim-keys.conf)
> or the ISC license text to the top of the two new files?
>
> I think you have probably added enough to tmux.vim at least to be able
>
On Mon, Feb 17, 2014 at 13:47:05 +, Nicholas Marriott wrote:
> are you very sure you have latest git?
commit b3de4a3dec85bc84bb83da6b46e2a8e2a634ace3
Merge: 8edbbb9 81db6ba
Author: Thomas Adam
Date: Sun Feb 16 23:02:07 2014 +
does not work and on top of that reverting
f52eac62259c431da
Right but that commit changes a lot. What if you don't revert it but revert the
two xterm-keys partial fixes? Last two or so changes to xterm-keys.c and
tty-keys.c, I can't look up thm now but they should obviously mention partial
keys.
Original message
From: Ben Boeckel
Da
On Mon, Feb 17, 2014 at 16:51:32 +, Nicholas Marriott wrote:
> Right but that commit changes a lot. What if you don't revert it but
> revert the two xterm-keys partial fixes? Last two or so changes to
> xterm-keys.c and tty-keys.c, I can't look up thm now but they should
> obviously mention pa
Yes, I know, it changes the keys that are sent entirely. But tmux should
work with either set of keys. And this happened in October. Why don't
you just check and see if reverting c52548f and 72d1be5 fixes it
instead?
On Mon, Feb 17, 2014 at 12:46:44PM -0500, Ben Boeckel wrote:
> On Mon, Feb 17,
Yes you're right this is fine thanks.
On Mon, Feb 17, 2014 at 03:05:21PM +, Thomas Adam wrote:
>Hi,
>
>It does show an error when the command is parsed. Or were you wanting
>something explicit here?
>
>Thomas Adam
>
>On 17 Feb 2014 13:49, "Nicholas Marriott" <[1]nichola
On Mon, Feb 17, 2014 at 18:08:47 +, Nicholas Marriott wrote:
> Yes, I know, it changes the keys that are sent entirely. But tmux should
> work with either set of keys. And this happened in October.
I haven't been tracking git HEAD as closely as in the past. The previous
update on this machine
Seems like you are missing c52548f:
commit c52548f6fd311e4df3076ba4cc6f6ab8849557ac
Author: nicm
Date: Mon Feb 10 11:20:41 2014 +
The last fix to xterm keys meant that some keys such as \033OA were
being wrongly treated as partial matches. So both check xterm keys after
standar
Hello all,
Two developers login via ssh with the same unix user, attach to the same
tmux, and have all activity synced, for example, if one developers changes
the window, the current window will also change for the other developer.
That makes impossible for both users to work simultaneously in di
On Mon, Feb 17, 2014 at 04:26:33PM -0300, Br??ulio Bhavamitra wrote:
> Hello all,
>
> Two developers login via ssh with the same unix user, attach to the same
> tmux, and have all activity synced, for example, if one developers changes
> the window, the current window will also change for the othe
Thank you Thomas.
On Mon, Feb 17, 2014 at 4:30 PM, Thomas Adam wrote:
> On Mon, Feb 17, 2014 at 04:26:33PM -0300, Br??ulio Bhavamitra wrote:
> > Hello all,
> >
> > Two developers login via ssh with the same unix user, attach to the same
> > tmux, and have all activity synced, for example, if on
This looks good but you need to add the new flag and key to the manpage?
On Sat, Feb 15, 2014 at 04:20:03PM -0600, J Raynor wrote:
> > Hi. Can you make this a flag to setb (-A? -a?) instead of a new command?
>
> Sure. I've attached a new patch. There's no append-buffer command,
> and passing -
Hi
Thanks.
I tried to make your FAQ text clearer but I don't understand what the
FAQ entry is telling me to do.
Should I copy screen.el into load path and edit it? Or tmux.el? Or both?
It seems like just tmux.el is enough if xterm-keys is on?
So what should I do with tmux.el? Put it in load pat
Looks good but I think this'll wait til after 1.9.
Original message
From: J Raynor
Date: 14/02/2014 05:15 (GMT+00:00)
To: Nicholas Marriott
Cc: tmux-users@lists.sourceforge.net
Subject: Re: use "--" to mark start of command w/ neww etc to avoid quoting
> I reckon we al
> This looks good but you need to add the new flag and key to the manpage?
I've attached a new patch that includes updates to the man page.
tmux-append.patch
Description: Binary data
--
Managing the Performance of Cloud-
On Mon, Feb 17, 2014 at 18:28:35 +, Nicholas Marriott wrote:
> Seems like you are missing c52548f:
>
> commit c52548f6fd311e4df3076ba4cc6f6ab8849557ac
> Author: nicm
> Date: Mon Feb 10 11:20:41 2014 +
>
> The last fix to xterm keys meant that some keys such as \033OA were
> bei
21 matches
Mail list logo
