From: Qiantan Hong <qhong@mit.edu>
To: Karl Fogel <kfogel@red-bean.com>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Checking in on status of crdt.el for collaborative editing.
Date: Fri, 21 May 2021 07:55:52 +0000 [thread overview]
Message-ID: <4DF11100-EA68-42E2-A89E-61905F1E9A52@mit.edu> (raw)
In-Reply-To: <87sg2pswab.fsf@red-bean.com>
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]
Hi Karl,
Sorry for being non responsive for a while! Luckily semester is ending and I’m back to life :)
I haven’t put much time in improving crdt.el during semester (I probably will during summer),
but my friends and I are using it for other projects, none of us ever had any problems. So I think it should be at beta test.
Except this one issue I’m worried about https://code.librehq.com/qhong/crdt.el/-/issues/6
My friends and I didn’t encounter this ever once in our scenarios and I haven’t reproduced it so far.
I suggest trying it in your settings and see if such thing happen, before using in production.
Also I will put best effort to locate and fix the cause of it during summer.
Hope this help. Happy hacking!
Best,
Qiantan
On May 14, 2021, at 1:45 AM, Karl Fogel <kfogel@red-bean.com<mailto:kfogel@red-bean.com>> wrote:
Qiantan, I was just wondering what the status of crdt.el is. I can see from the issue tracker that some people are trying it out. Speaking approximately, do you think it's at alpha testing stage? Beta testing?
(I ask because my business partner, James Vasile, and I have mutually decided that we're in the "will beta test in production" camp when you think it's reached that point.)
Best regards,
-Karl
[-- Attachment #2: Type: text/html, Size: 3083 bytes --]
next prev parent reply other threads:[~2021-05-21 7:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 5:45 Checking in on status of crdt.el for collaborative editing Karl Fogel
2021-05-21 7:55 ` Qiantan Hong [this message]
2021-05-21 8:05 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DF11100-EA68-42E2-A89E-61905F1E9A52@mit.edu \
--to=qhong@mit.edu \
--cc=emacs-devel@gnu.org \
--cc=kfogel@red-bean.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.