From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-users@sunsite.auc.dk
Subject: Re: ZLE Widget: Insert last word (except &)
Date: Wed, 12 Jul 2000 08:26:36 +0000 [thread overview]
Message-ID: <1000712082636.ZM9329@candle.brasslantern.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10007111846240.1513-100000@langec.myip.org>
I wrote:
} If we don't accept the shell syntax definition of a "word", how can we
} choose a single definition of what constitutes a "word" that everyone
} will agree on?
The answer is, we don't, we use a style. Which isn't (presently) ever done
with the builtin widgets, so you aren't going to see this as the default
behavior of insert-last-word any time soon.
---- 8< ---- cut ---- 8< ----
# smart-insert-last-word
# Inspired by Christoph Lange <langec@gmx.de> from zsh-users/3265.
#
# This function as a ZLE widget can replace insert-last-word, like so:
#
# zle -N insert-last-word smart-insert-last-word
#
# With a numeric prefix, simply calls .insert-last-word, which is also the
# fall-through case in the event that "smart" word selection fails.
#
# Otherwise, the rightmost "interesting" word from the previous command is
# found and inserted. The default definition of "interesting" is that the
# word contains at least one alphabetic character, slash, or backslash.
# This definition can be overridden by use of a style like so:
#
# zstyle :insert-last-word match '*[[:alpha:]/\\]*'
#
# For example, you might want to include words that contain spaces:
#
# zstyle :insert-last-word match '*[[:alpha:][:space:]/\\]*'
#
# Or include numbers as long as the word is at least two characters long:
#
# zstyle :insert-last-word match '*([[:digit:]]?|[[:alpha:]/\\])*'
#
# That causes redirections like "2>" to be included.
#
# Note also that the style is looked up based on the widget name, so you
# can bind this function to different widgets to use different patterns:
#
# zle -N insert-last-assignment smart-insert-last-word
# zstyle :insert-last-assignment match '[[:alpha:]][][[:alnum:]]#=*'
# bindkey '\e=' insert-last-assignment
#
# (The above is a contrived example since it works only if the previous
# command line included an assignment, but you get the idea.)
if [[ -z "$NUMERIC" ]]
then
emulate -L zsh
setopt extendedglob
local lastcmd pattern
integer cursor=$CURSOR # Remember cursor position
zle up-history || return 1 # Retrieve previous command
lastcmd=( ${(z)BUFFER} ) # Split into shell words
zle down-history # Return to current command
CURSOR=$cursor # Restore cursor position
integer i=$#lastcmd
zstyle -s :$WIDGET match pattern ||
pattern='*[[:alpha:]/\\]*'
while ((i)); do
if [[ $lastcmd[i] == $~pattern ]]; then
LBUFFER="$LBUFFER$lastcmd[i]"
return 0
else
((--i))
fi
done
fi
zle .insert-last-word
---- 8< ---- cut ---- 8< ----
Note that this presently doesn't work right when the previous command line
contains a [[ ... ]] expression that uses one of the (#x) forms of extended
pattern matching, e.g. (#i) to ignore case. That's a bug in ${(z)...} (it
takes the # to be a comment introducer), so it should be fixed soon. If
this really bothers you in the meantime, try adding
local +h histchars=''
somewhere before the assignment to lastcmd -- but then it's broken for the
case of `setopt interactive_comments`, so choose your poison ...
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2000-07-12 8:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20000711140506.5143gmx1@mx14.gmx.net>
2000-07-11 17:29 ` Christoph Lange
2000-07-11 22:05 ` Vincent Lefevre
2000-07-11 23:04 ` Bart Schaefer
2000-07-12 8:26 ` Bart Schaefer [this message]
2000-07-12 16:38 ` Christoph Lange
2000-07-12 18:54 ` Bart Schaefer
2000-07-12 21:18 ` Christoph Lange
2000-07-12 22:33 ` 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=1000712082636.ZM9329@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-users@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).