From: "François Pinard" <pinard@iro.umontreal.ca>
To: emacs-orgmode@gnu.org
Cc: "Jean Schurger" <jean@schurger.org>,
"Aurélien Bondis" <abondis@ubity.com>
Subject: colorg: Weekly status!
Date: Mon, 28 Jan 2013 01:36:08 -0500 [thread overview]
Message-ID: <86mwvtq0fb.fsf@iro.umontreal.ca> (raw)
Hi, my Org friends.
The colorg project is about real-time collaborative editing of Org
files. The project progresses a bit on each weekend only, but I
seemingly cannot find free hours elsewhere in the week! Here is the
status after three weeks.
The parts slowly begin to fit together. I can launch a colorg server
and two Emacs sessions. In the first Emacs, I can upload a buffer
contents to the server as a resource. In the second Emacs, I can either
download that resource from the server into a empty buffer, or associate
it with a buffer already having identical contents. Then, making edits
to any Emacs go to the other. That's a start!
Take note that the tool is still unusable however, as the resolution
clashing code in the server still has to be implemented, it only works
when editing in disjoint areas. On a local Git branch, I have some
Emacs Lisp code to multiplex many buffers to many servers (or one), but
bugs remain, so I did not merge that branch yet.
I adjusted the documentation on https://github.com/pinard/colorg/wiki .
The Usage page has a list of known problems (remaining things to do).
Keep happy all!
François
P.S. When modifications clash, a region should never be deleted more
than once, and insertions should all be kept, so no work is lost
unexpectedly. This has consequences on the later alterations coming in
the same batches, and this is where the complexity lies. Not very
difficult (so far that I can see), but quite tedious to do correctly.
I'll come to it, hopefully.
next reply other threads:[~2013-01-28 6:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 6:36 François Pinard [this message]
2013-01-28 15:13 ` colorg: Weekly status! Loyall, David
2013-01-28 17:10 ` François Pinard
2013-01-30 10:57 ` Bastien
2013-01-30 16:08 ` François Pinard
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86mwvtq0fb.fsf@iro.umontreal.ca \
--to=pinard@iro.umontreal.ca \
--cc=abondis@ubity.com \
--cc=emacs-orgmode@gnu.org \
--cc=jean@schurger.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).