From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] simple question: multiple rename
Date: Tue, 16 Jun 2009 07:07:51 -0700 [thread overview]
Message-ID: <dd6fe68a0906160707u4557b8c9xe60f86ed0f9d74ec@mail.gmail.com> (raw)
In-Reply-To: <ec42638ffc30876c4d075f0220cb5bd1@quanstro.net>
the easiest thing to do is not use spaces in
your file names, even if others do in theirs.
most people take that approach, even on unix,
and it works fine.
if you are worried about names with spaces
and want to make a script more robust, then
the simplest option is to set ifs='
'
while you are manipulating the file names
with `{} commands. spaces may be allowed
but newlines most certainly are not. i keep
nl='
'
in my profile specifically so i can say ifs=$nl.
> using ws in filenames is a fossil-only problem;
> kfs, cwfs and ken's fs won't allow it.
gee, i'm pretty sure i read somewhere that
plan 9 lets any program be a file server ...
>> So what happens when you drawterm from a un*x box or access a VFAT partition?
>
> nothing. i'm running ken's fs, so from drawterm ...
the question (quoted) was about talking to non-plan 9
file systems, i.e. a linux or windows /mnt/term or
a dossrv disk.
if you are trying to disallow space you'd have
to fiddle with every file server you could possibly
talk to, or you'd have to edit the kernel.
the barn door has been open for a decade.
it's very late to be talking about closing it.
http://swtch.com/cgi-bin/plan9history.cgi?f=1999/0323/port/chan.c;v=diff;e=1
russ
next prev parent reply other threads:[~2009-06-16 14:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 19:58 Rudolf Sykora
2009-06-05 20:04 ` Martin Harriss
2009-06-05 20:07 ` Rudolf Sykora
2009-06-08 7:50 ` Rudolf Sykora
2009-06-08 9:35 ` Russ Cox
2009-06-16 11:51 ` roger peppe
2009-06-16 12:00 ` erik quanstrom
2009-06-16 12:43 ` Ethan Grammatikidis
2009-06-16 12:52 ` erik quanstrom
2009-06-16 14:07 ` Russ Cox [this message]
2009-06-16 14:40 ` erik quanstrom
2009-06-16 23:00 ` Ethan Grammatikidis
2009-06-16 23:01 ` erik quanstrom
2009-06-17 14:34 ` Ethan Grammatikidis
2009-06-18 22:54 ` John Floren
2009-06-18 22:59 ` erik quanstrom
2009-06-16 15:48 ` Charles Forsyth
2009-06-16 15:31 ` erik quanstrom
2009-06-16 22:57 ` Ethan Grammatikidis
2009-06-16 15:55 ` john
2009-06-16 17:19 ` Tim Newsham
2009-06-16 23:05 ` Ethan Grammatikidis
2009-06-08 9:45 ` Martin Neubauer
2009-06-08 10:40 ` Rudolf Sykora
2009-06-16 18:34 Francisco J Ballesteros
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=dd6fe68a0906160707u4557b8c9xe60f86ed0f9d74ec@mail.gmail.com \
--to=rsc@swtch.com \
--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).