From: Peter Stephenson <pws@ibmth.df.unipi.it>
To: "'zsh-workers@sunsite.auc.dk'" <zsh-workers@sunsite.auc.dk>
Subject: Re: history related suggestions
Date: Tue, 15 Jun 1999 17:27:14 +0200 [thread overview]
Message-ID: <9906151527.AA30610@ibmth.df.unipi.it> (raw)
In-Reply-To: ""Kiddle, Oliver""'s message of "Tue, 15 Jun 1999 14:10:54 DFT." <4FBF540FF16FD1119D9600A0C94B2B51F29E89@napier.logica.co.uk>
"Kiddle, Oliver" wrote:
> I'm not convinced by the zle set-local-history system for toggling between
> local and shared history. I (and I would think most people) will bind one
> set of keys to shared history operations and another set to local ones
> rather than binding a key to toggle the history mode.
You're supposed to use a widget function rather than bind it directly.
(What's happened to the manual entry for set-local-history in the zle
documentation? It doesn't seem to say anywhere how it works.)
this-with-local-history() {
local savnum=$NUMERIC
NUMERIC=1
zle set-local-history
NUMERIC=$savnum
zle the-normal-this-command
NUMERIC=0
zle set-local-history
}
zle -N this-with-local-history
bindkey '...' this-with-local-history
(this will all become smoother when argument handling becomes standardised
anyway).
> With argument handling
> hopefully being added to zle widgets (which I think is a great idea), I
> think it would be better to ditch set-local-history and add an option to
> each of the history related widgets specifying whether to use shared or
> local history.
It might be a nice idea to add this.
> Along with this, I would suggest that parameter expansion be
> done on the zle widget arguments each time the widget is run. This would
> allow users to do:
> bindkey '^[[A' up-line-or-history '$history_toggle'
> and then change the $history_toggle variable to select between local and
> shared history.
That sort of thing should certainly be done inside functions.
up-line-or-history-switch() {
zle up-line-or-history $history_toggle
}
zle -N up-line-or-history-switch
bindkey '^[[A' up-line-or-history-switch
Extra levels of expansion tend to make things a bit of a mess, and in my
experience you always get to the point where you need the extra flexibility
of a function anyway. (Cf. S. Wischnowsky, Collected New Completion
Mailings, Zsh Workers Mailing List 1999, passim.)
--
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-06-15 15:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-15 13:10 Kiddle, Oliver
1999-06-15 15:27 ` Peter Stephenson [this message]
1999-06-16 8:19 ` history related suggestions (plus bug reports) Bart Schaefer
1999-06-16 20:46 ` PATCH: pws-22: history -r fix Wayne Davison
1999-06-16 21:59 ` history related suggestions (plus bug reports) Wayne Davison
1999-06-17 6:33 ` Bart Schaefer
1999-06-16 13:00 history related suggestions Kiddle, Oliver
1999-06-16 13:07 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=9906151527.AA30610@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).