9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: hugo rivera <uair00@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Acme and spaces in file names
Date: Fri, 13 Feb 2009 11:07:21 +0100	[thread overview]
Message-ID: <138575260902130207k17da0327k5010b7e883c8d2f9@mail.gmail.com> (raw)
In-Reply-To: <8ccc8ba40901140808x1e2da066sed64df0b8a63edc0@mail.gmail.com>

I couldn't find anything in /n/sources/contrib/nemo. Can you please
copy it again?


2009/1/14 Francisco J Ballesteros <nemo@lsub.org>:
> trfs.
> We're using it within the 9fs script so everything can use it.
>
> I think it must be in /n/sources/contrib/nemo
> somewhere (it was part of Plan B).
>
> If you cannot find it just drop me a line and I'll copy it again.
>
> On Wed, Jan 14, 2009 at 4:39 PM, Robert Raschke <rtrlists@googlemail.com> wrote:
>> On Wed, Jan 14, 2009 at 2:26 PM, hugo rivera <uair00@gmail.com> wrote:
>>> Hi guys,
>>> I realized that acme gets confused when handling files with spaces in
>>> their names, is there an easy way to handle this?
>>> I mean, for example, when I paint a file name with an space on it,
>>> using the left click, it would be nice that acme could open that file.
>>> Obviously removing spaces from my file names is a solution, but can
>>> acme handle this by its own?
>>
>> There exists a 9P wrapper that you can slot between your normal fs and
>> Acme that will translate characters. I'm not sure what it's called, or
>> where it lives. Sorry.
>>
>> The Acme SAC (based on Inferno) uses this automatically and maps
>> spaces to little "space" characters (␣).
>>
>> Robby
>>
>



-- 
Saludos

Hugo



  reply	other threads:[~2009-02-13 10:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14 14:26 hugo rivera
2009-01-14 15:39 ` Robert Raschke
2009-01-14 16:08   ` Francisco J Ballesteros
2009-02-13 10:07     ` hugo rivera [this message]
2009-02-13 10:13       ` Fco. 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=138575260902130207k17da0327k5010b7e883c8d2f9@mail.gmail.com \
    --to=uair00@gmail.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).