emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "François Pinard" <pinard@iro.umontreal.ca>
To: emacs-orgmode@gnu.org
Subject: Re: Rudel - Real-Time collaborative editing of Org-Mode files
Date: Tue, 25 Dec 2012 15:02:18 -0500	[thread overview]
Message-ID: <86han9dho5.fsf@iro.umontreal.ca> (raw)
In-Reply-To: <86licmclle.fsf@iro.umontreal.ca> ("François Pinard"'s message of "Tue, 25 Dec 2012 08:22:53 -0500")

François Pinard <pinard@iro.umontreal.ca> writes:

> Bastien <bzg@altern.org> writes:

>> [...] let *anyone* write Org doc collaboratively and seemlessly.
>> Com'on, let's start something great :)

> It would be great indeed!

On the road this morning, I gave some thought on this problem, which
does not seem trivial at all, to me at least.  Unless taken under the
appropriate angle — which I do not know yet! — I think I see that many
design choices could trap developers in a maze of sad consequences.

Nevertheless, it might be an interesting problem.  Maybe it would be
worth seeking a few avenues on this mailing list, trying to find a
workable solution?  Would there be an interest for such a discussion?


  reply	other threads:[~2012-12-25 20:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-21 18:50 Rudel - Real-Time collaborative editing of Org-Mode files Ciaran Mulloy
2012-12-23 23:18 ` Bastien
2012-12-25 13:22   ` François Pinard
2012-12-25 20:02     ` François Pinard [this message]
2012-12-26 21:44       ` Eric Schulte
2012-12-27  2:18         ` François Pinard
2013-01-01 22:04           ` Torben Hoffmann
2013-01-12 14:47             ` François Pinard
2013-01-12 23:33               ` colorg: Protocol [was: Re: Rudel - Real-Time collaborative editing of Org-Mode files] François Pinard
2013-01-14 10:29                 ` Samuel Loury
2013-01-14 14:38                   ` François Pinard
2013-04-01 20:46                     ` Torben Hoffmann

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: 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=86han9dho5.fsf@iro.umontreal.ca \
    --to=pinard@iro.umontreal.ca \
    --cc=emacs-orgmode@gnu.org \


* 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).