From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] rc and spaces in file names
Date: Fri, 20 Dec 2013 10:01:43 -0500 [thread overview]
Message-ID: <672a388b53a7dc22063d0fc83568960a@mikro> (raw)
In-Reply-To: <52b457e6.hhwWXIxhk39u6dMd%trebol55555@aol.com>
On Fri Dec 20 09:48:29 EST 2013, trebol55555@aol.com wrote:
> Ok, thanks to both. I got confused with this part of rc(1):
>
> `{command}
> rc executes the command and reads its standard output,
> splitting it into a list of arguments, using characters
> in $ifs as separators. If $ifs is not otherwise set,
> its value is ' \t\n'.
that's a good point. it looks like the wrong conventions were applied
to that string. ironically, one would guess, this was to solve a
readability problem. perhaps "... otherwise set, space, newline, tab will
be used as separators" would be more precice even if it doesn't read
as well.
- erik
next prev parent reply other threads:[~2013-12-20 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 14:44 trebol
2013-12-20 15:01 ` erik quanstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-20 14:14 trebol
2013-12-20 14:25 ` erik quanstrom
2013-12-20 14:25 ` Tristan
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=672a388b53a7dc22063d0fc83568960a@mikro \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).