From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
From: nemo@plan9.escet.urjc.es
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 'find'
Date: Thu, 3 Jul 2003 12:03:38 +0200 [thread overview]
Message-ID: <e9978de894af74e10f353e7704a2bfbe@plan9.escet.urjc.es> (raw)
In-Reply-To: <3F00600D.4060005@null.net>
[-- Attachment #1: Type: text/plain, Size: 322 bytes --]
Dont know if it was good or bad.
What I know is that I ended up using trfs
because in the end 'this stuff' didnt work
as expected (think of acme and others).
Sure, it's not perfect, but I need no extra
options, and all the programs work as
expected (while at the same time they remain
using blanks all the times).
[-- Attachment #2: Type: message/rfc822, Size: 2260 bytes --]
From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 'find'
Date: Thu, 3 Jul 2003 09:42:20 GMT
Message-ID: <3F00600D.4060005@null.net>
rog@vitanuova.com wrote:
> and i guess awk printf should be given a %q option
> and maybe echo should have a -q option too
> and du should print its output quoted
> and pwd should too
> and maybe cp should have an option ...
Does this suggest why quoting (prompted by a limitation
at the "shell" level) was the wrong idea?
next prev parent reply other threads:[~2003-07-03 10:03 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-29 16:57 D. Brownlee
2003-06-29 16:59 ` Sape Mullender
2003-06-30 14:07 ` rog
2003-06-30 14:18 ` Scott Schwartz
2003-06-30 14:50 ` rog
2003-07-03 9:42 ` Douglas A. Gwyn
2003-07-03 10:03 ` Fco.J.Ballesteros, nemo [this message]
2003-07-03 15:14 ` rob pike, esq.
2003-07-03 12:57 ` matt
2003-07-03 16:59 ` Douglas A. Gwyn
2003-07-03 17:09 ` matt
2003-06-30 15:30 ` Dan Cross
2003-07-03 12:11 ` Kenji Arisawa
2003-06-29 18:11 ` Jack Johnson
2003-06-29 18:42 ` Dan Cross
2003-07-04 14:08 ` Ralph Corderoy
2003-07-05 18:38 ` Dan Cross
2003-07-06 3:11 ` boyd, rounin
2003-07-07 8:33 ` Douglas A. Gwyn
2003-07-07 10:49 ` boyd, rounin
2003-07-07 14:05 ` Douglas A. Gwyn
2003-07-07 15:46 ` rob pike, esq.
2003-07-07 19:18 ` Dan Cross
2003-07-07 19:26 ` David Presotto
2003-07-07 19:46 ` Dan Cross
2003-07-07 19:08 ` Dan Cross
2003-07-07 19:21 ` Dan Cross
2003-07-08 8:31 ` Douglas A. Gwyn
2003-07-08 11:20 ` Dan Cross
2003-07-06 16:12 ` Jack Johnson
2003-07-06 22:20 ` matt
2003-07-07 13:28 ` Ralph Corderoy
2003-07-07 19:13 ` Dan Cross
2003-06-30 7:47 ` Fco.J.Ballesteros, nemo
2003-06-30 7:55 ` boyd, rounin
2003-06-30 14:32 ` Dan Cross
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=e9978de894af74e10f353e7704a2bfbe@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--cc=9fans@cse.psu.edu \
/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).