Re: [9front] [PATCH 4/6] walk: quote name and path using N and P; use quotefmt and free()

[unobe@cpan.org]

Quoth ori@eigenstate.org:
> Quoth unobe@cpan.org:
> > I had sent an earlier version of this around August 10.  Moody helped
> > me on gridchat with some finer points, and figured I'd send it out
> > again along with the other patches I've been accumulating.
> 
> I think the last time this was brought up, I wasn't convinced
> of the need for a change here; the motivating example didn't
> actualy work. `{} doesn't evaluate quotes.
> 
> How do you plan to use this?
> 

For one, it has made it easier to plumb/send files.  It's not perfect
when a quote is in the filename because rio/acme doesn't span two
singlequotes when selecting, but it does make it faster for files with
other quoted characters, like spaces.  Most often through no fault of
my own, I have to deal with alien file names that have spaces.  So
when creating a script still using `\n like below, having the
output quoted makes it easy to select the file to plumb/send:
for (f in `'
'{walk-n 1 -emNs -f /usr/glenda}) echo $f
1660336534 acme.dump 0
1695882474 diff.patch 654
1695918225 'test this out' 0

Perhaps that could be why ls(1) has the default as quoting the file
name when needed, and yet does provide -Q for cases when that's not
desired.  This would give walk(1) a similar knob to turn.