9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Noah Evans <noah.evans@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 12:50:00 +0200	[thread overview]
Message-ID: <56a297000907270350k8ab416bw7fb0f67566bc3c65@mail.gmail.com> (raw)
In-Reply-To: <56a297000907270347t2779c4a9g51594ca6d2fc1596@mail.gmail.com>

That doesn't work because B ends after it plumbs the file to acme. CVS
will think that you're done. You need something like p9p's ipso.

On Mon, Jul 27, 2009 at 12:47 PM, Noah Evans<noah.evans@gmail.com> wrote:
> That doesn't work because B ends after it plumbs the file to acme. CVS
> will think that you're done. You need some
>
> On Mon, Jul 27, 2009 at 11:38 AM, Sape
> Mullender<sape@plan9.bell-labs.com> wrote:
>> Take a look at B, which can be used to send a file
>> to acme.  Also you may want to familiarize yourself with plumb.
>>
>>
>>> Hello,
>>>
>>> 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.
>>>
>>>       Aaron W. Hsu
>>>
>>> --
>>> Of all tyrannies, a tyranny sincerely exercised for the good of its
>>> victims may be the most oppressive. -- C. S. Lewis
>>
>>
>>
>



  reply	other threads:[~2009-07-27 10:50 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 [this message]
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
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=56a297000907270350k8ab416bw7fb0f67566bc3c65@mail.gmail.com \
    --to=noah.evans@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).