From: tomas@tuxteam.de
To: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: collaborative editing
Date: Sun, 7 Jun 2020 11:28:01 +0200 [thread overview]
Message-ID: <20200607092801.GB15198@tuxteam.de> (raw)
In-Reply-To: <E1jhm6t-0000iY-T1@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 736 bytes --]
On Sat, Jun 06, 2020 at 11:36:35PM -0400, Richard Stallman wrote:
[...]
> I've changed it to try to separate this question from others.
Good idea, thanks!
> I have not done shared editing over the network, but lots of people do
> it -- in Etherpad and in Google Docs -- and it is clear that they
> find it useful. How about if we take for granted it is useful
> and skip the debate about that point?
I didn't take the debate as being about /whether/ it is useful, but
rather about /in which way/ it may be useful: from that angle, I think
the debate itself is useful, as it may help to guide us shaping this
feature.
Myself, I'll give Rudel a try and look into the TLS point Stefan made,
as a result of this debate.
Cheers
-- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2020-06-07 9:28 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 15:58 What is the most useful potential feature which Emacs lacks? Van Ly
2020-05-28 3:13 ` Richard Stallman
2020-05-30 7:17 ` Van Ly
2020-05-31 7:10 ` Richard Stallman
2020-05-31 10:01 ` Van Ly
2020-05-31 12:49 ` excalamus--- via Emacs development discussions.
2020-06-01 3:54 ` Richard Stallman
2020-06-01 5:21 ` Yuri Khan
2020-06-02 2:55 ` Richard Stallman
2020-06-02 3:57 ` Karl Fogel
2020-06-02 5:15 ` Ihor Radchenko
2020-06-02 13:42 ` Stefan Monnier
2020-06-01 9:11 ` Bastien
2020-06-01 15:03 ` Eli Zaretskii
2020-06-01 23:32 ` Bastien
2020-06-01 23:50 ` Jean-Christophe Helary
2020-06-06 9:42 ` Eli Zaretskii
2020-06-06 9:58 ` tomas
2020-06-06 10:11 ` Eli Zaretskii
2020-06-06 10:29 ` tomas
2020-06-06 14:19 ` Stefan Monnier
2020-06-06 14:58 ` Arthur Miller
2020-06-06 20:18 ` tomas
2020-06-06 22:20 ` Stefan Monnier
2020-06-06 9:59 ` Thibaut Verron
2020-06-06 10:12 ` Eli Zaretskii
2020-06-06 10:18 ` tomas
2020-06-07 3:36 ` collaborative editing Richard Stallman
2020-06-07 9:28 ` tomas [this message]
2020-06-06 12:05 ` What is the most useful potential feature which Emacs lacks? Jean-Christophe Helary
-- strict thread matches above, loose matches on Subject: below --
2021-08-12 23:43 Collaborative editing Perry E. Metzger
2021-08-13 5:32 ` Tim Cross
2021-08-13 6:40 ` Eli Zaretskii
2021-09-01 6:32 ` Ag Ibragimov
2021-08-15 5:46 ` Jean Louis
2021-08-15 11:24 ` Ergus
2021-08-19 9:32 ` Philip Kaludercic
2021-08-19 9:33 ` Philip Kaludercic
2021-08-19 14:18 ` Ergus
2021-08-19 14:38 ` dick
2021-08-19 15:19 ` Perry E. Metzger
2021-08-19 15:56 ` Eli Zaretskii
2021-08-19 15:36 ` Philip Kaludercic
2021-08-28 8:41 ` Qiantan Hong
2021-08-28 11:40 ` Philip Kaludercic
2021-08-28 11:53 ` Qiantan Hong
2021-08-28 12:14 ` Philip Kaludercic
2021-08-28 9:17 ` Qiantan Hong
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=20200607092801.GB15198@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.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.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).