From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <86ipu0evi2.fsf@cmarib.ramside> <201104262052.36817.dexen.devries@gmail.com> Date: Tue, 26 Apr 2011 12:35:14 -0700 Message-ID: From: Paul Lalonde To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=90e6ba613b7057852004a1d76c16 Subject: Re: [9fans] spaces in filenames Topicbox-Message-UUID: d624f940-ead6-11e9-9d60-3106f5b1d025 --90e6ba613b7057852004a1d76c16 Content-Type: text/plain; charset=ISO-8859-1 I mostly run acme from inferno (acme-SAC), and live with trfs to take care of my windows and mac paths. My linux paths are much better behaved, and so I run from p9p there. Paul On Tue, Apr 26, 2011 at 12:31 PM, Rob Pike wrote: > I still use acme. My solution for spaces in file names is to avoid > them. That might not work for everyone. > > -rob > > -- I'm migrating my email. plalonde@telus.net will soon be disconnected. Please use paul.a.lalonde@gmail.com from now on. --90e6ba613b7057852004a1d76c16 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I mostly run acme from inferno (acme-SAC), and live with trfs to take care = of my windows and mac paths. =A0My linux paths are much better behaved, and= so I run from p9p there.

Paul

On Tue, Apr 26, 2011 at 12:31 PM, Rob Pike <robpike@gmail.com> wrote:
I still use acme. =A0My solution for spaces in file names is to avoid
them. =A0That might not work for everyone.

-rob




--
I'm mig= rating my email. =A0plalonde@telus.net will soon be disconnected. =A0Please use paul.a.lalonde@gmail.co= m from now on.


--90e6ba613b7057852004a1d76c16--