From: "Paul W. Rankin" <hello@paulwrankin.com>
To: Jean-Christophe Helary <brandelune@gmail.com>
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>,
Noam Postavsky <npostavs@gmail.com>
Subject: Re: collaborative editing in emacs on macos
Date: Thu, 18 Apr 2019 14:47:58 +1000 [thread overview]
Message-ID: <m2v9zbzzpd.fsf@paulwrankin.com> (raw)
In-Reply-To: <C2369AD9-8B99-49AE-9C7A-8D6D0F45804E@gmail.com>
On Wed, Apr 17 2019, Jean-Christophe Helary wrote:
> There is one. MIT license since octobre 2018:
> https://www.emacswiki.org/emacs/SubEthaEditProtocol
To me this is *waaaaaaay* too complicated. I don't know how I'd
pronounce SubEthaEdit (and needed to double-check how to spell it) so
it'd be a rocky start to asking someone to collaborate with it.
I think collaboration needs to be as easy as: "Let's just collaborate
over email."
So "Let's just collaborate over IRC" seems like a low enough barrier to
entry, and from my noobish mind, sending short diffs via IRC seems
pretty tenable... the a/b file header stuff could be omitted, since
there would be only a single collaboration file, and this value would be
stored in a variable. Ideally this would occur within an IRC CTCP so you
could chat while also seeing the diffs fly back and forth in real time
(with some sort of prefix so the client program could read & apply
them).
Pie is sky of course...
--
https://www.paulwrankin.com
next prev parent reply other threads:[~2019-04-18 4:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 6:43 collaborative editing in emacs on macos Jean-Christophe Helary
2019-04-16 7:39 ` Paul W. Rankin
2019-04-16 7:44 ` Paul W. Rankin
2019-04-16 8:09 ` Jean-Christophe Helary
2019-04-16 11:29 ` Noam Postavsky
2019-04-16 12:05 ` Jean-Christophe Helary
2019-04-17 2:04 ` Paul W. Rankin
2019-04-17 3:23 ` Jean-Christophe Helary
2019-04-18 4:47 ` Paul W. Rankin [this message]
2019-04-18 7:20 ` Jean-Christophe Helary
2019-04-26 7:29 ` Van L
2019-04-29 5:48 ` Paul W. Rankin
2019-04-29 7:42 ` Van L
2019-04-18 21:25 ` Phillip Lord
2019-04-19 1:12 ` Jean-Christophe Helary
2019-04-19 20:51 ` Jordan Wilson
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2v9zbzzpd.fsf@paulwrankin.com \
--to=hello@paulwrankin.com \
--cc=brandelune@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=npostavs@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).