From: "J.R. Mauro" <jrm8005@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Using Acme as an external Editor
Date: Mon, 27 Jul 2009 21:19:39 -0400 [thread overview]
Message-ID: <3aaafc130907271819y4c153150j7b2310e93a0d621@mail.gmail.com> (raw)
In-Reply-To: <dd6fe68a0907271122w1834cbfcwff848a996622e896@mail.gmail.com>
On Mon, Jul 27, 2009 at 2:22 PM, Russ Cox<rsc@swtch.com> wrote:
> On Mon, Jul 27, 2009 at 11:06 AM, Tim Newsham<newsham@lava.net> wrote:
>>> Is there some idiom or method for using Acme as an external editor to some
>>> other program? Say I want to use it as the editor that is spawned when I do
>>> a CVS commit to a system; how would I do this, or can this even be done? I'm
>>> using plan9ports, but I don't know how much of this question relates to
>>> what.
>>
>> I was playing with this exact problem recently. There's an easy way to send
>> a file to acme for editing -- the plumber. There's a downside, it doesn't
>> wait for the editor to save or complete. So.. you could plumb the file and
>> then wait for a save to happen, somehow, or you can write another program
>> that forces a new acme window with the contents of the file and waits for it
>> to either Put or Del. I wrote a small program to do this recently (see the
>> thread: http://9fans.net/archive/2009/06/290) which was a bit hacky, but
>> worked. I solicited some feedback on some questions and got some good
>> advice from Russ (http://9fans.net/archive/2009/06/292) but havent yet gone
>> back and applied it.
>
> I don't think you need to be that fancy.
> Lorenzo Bolla already pointed out E in this thread,
> and it exists exactly for this purpose.
>
> http://swtch.com/plan9port/man/man1/sam.html
> (description of E is at the end)
>
> Russ
>
>
One caveat about E: if you're paranoid like I am and save your file
many times while editing, E will not be terribly friendly until you
train yourself to save only when finished. (This is not a criticism of
E, it is merely a warning to people with my kind of idiosyncrasies)
next prev parent reply other threads:[~2009-07-28 1:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 9:31 Aaron W. Hsu
2009-07-27 9:38 ` Sape Mullender
2009-07-27 10:47 ` Noah Evans
2009-07-27 10:50 ` Noah Evans
2009-07-27 11:16 ` Lorenzo Bolla
2009-07-27 11:22 ` Steve Simon
2009-07-27 18:06 ` Tim Newsham
2009-07-27 18:22 ` Russ Cox
2009-07-28 1:19 ` J.R. Mauro [this message]
2009-07-28 6:55 ` sqweek
2009-07-28 22:43 ` J.R. Mauro
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=3aaafc130907271819y4c153150j7b2310e93a0d621@mail.gmail.com \
--to=jrm8005@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).