From: "Rubén Berenguel" <ruben@mostlymaths.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Acme: spaces in file names
Date: Thu, 12 Dec 2013 18:00:13 +0100 [thread overview]
Message-ID: <CAHk2O6rG-8WqW9B=Ech6kgKDH+GYS4u4vi-v7ExOByTfOFe5_Q@mail.gmail.com> (raw)
In-Reply-To: <CAH+xwdANOMBCq6zCGv+z-6+v9ZuRPerSxC+cC-g2XC38-RgKAQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1733 bytes --]
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 <rtrlists@googlemail.com>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" <blake@mcbride.name> 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
>>
>>
[-- Attachment #2: Type: text/html, Size: 2456 bytes --]
next prev parent reply other threads:[~2013-12-12 17:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 18:17 Blake McBride
2013-12-12 16:53 ` Robert Raschke
2013-12-12 17:00 ` Rubén Berenguel [this message]
2013-12-12 21:10 ` Blake McBride
2013-12-15 15:25 ` Blake McBride
2013-12-15 15:38 ` Friedrich Psiorz
2013-12-15 16:19 ` Blake McBride
2013-12-15 16:26 ` Friedrich Psiorz
2013-12-15 16:38 ` Blake McBride
2013-12-15 17:51 ` Friedrich Psiorz
2013-12-15 17:56 ` Blake McBride
2013-12-15 19:39 ` andrey mirtchovski
2014-08-19 20:37 ` Blake McBride
2014-08-20 9:03 ` Riddler
2014-08-20 18:00 ` Blake McBride
2014-08-21 15:32 ` Skip Tavakkolian
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='CAHk2O6rG-8WqW9B=Ech6kgKDH+GYS4u4vi-v7ExOByTfOFe5_Q@mail.gmail.com' \
--to=ruben@mostlymaths.net \
--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).