From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] PATCH walk(1) to (optionally) quote name and path
Date: Sat, 12 Aug 2023 15:40:19 -0400 [thread overview]
Message-ID: <C764810ADEF4238B5E7A15F68D93DC4B@eigenstate.org> (raw)
In-Reply-To: <E80EFEEC53D609B9C4EE4313761FFFB3@smtp.pobox.com>
Quoth unobe@cpan.org:
> I realized I didn't reply to your question, sorry. No, not directly.
> I am trying to consolidate some files spread across different paths to
> one directory, so first doing:
>
> walk -f -eP | grep 'pattern' > /tmp/files_of_interest.txt
>
> Then after reviewing and deleting further, I was going to do something like:
>
> clone `{cat /tmp/files_of_interest.txt} /path/
in this case, rc doesn't evaluate the quotes, it simply splits
on spaces (or whatever ifs is).
> Are you thinking I'd do something like set the ifs manually?
>
> ifs='
> '
> clone `{cat /tmp/files_of_interest.txt} /path
>
yes; though I tend to use the inline version, since
it has fewer warts around nested shell functions.
nl='
'
clone `$nl{cat /tmp/files} /path
next prev parent reply other threads:[~2023-08-12 19:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 3:25 Romano
2023-08-12 5:46 ` ori
2023-08-12 6:34 ` unobe
2023-08-12 6:44 ` unobe
2023-08-12 19:40 ` ori [this message]
2023-08-12 20:07 ` unobe
2023-08-12 13:21 ` hiro
2023-08-12 20:11 ` unobe
2023-08-13 20:10 ` hiro
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=C764810ADEF4238B5E7A15F68D93DC4B@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.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.
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).