From: Peter Stephenson <pws@ibmth.df.unipi.it>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Alternative design for keymap code
Date: Fri, 02 Jul 1999 18:06:06 +0200 [thread overview]
Message-ID: <9907021606.AA33014@ibmth.df.unipi.it> (raw)
In-Reply-To: ""Anthony J Heading""'s message of "Thu, 01 Jul 1999 22:14:56 DFT." <482567A1.004530C0.00@nyc-ntgw-n01.ny.jpmorgan.com>
"Anthony J Heading" wrote:
> After reflecting for a while, I believe there's still value in some of the
> design. And I'm thinking instead that maybe there should be a shell
> parameter KEYMAP/keymap pair, which specificies the prevailing set of
> keymaps. These are searched in order. Shell function are then able to
> push their own map onto the head the list if they need. And by allowing
> the KEYMAP parameter to be function-local, exit cleanup is automatic.
Just some thoughts while I'm waiting to go to a conference dinner: perhaps
these should be ZKEYMAP and zkeymap since we`re trying to keep the
parameter list reasonably unpolluted. Also, if these are going to be tied,
then they should probably be normal rather than special tied arrays, since
if I remember right (I try hard never to look at this in the code since it
gives me nightmares, but it would seem I do) making special parameters
local still doesn`t work. Maybe we should fix this, then I could sleep at
nights. The problem is keeping them special and restoring the values, but
this has been pretty much solved for `special=value builtin' so it
shouldn't be too hard to solve it here as well.
--
Peter Stephenson <pws@ibmth.df.unipi.it> Tel: +39 050 844536
WWW: http://www.ifh.de/~pws/
Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy
next prev parent reply other threads:[~1999-07-02 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 14:14 Anthony J Heading
1999-07-02 16:06 ` Peter Stephenson [this message]
1999-07-02 6:56 Sven Wischnowsky
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=9907021606.AA33014@ibmth.df.unipi.it \
--to=pws@ibmth.df.unipi.it \
--cc=zsh-workers@sunsite.auc.dk \
/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).