From: Peter Stephenson <pws@csr.com>
To: zsh-users@sunsite.dk (Zsh users list)
Subject: Re: Menu-driven version of history-beginning-search-backward
Date: Thu, 27 Jul 2006 17:53:12 +0100 [thread overview]
Message-ID: <200607271653.k6RGrCIk003550@news01.csr.com> (raw)
In-Reply-To: <dc507f4a0607270901r5a4c19f2n20a895b8a831ab3@mail.gmail.com>
"Felix Rosencrantz" wrote:
> I tried this function. One problem is it doesn't seem to work if the
> line (your search string) contains a space.
Grrr... the quoting of patterns in associative array subscripts is
screwy. You *can* quote the pattern characters, but if you quote any
other characters too they stay quoted. I've tried to quote only pattern
characters. This isn't very programmer-friendly.
> It would be nice if the
> user says "foo bar" it matches lines that matches line that match
> foo*bar
I've done it so you do this by including "-space" in the name of the
widget.
#BEGIN
# Menu-driven alternative to history-beginning-search-backward.
# As it uses a menu there is no sense of "forward" or "backward", however;
# the entire history is searched.
#
# Configuration:
# autoload -U history-beginning-search-menu
# zle -N history-beginning-search-menu
# bindkey '\eP' history-beginning-search-menu
#
# Example:
# % /bin/su<ESC-P>
# Enter digit:
# 1 /bin/su -c 'make install' 4 /bin/su - perforce
# 2 /bin/su 5 /bin/su -c
# 3 /bin/su -c 'chown pws:pws **/*(u0)'
#
# Typing "1" expands the line to
# % /bin/su -c 'make install'
#
# With a prefix argument, the search is not anchored to the beginning,
# so for example "/su" could expand to "p4 files //depot/support/..."
#
# If this is bound to a widget containing "-end", e.g.
# zle -N history-beginning-search-menu-end history-beginning-search-menu
# then the cursor is put at the end of the line, else it is left
# after the matched characters.
#
# If this is bound to a widget containing "-space", then any space in
# the line so far is matched as a wildcard. (This means putting a space
# at the start of the line is equivalent to specifying a prefix
# argument.)
emulate -L zsh
setopt extendedglob
zmodload -i zsh/parameter
local -aU matches
local -a display
local search=$LBUFFER
if [[ $WIDGET = *-space* ]]; then
search=${search//(#m)[*?#<>]/\\$MATCH/}
search=${search// /*}
fi
if (( ${+NUMERIC} )); then
matches=(${(o)history[(R)*${search}*]})
else
matches=(${(o)history[(R)${search}*]})
fi
# Filter out any match that's the same as the original.
# Note this isn't a pattern this time.
matches=(${matches:#${LBUFFER}})
integer n=${#matches}
integer width=${#n}
(( n == 0 )) && return 1
# Hey, this works...
integer i
display=(${matches/(#m)*/${(l.$width..0.):-$((++i))} $MATCH})
zle -R "Enter digit${${width##1}:+s}:" $display
local chars
read -k$width chars
if [[ $chars != [[:digit:]]## || $chars -eq 0 || $chars -gt $n ]]; then
return 1
fi
if [[ $WIDGET = *-end* ]]; then
LBUFFER=${matches[$chars]} RBUFFER=
else
integer newcursor
if (( ${+NUMERIC} )); then
# Advance cursor so that it's still after the string typed
local -a match mbegin mend
if [[ $matches[$chars] = (#b)(*${LBUFFER})* ]]; then
newcursor=${#match[1]}
fi
fi
BUFFER=${matches[$chars]}
(( newcursor )) && CURSOR=$newcursor
fi
#END
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
To access the latest news from CSR copy this link into a web browser: http://www.csr.com/email_sig.php
next prev parent reply other threads:[~2006-07-27 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 16:38 Peter Stephenson
2006-07-27 16:01 ` Felix Rosencrantz
2006-07-27 16:53 ` Peter Stephenson [this message]
2006-07-31 14:38 ` Andy Spiegl
2006-07-31 14:55 ` Peter Stephenson
2006-07-28 4:24 ` Bart Schaefer
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=200607271653.k6RGrCIk003550@news01.csr.com \
--to=pws@csr.com \
--cc=zsh-users@sunsite.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).