zsh-users
 help / color / mirror / code / Atom feed
From: "Jesper Nygårds" <jesper.nygards@gmail.com>
To: zsh-users@zsh.org
Subject: Completing all possible candidates
Date: Fri, 11 Jan 2013 12:30:56 +0100	[thread overview]
Message-ID: <CABZhJg9jVc1PRX0T7p6XR3sc87oszM0hKQSeYAJnZb52Vp36xQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]

For quite a while, I've used the following when I want completion from the
output of a previous command:

_my-prev-result() {
    local hstring
    # Run last command again, save output
    hstring=$(eval $(fc -l -n -1))
    # Split items on new-line into an array, quote each item
    compadd - ${(@f)hstring}
}

zle -C my-prev-comp menu-complete _my-prev-result
bindkey '\ee' my-prev-comp

zle -C my-rev-prev-comp reverse-menu-complete _my-prev-result
bindkey '\eE' my-rev-prev-comp

This allows me to for example use "locate foo", and then complete the next
command with the found files (the drawback is of course that the previous
command could take a while to run). I know about the  "keeper" functions in
the zsh distribution, but this is simpler.

Anyway, I recently realized that I sometimes could have use for putting ALL
the possibilities on the command line with a keystroke, à la the
"all-matches" example under _all_matches in the zsh manual.

In fact, I suspect the _all_matches completer should be involved somehow,
but I have failed to find out how.

Simply stated, I want a key that says: "run the previous command line, and
put all the resulting output on the command line". How to do this?

             reply	other threads:[~2013-01-11 11:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11 11:30 Jesper Nygårds [this message]
2013-01-11 14:32 ` Bart Schaefer
2013-01-15  7:28   ` Jesper Nygårds
2013-01-17  3:14     ` Bart Schaefer
2013-01-17  6:28       ` Jesper Nygårds
  -- strict thread matches above, loose matches on Subject: below --
2012-04-03 19:08 Large LS_COLORS makes auto_cd very slow Jesper Nygårds
2012-04-04  7:52 ` Bart Schaefer
2012-04-04 16:57   ` Jesper Nygårds
2012-04-05  9:30   ` Václav Zeman
2012-04-05 15:51     ` Bart Schaefer
2012-04-05 16:33       ` Bart Schaefer
2012-04-05 17:00         ` Philippe Troin
2012-04-06  9:49       ` Václav Zeman
2012-04-06 11:07         ` Mark van Dijk
2012-04-06 15:51         ` Bart Schaefer
2012-04-09  8:23         ` Václav Zeman
2012-04-09 19:28           ` Bart Schaefer
2012-04-06 18:30   ` Valodim Skywalker
2012-04-07 16:43     ` 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=CABZhJg9jVc1PRX0T7p6XR3sc87oszM0hKQSeYAJnZb52Vp36xQ@mail.gmail.com \
    --to=jesper.nygards@gmail.com \
    --cc=zsh-users@zsh.org \
    /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).