From: unobe@cpan.org
To: 9front@9front.org
Subject: Re: [9front] PATCH walk(1) to (optionally) quote name and path
Date: Fri, 11 Aug 2023 23:44:35 -0700 [thread overview]
Message-ID: <E80EFEEC53D609B9C4EE4313761FFFB3@smtp.pobox.com> (raw)
In-Reply-To: <14FD1A161954B653928B89F61F9F7510@eigenstate.org>
Quoth ori@eigenstate.org:
> Quoth Romano <unobe@cpan.org>:
> > I'm working with files on a backup drive that have spaces and
> > quotation marks in their names, using walk(1). I can pipe to sed
> > s/''''/''''''''''/g and do similarly for other characters requiring
> > escaping for rc(1), but figured patching walk(1) would be better.
>
> generally no objections, though it's usually relatively easy to
> structure scripts such that there's relatively little that is
> interpreted by rc; is this for interactive use?
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/
Are you thinking I'd do something like set the ifs manually?
ifs='
'
clone `{cat /tmp/files_of_interest.txt} /path
next prev parent reply other threads:[~2023-08-12 6:47 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 [this message]
2023-08-12 19:40 ` ori
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=E80EFEEC53D609B9C4EE4313761FFFB3@smtp.pobox.com \
--to=unobe@cpan.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).