From: Daimrod <email@example.com>
To: "François Pinard" <firstname.lastname@example.org>
Subject: Re: colorg: Some news!
Date: Mon, 21 Jan 2013 06:50:52 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (=?utf-8?Q?=22Fran=C3=A7ois?= Pinard"'s message of "Mon, 21 Jan 2013 00:30:28 -0500")
[-- Attachment #1: Type: text/plain, Size: 1651 bytes --]
François Pinard <email@example.com> writes:
> Hi to all my Org friends.
> ColOrg is a project about real-time collaborative editing of Org files.
> Here are some news about its progress, after a second push this
> weekend. It is not usable yet, but a few more steps have been taken. A
> few more ropes are needed to tie it up all together, but not much.
> Some details follow.
> The ColOrg client (on the Emacs side) acquired code for processing all
> commands coming from a ColOrg server. This includes per-collaborator
> colorization of recently inserted text, and notification windows for
> transient diagnostics. To be usable, the client still misses the
> association between local buffers and remote resource numbers, so
> modifications go where they were meant. The client should also ask the
> server to build completions for existing users or resources.
> The ColOrg server (on the Python side) requires more work. The protocol
> has been solidified a bit, but needs some love in the area of returned
> values. The problem of proper command rewriting is now better analyzed,
> it looks simpler, but still has to be programmed. I decided for a naive
> approach, and by postponed optimization issues, all dark corners have
> been lit, none remain so far that I know.
> The Wiki also got some more text. See https://github.com/pinard/ColOrg.
That's a really cool project! Do you plan to keep the server in Python?
Or do you think it would be possible to make this in Emacs Lisp only
with Elnode for the server-side?
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2013-01-21 5:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 5:30 colorg: Some news! François Pinard
2013-01-21 5:50 ` Daimrod [this message]
2013-01-21 15:53 ` François Pinard
2013-01-21 16:28 ` Daimrod
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).