From: Tristan <9p-st@imu.li>
To: 9fans@9fans.net
Subject: Re: [9fans] rc and spaces in file names
Date: Fri, 20 Dec 2013 09:25:25 -0500 [thread overview]
Message-ID: <257c47.19da62f2.Uf8U.mx@tumtum.plumbweb.net> (raw)
In-Reply-To: <52b450b5.5jJHH5Wi3lSMdJj+%trebol55555@aol.com>
> term% ifs='\n' for(i in Plan*){cp $i `{echo $i | sed 's/lan/LAN/'}}
> cp: can't create PLAN 9
> : bad character in file name: 'PLAN 9
> '
> cp: can't create PLAN B
> : bad character in file name: 'PLAN B
> '
> '
> So the last newline character is added to the file name...
> I tried typing a literal newline in the ifs variable and it works:
> term% ifs='
> ' for(i in Plan*){cp $i `{echo $i | sed 's/lan/LAN/'}}
> term% ls P*
> 'PLAN 9'
> 'PLAN B'
> 'Plan 9'
> 'Plan B'
> With p9p is the same. I'll appreciate If anyone can tell me why.
rc doesn't do backslash escapes.
tristan
--
All original matter is hereby placed immediately under the public domain.
next prev parent reply other threads:[~2013-12-20 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 14:14 trebol
2013-12-20 14:25 ` erik quanstrom
2013-12-20 14:25 ` Tristan [this message]
2013-12-20 14:44 trebol
2013-12-20 15:01 ` erik quanstrom
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=257c47.19da62f2.Uf8U.mx@tumtum.plumbweb.net \
--to=9p-st@imu.li \
--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).