From: Blake McBride <blake@mcbride.name>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Acme: spaces in file names
Date: Tue, 19 Aug 2014 15:37:09 -0500 [thread overview]
Message-ID: <CABwHSOv398bW1kSJc4oW_4U0cD8MU82so3++J0wkWK1s_9aJSw@mail.gmail.com> (raw)
In-Reply-To: <CAK4xykW2bmvVt4PKsAb0OK9aF5XoVACnar_OBaKdLtROE5ADsg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 751 bytes --]
B 'some directory name with spaces'
does load the directory correctly. But as soon as you put the cursor into
the directory acme changes the buffer header from "some directory name with
spaces" to "some". Not supporting space in file/directory names has been
the single biggest impediment to my use of acme.
I noticed Wily doesn't have this problem. Of course it is missing win,
Edit, Tab, etc....
Thanks.
Blake
On Sun, Dec 15, 2013 at 1:39 PM, andrey mirtchovski <mirtchovski@gmail.com>
wrote:
> with the plumber running, issuing "B /anyfile" will open the file in
> acme, even if acme isn't running. this is very useful when you start
> scripting little tools.
>
> i think this covers everything about acme :)
>
>
[-- Attachment #2: Type: text/html, Size: 1194 bytes --]
next prev parent reply other threads:[~2014-08-19 20:37 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
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 [this message]
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=CABwHSOv398bW1kSJc4oW_4U0cD8MU82so3++J0wkWK1s_9aJSw@mail.gmail.com \
--to=blake@mcbride.name \
--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).