From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7676 invoked from network); 22 Mar 1999 20:16:24 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 22 Mar 1999 20:16:24 -0000 Received: (qmail 17031 invoked by alias); 22 Mar 1999 20:15:59 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 5884 Received: (qmail 17011 invoked from network); 22 Mar 1999 20:15:56 -0000 Message-ID: <36F6A29F.A730C19A@magix.com.sg> Date: Tue, 23 Mar 1999 04:05:51 +0800 From: Anthony Heading X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: zsh-workers@sunsite.auc.dk Subject: A couple of questions on 'bindkey' Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, I'm hacking the keymap code a bit at the moment. Am now looking for a way to switch between multiple keymaps which is more general than bindkey -e/-v, and which also allows one to switch keymaps temporarily. Two possibilities come to mind: o Switching via invocation of some new 'keymap' builtin o setting a magical shell parameter: e.g. KEYMAP=myemacs Is either of these a generally preferred mechanism? Also, having now ripped 'bindkey' to bits, I have the dull task of putting it back together. And therein I was somewhat struck by the heavyweight nature of the code which binds keys to 'ranges'. When this is really ever needed? Why wouldn't a simple shell loop be a better solution? Clearly it's needed to support reading back keymaps which were dumped in this format, but that seems to me somewhat redundant too. Would it be a good/bad/utterly unacceptable thing to remove this functionality? (I have to concede a hidden agenda - under my brave new world the housekeeping to keep track of whether we're in such a range is even more cumbersome...) Regards Anthony