From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@sunsite.dk
Subject: Re: Tip of the day: previous command output
Date: Fri, 20 Aug 2004 22:58:07 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0408202230290.2395@toltec.zanshin.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0408200905300.27591@toltec.zanshin.com>
On Fri, 20 Aug 2004, Bart Schaefer wrote:
> I won't try to test this, but something like this should do it:
OK, I lied. I tested it. It didn't do what I expected, though it did
what I told it to do.
Here's a version that actually does what was asked:
_expand_word_and_keep() {
function compadd() {
local -A args
zparseopts -E -A args J:
if [[ $args[-J] == all-expansions ]]
then
builtin compadd -A kept "$@"
kept=(${(Q)${(z)kept}})
fi
builtin compadd "$@"
}
local result
_main_complete _expand
result=$?
unfunction compadd
return result
}
With 4.2.1, you can replace the five "local ... return" lines with
{ _main_complete _expand } always { unfunction compadd }
Left as an excercise: Get the name of the "keep" variable from a zstyle,
so you can stash expansions in different places depending on context.
next prev parent reply other threads:[~2004-08-21 6:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 8:58 Jesper Holmberg
2004-08-19 15:20 ` Bart Schaefer
2004-08-19 16:42 ` Andy Spiegl
2004-08-19 17:16 ` Bart Schaefer
2004-08-20 9:30 ` Andy Spiegl
2004-08-20 11:13 ` Vincent Lefevre
2004-08-20 12:12 ` Andy Spiegl
2004-08-20 14:50 ` Vincent Lefevre
2004-08-21 4:25 ` Bart Schaefer
2004-08-21 5:58 ` Bart Schaefer [this message]
2004-08-21 17:06 ` Bart Schaefer
2004-08-22 20:58 ` Vincent Lefevre
2004-08-23 1:10 ` Bart Schaefer
2004-08-23 13:51 ` Vincent Lefevre
2004-08-22 21:21 ` Vincent Lefevre
2004-08-22 23:03 ` Bart Schaefer
2004-08-23 13:00 ` Vincent Lefevre
2004-08-23 15:21 ` Bart Schaefer
2004-08-23 19:14 ` Vincent Lefevre
2004-08-26 23:16 ` Andy Spiegl
2004-08-27 0:43 ` Bart Schaefer
2004-08-27 10:21 ` Andy Spiegl
2004-08-31 15:03 ` zzapper
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=Pine.LNX.4.61.0408202230290.2395@toltec.zanshin.com \
--to=schaefer@brasslantern.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).