From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: SubEthaEdit style networked editing
Date: Wed, 22 Mar 2006 12:32:06 -0700 [thread overview]
Message-ID: <dvs8ov$7p8$1@sea.gmane.org> (raw)
In-Reply-To: <1143047663.612599.18490@u72g2000cwu.googlegroups.com>
Shug Boabby wrote:
> Kevin wrote:
>>But not that they are actually working at the same time.
>
> of course we can assume this... it would be pointless otherwise! the
> whole point of collaborative editing *NOT VERSION CONTROL* is that two
> (or more) people can work on the same file *at the same time*.
That may very well be the definition of "collaborative editing", but the
Emacs developers (the antecedent of "they") collaborate (i.e. work
together) asynchronously from distant time zones.
> if you think this has anything to do with version control (two people
> editing the same file at different times, saving revisions and storing
> version info), then you have missed the point of the collaborative
> editing concept. at the end of a collaborative editing session, one
> person would commit the file to the version control system with a
> Changelog.
Sounds spiffy!
--
Kevin Rodgers
next prev parent reply other threads:[~2006-03-22 19:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 16:21 SubEthaEdit style networked editing Shug Boabby
2006-03-13 16:27 ` David Kastrup
2006-03-13 17:09 ` Shug Boabby
2006-03-14 14:13 ` david.reitter
2006-03-14 17:57 ` Shug Boabby
2006-03-15 16:03 ` Mathias Dahl
2006-03-15 16:54 ` Shug Boabby
2006-03-15 17:04 ` Shug Boabby
2006-03-16 15:31 ` Mathias Dahl
2006-03-21 16:38 ` Stefan Monnier
2006-03-22 14:45 ` Shug Boabby
2006-03-22 15:56 ` Kevin Rodgers
[not found] ` <mailman.32.1143043283.14011.help-gnu-emacs@gnu.org>
2006-03-22 17:14 ` Shug Boabby
2006-03-22 17:17 ` Shug Boabby
2006-03-22 19:32 ` Kevin Rodgers [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-16 0:15 David Reitter
[not found] <mailman.94.1142468136.9686.help-gnu-emacs@gnu.org>
2006-03-16 20:04 ` Shug Boabby
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='dvs8ov$7p8$1@sea.gmane.org' \
--to=ihs_4664@yahoo.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).