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: Wed, 20 Aug 2014 13:00:45 -0500 [thread overview]
Message-ID: <CABwHSOuvhUUM5ucMQuKwU9WmYPqEqepzfB79qE9z25AJFOzTRQ@mail.gmail.com> (raw)
In-Reply-To: <CAGMcHPr3BppH=-Oz=1D0xe2BG3ERcFitCXb8i1sEf=CWG-m_3g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]
Thanks for the suggestion. I really wish acme were just fixed. I find
acme a beautiful editor. A small number of issues render the editor too
much of a hassle to use for me. It is a shame because I really like it.
It is clean, simple, easy to learn, and powerful.
Thanks.
Blake
On Wed, Aug 20, 2014 at 4:03 AM, Riddler <riddler876@gmail.com> wrote:
> Perhaps making the tagline a special case where acme will read from the
> left to the bar | and use that for the file/directory name.
>
> You would still have to chord it elsewhere but it might fix the most
> annoying issue (inability to one click put etc)
>
> Thoughts?
> On 19 Aug 2014 21:40, "Blake McBride" <blake@mcbride.name> wrote:
>
>> 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: 2611 bytes --]
next prev parent reply other threads:[~2014-08-20 18: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
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 [this message]
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=CABwHSOuvhUUM5ucMQuKwU9WmYPqEqepzfB79qE9z25AJFOzTRQ@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).