From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: PATCH: give precedence to local keymaps (was Re: More on getkeycmd())
Date: Mon, 03 Nov 2014 19:58:21 -0800 [thread overview]
Message-ID: <141103195821.ZM32334@torch.brasslantern.com> (raw)
In-Reply-To: <20535.1415032236@thecus.kiddle.eu>
On Nov 3, 5:30pm, Oliver Kiddle wrote:
} Subject: Re: PATCH: give precedence to local keymaps (was Re: More on getk
}
} Bart wrote:
} >
} > I don't particularly object, though of course the ideal behavior would be
} > that the prefix would be treated as such whenever the two maps overlap.
}
} Well, no: I don't want to treat the key as a prefix when the global
} binding is a prefix of the local binding because then I'm forced to
} type the local binding faster than $KEYTIMEOUT.
Hmm, I can see where that might be an issue for vi-mode. I'm strictly
an emacs-mode person when in the shell (although I'm editing this
message in vim) and the behavior I described is similar to the way
keymaps work in emacs.
} How about the following patch? This does hiding in the case I mention
} above but not for the converse: a local binding that is a prefix of a
} global binding won't hide the longer global binding
That's probably quite sufficient.
prev parent reply other threads:[~2014-11-04 3:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 14:53 More on getkeycmd() Bart Schaefer
2005-09-27 15:01 ` Peter Stephenson
2005-09-27 15:43 ` Bart Schaefer
2014-11-03 8:45 ` PATCH: give precedence to local keymaps (was Re: More on getkeycmd()) Oliver Kiddle
2014-11-03 9:33 ` Bart Schaefer
2014-11-03 16:30 ` Oliver Kiddle
2014-11-04 3:58 ` Bart Schaefer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=141103195821.ZM32334@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).