[PATCH] Allow custom key tables for e.g. multiple keystroke bindings.
(too old to reply)
Nicholas Marriott
2015-04-13 19:49:28 UTC
I made a load of changes and sent them to the author but he didn't respond and I haven't had time to pick it up again. I'll send the latest to you when I get home if you want to continue with it. IIRC it was pretty much done just needed testing and maybe man page...

-------- Original message --------
From: Ross Hadden <***@gmail.com>
Date:13/04/2015 16:21 (GMT+00:00)
To: tmux-***@lists.sourceforge.net
Subject: Re: [PATCH] Allow custom key tables for e.g. multiple keystroke bindings.
Or are you thinking of creating the table after running the set
This shouldn't work - you shouldn't be able to set a client to a
nonexistent table.
I guess I don't super care what happens since I won't personally be
writing any switch-client -T into an empty table but I had assumed we
would allow switching to a new [and ephemeral] table since otherwise
switch-client -T can fail which just seems weird to me.
I'd say it should fail if the table doesn't exist.
I can't think of a case where I would want it to automatically create a
table, except to confuse people who make a typo in the table name. Do
you have a use in mind?
Not specifically, I just prefer to see tools degrade what might be
described as "uniformly" where possible.  Nonuniform behaviour makes
tools dangerous for automated use because when writing a script you're
unlikely to think of things like "what if this table is empty" or "what
if this command barfs on no args when really no args means I just didn't
need it to do anything".
I'll switch it and the next set of patches will be up shortly.
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform
Simple to use. Nothing to install. Get started now for free."
Has work on this continued?  I made an issue about it
(https://sourceforge.net/p/tmux/tickets/172/) in an effort to bring
attention to this patch, but Thomas said it's pretty much not going anywhere
unless the original patch author continues or makes an effort to get it
merged himself.

I would love to see this landed in tmux!  My current workaround can be seen
at https://github.com/rosshadden/dotfiles/blob/master/src/.tmux.conf#L79-L85
and https://github.com/rosshadden/dotfiles/blob/master/src/lib/tmux-