From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: From: =?ISO-8859-1?Q?Rub=E9n_Berenguel?= Date: Thu, 12 Dec 2013 18:00:13 +0100 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=e89a8ff1c462a919bd04ed59485a Subject: Re: [9fans] Acme: spaces in file names Topicbox-Message-UUID: 97fcd5c8-ead8-11e9-9d60-3106f5b1d025 --e89a8ff1c462a919bd04ed59485a Content-Type: text/plain; charset=ISO-8859-1 A kind of crude workaround is using the whole /Users/whatever/file with spaces, selecting it with first button and 1-2 chording it to Get. This works on Mac, problem is that it's quite horrible to do. An intermediate solution may be to use some piping rule like sp:filename with spaces, but I don't remember if piping works with right-button and selected text or follows the same rules as opening a file. Ruben On Thu, Dec 12, 2013 at 5:53 PM, Robert Raschke wrote: > Someone once made a little filesystem that would substitute spaces in > filenames with a different character. When placed between the normal fs and > Acme, this would make things work quite nicely. > > If I remember correctly, Acme-SAC (built on top of Inferno) does that by > default. > > No idea where you can find such a fs for Mac though. But this might give > you a start. > > Robby > On Dec 11, 2013 6:19 PM, "Blake McBride" wrote: > >> Greetings, >> >> Just started using acme (and sam). Cool. >> >> I am using acme on a Mac form plan9port. >> >> Within a file list one can right-click a listing in order to decend into >> another directory or load a file. The problem is that neither work if a >> space is contained within the name. Apparently, the right-click >> functionality only looks at non-white space strings. An easy fix to this >> would be to allow the user to highlight the entire string (including >> spaces) and then right-click as normal. The system would allow the >> highlight facility to override the "just test for contigous non-space >> string" current functionality. >> >> Any thoughts on this? >> >> Thanks. >> >> Blake McBride >> >> --e89a8ff1c462a919bd04ed59485a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
A kind of crude workaround is using the whole /Users/whate= ver/file with spaces, selecting it with first button and 1-2 chording it to= Get. This works on Mac, problem is that it's quite horrible to do. An = intermediate solution may be to use some piping rule like sp:filename with = spaces, but I don't remember if piping works with right-button and sele= cted text or follows the same rules as opening a file.

Ruben


On Thu, Dec 12, 2013 at 5:53 PM, Robert Raschke <= rtrlists@googlemail.com> wrote:

Someone once made a little filesystem tha= t would substitute spaces in filenames with a different character. When pla= ced between the normal fs and Acme, this would make things work quite nicel= y.

If I remember correctly, Acme-SAC (built on top of Inferno) does that by= default.

No idea where you can find such a fs for Mac though. But this might give= you a start.

Robby

On Dec 11, 2013 6:19 PM, "Blake McBride&quo= t; <blake@mcbrid= e.name> wrote:
Greetings,

Just started using acme (and= sam). =A0Cool.

I am using acme on a Mac form plan= 9port.

Within a file list one can right-click a li= sting in order to decend=A0into another directory or load a fi= le. =A0The problem is that neither work if a space is contained within the = name. =A0Apparently, the right-click functionality only looks at non-white = space strings. =A0An easy fix to this would be to allow the user to highlig= ht the entire string (including spaces) and then right-click as normal. =A0= The system would allow the highlight facility to override the "just te= st for contigous=A0non-space string" current functionalit= y.

Any thoughts on this?

Thanks.<= /div>

Blake McBride


--e89a8ff1c462a919bd04ed59485a--