From: Nemo <nemo@lsub.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Question about o/mero -> o/live event notification mechanism
Date: Wed, 2 May 2012 17:02:02 +0200 [thread overview]
Message-ID: <1870B378-FCFA-432E-852F-65C26D42F387@lsub.org> (raw)
In-Reply-To: <op.wdoo0wkz7pj5eq@thinkii>
On May 2, 2012, at 3:56 PM, aram wrote:
> % cat olive
>
> I receive nothing, whereas by executing
Because IIRC that file is used to speak a protocol.
That is, unless you issue certain requests on that file, o/mero
wont reply.
That's used to synchronize all o/lives so that they all perform
very much like in cooperative editing environments.
The ctls you saw in the comment are the protocol (merop).
prev parent reply other threads:[~2012-05-02 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 21:54 aram
2012-05-01 8:58 ` Nemo
2012-05-02 13:56 ` aram
2012-05-02 15:02 ` Nemo [this message]
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=1870B378-FCFA-432E-852F-65C26D42F387@lsub.org \
--to=nemo@lsub.org \
--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).