From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <20090616134331.e7114d5e.eekee57@fastmail.fm> Date: Tue, 16 Jun 2009 07:07:51 -0700 Message-ID: Subject: Re: [9fans] simple question: multiple rename From: Russ Cox To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Topicbox-Message-UUID: 0bc71a58-ead5-11e9-9d60-3106f5b1d025 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=3D' ' while you are manipulating the file names with `{} commands. spaces may be allowed but newlines most certainly are not. i keep nl=3D' ' in my profile specifically so i can say ifs=3D$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 parti= tion? > > nothing. =C2=A0i'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=3D1999/0323/port/chan.c;v=3Ddif= f;e=3D1 russ