From: zzapper <david@tvis.co.uk>
To: zsh-users@sunsite.dk
Subject: Re: file names in arrays
Date: Mon, 04 Jul 2005 13:06:04 +0100 [thread overview]
Message-ID: <fa9ic19jnhim7v5udgq91v2mo2uh9bimre@4ax.com> (raw)
In-Reply-To: <1050702205137.ZM4701@candle.brasslantern.com>
On Sat, 02 Jul 2005 20:51:37 +0000, wrote:
>On Jun 30, 4:51pm, zzapper wrote:
>}
>} At the risk of being abused, RTFM etc etc
>}
>} Has anyone got a script where a number of file names resulting from
>} say a find/grep are loaded into an array.
>
>Go to http://www.zsh.org/cgi-bin/mla/wilma/users and search for "keeper".
>
>} And then this array is looped thru with a promt deciding what might
>} happen to these files, mv,rm,cp edit etc
>
>Isn't the answer to this the same as -- or awfully similar to, at any
>rate -- the answer to your "Creating a Case statement dynamically"
>thread from a couple of days earlier?
>
>
> local file command target
> find "$@" | keep
> for file in $kept
> do
> PS3="Action on $file: "
> target=''
> select command in mv cp rm gvim
> do
> case $REPLY in
> ((Q|q)*) break 2;;
> (<1->)
> case $command in
> (cp|mv) vared -e -p "$command $file " target &&
> [[ -n $target ]] && $command $file $target
> (?*) $command $file;;
> (*) break;;
> esac;;
> (*) break;;
> esac
> done
> done
Bart,
Yes it's similar to my previous thread, but hopefully more general. I'd found a useful solution, but
didn't use arrays, so I ended up repeating operations.
Your script above blows up for me on
pick3:17: parse error near `$command' (the vared line)
zsh 4.2.4 (i686-pc-cygwin)
--
zzapper
vim -c ":%s%s*%Cyrnfr)fcbafbe[Oenz(Zbbyranne%|:%s)[[()])-)Ig|norm Vg?"
http://www.rayninfo.co.uk/tips/ vim, zsh & success tips
next prev parent reply other threads:[~2005-07-04 12:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 15:51 zzapper
2005-06-30 17:12 ` Philippe Troin
2005-07-02 20:51 ` Bart Schaefer
2005-07-04 12:06 ` zzapper [this message]
2005-07-04 14:09 ` Bart Schaefer
2005-07-04 15:31 ` zzapper
2005-07-04 17:33 ` 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=fa9ic19jnhim7v5udgq91v2mo2uh9bimre@4ax.com \
--to=david@tvis.co.uk \
--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).