From: Bart Schaefer <schaefer@brasslantern.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: PATCH: documentation on keymap selection
Date: Tue, 07 Sep 2010 09:58:48 -0700 [thread overview]
Message-ID: <100907095848.ZM12813@torch.brasslantern.com> (raw)
In-Reply-To: <20100905204050.0a87a151@pws-pc>
On Sep 5, 8:40pm, Peter Stephenson wrote:
} Subject: Re: PATCH: documentation on keymap selection
}
} On Fri, 3 Sep 2010 23:06:10 +0100
} Peter Stephenson <p.w.stephenson@ntlworld.com> wrote:
} > Peter Stephenson <p.w.stephenson@ntlworld.com> wrote:
} > > It doesn't address the issue that "bindkey -lL" lies about aliased
} > > keymaps.
} >
} > This does.
}
} While I'm at it, this seems a natural extension.
}
} +List all existing keymap names; if any arguments are given, list just
} +those keymaps.
} +
} +If the tt(-L) option is also used, list in the form of tt(bindkey)
} +commands to create or link the keymaps.
I just tried this out, and got this:
schaefer<501> bindkey -lL
bindkey -N .safe
bindkey -N command
bindkey -N emacs
bindkey -N isearch
bindkey -N listscroll
bindkey -A emacs main
bindkey -N menuselect
bindkey -N vicmd
bindkey -N viins
Is it really correct to include "bindkey -N .safe" in that output? If
I turn around and feed that back to the shell again, I get
schaefer<502> bindkey -N .safe
bindkey: keymap name `.safe' is protected
Perhaps the .safe keymap should be treated as invisible for this.
next prev parent reply other threads:[~2010-09-07 16:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 22:06 Peter Stephenson
2010-09-05 19:40 ` Peter Stephenson
2010-09-05 22:44 ` Bart Schaefer
2010-09-07 16:58 ` Bart Schaefer [this message]
2010-09-07 17:16 ` Bart Schaefer
2010-09-07 17:55 ` Peter Stephenson
-- strict thread matches above, loose matches on Subject: below --
2010-09-03 20:47 Peter Stephenson
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=100907095848.ZM12813@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).