zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh-users List <zsh-users@sunsite.dk>
Subject: Re: Tip of the day: previous command output
Date: Thu, 19 Aug 2004 08:20:17 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.61.0408190748530.9464@toltec.zanshin.com> (raw)
In-Reply-To: <20040819085812.GL22962@localhost>

On Thu, 19 Aug 2004, Jesper Holmberg wrote:

> The motivation for the following snippet is the fact that I often do a 
> 'find' or a 'locate' to find some files I'm interested in, and then want 
> to do some action on one of the files I just found.
[...]
> What this does is that it repeats the previous command, saving the output
> in a string.

I use this little function [*] for a similar purpose:

    keep () {
        kept=()		# Erase old value in case of error on next line
        kept=($~*)
        print -Rc - $kept
    }
    alias keep='noglob keep '

Note that "kept" is deliberately not declared local.

E.g. I might do

     patch < zsh-workers_NNNN.diff
     keep **/*.(orig|rej)
     emacs ${${kept:#*.orig}:r}
     rm $kept

That way I don't have to redo the possibly-expensive recursive glob twice;
the result is all stashed in $kept where I can manipulate the file names
and pick out the ones I want to work on.

I haven't bothered to combine it with a completion key because I hardly
ever want one specific file or its unmodified name; I almost always end up
typing some kind of parameter substitution expression.


[*] OK, I'm fibbing.  I actually call it "show" but there's an MH command
by that name that zsh may try to do completion for, so I changed the name
for public consumption.


  reply	other threads:[~2004-08-19 15:23 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 [this message]
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
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.0408190748530.9464@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).