Org-mode mailing list
 help / color / mirror / Atom feed
From: Daimrod <>
To: "François Pinard" <>
Subject: Re: colorg: Some news!
Date: Mon, 21 Jan 2013 06:50:52 +0100
Message-ID: <87obgjythf.fsf@casa.home> (raw)
In-Reply-To: <> (=?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 <> 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

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[1] for the server-side?

> François


[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

  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 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

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87obgjythf.fsf@casa.home \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Org-mode mailing list

This inbox may be cloned and mirrored by anyone:

	git clone --mirror list/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 list list/ \
	public-inbox-index list

Example config snippet for mirrors.
Newsgroups are available over NNTP:

AGPL code for this site: git clone