From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [PATCH] Re: zed-set-filename breaks zed keymap?
Date: Sun, 25 Apr 2021 13:55:03 -0700 [thread overview]
Message-ID: <CAH+w=7a_WN6YvOGwL25dPATQHRMtEyQoT=3do6HYM5XChLo80A@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7bV1nTYjfpafs1HM1gxnCDqpPZqfSpK5gBqHZ-LDJbccQ@mail.gmail.com>
On Sun, Apr 25, 2021 at 12:35 PM Bart Schaefer
<schaefer@brasslantern.com> wrote:
>
> So ... what's the correct fix here? Shortest is to change
> zed-set-file-name to use
> bindkey -A zed-normal-keymap main
> Attached patch does that.
>
> + local curcontext=zed-set-filename:::
(Typo, should be "file-name", will fix if/when committing)
Incidentally, invoking _complete_help from either zed or
zed-set-file-name gives output like this:
-----
% zed foo
File name:
_help_sort_tags:comptry:8: no tags registered
File name:
tags in context :completion:zed-set-file-name:complete:-value-,var,::
use-compctl (_default _value _value _in_vared)
-----
Is an error message from comptry really appropriate? Easily enough
discarded in _complete_help, but under what circumstances would one
ever want that error?
prev parent reply other threads:[~2021-04-25 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 3:30 Bart Schaefer
2020-05-27 4:25 ` Bart Schaefer
2021-04-25 19:35 ` [PATCH] " Bart Schaefer
2021-04-25 20:55 ` 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='CAH+w=7a_WN6YvOGwL25dPATQHRMtEyQoT=3do6HYM5XChLo80A@mail.gmail.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).