unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Shug Boabby" <Shug.Boabby@gmail.com>
Subject: Re: SubEthaEdit style networked editing
Date: 15 Mar 2006 08:54:17 -0800	[thread overview]
Message-ID: <1142441657.075475.315230@p10g2000cwp.googlegroups.com> (raw)
In-Reply-To: <uu09zpueb.fsf@gmail.com>

Mathias asked:
> what are the things you need to edit with other people at the same time?
> I have always wondered, probably because I seldom or never has seen
> the use myself.

Text (technical) documents... primarily short LaTeX reports that I am
rapidly working on with 2 -> 5 other members of my team. We are all
sitting in the same room working on a 5 -> 7 page document and giving
it a heavy edit after getting the core content down.

It is not always plausible (especially during the final editing stages)
to designate a set of paragraphs to individual authors, and using
something like svn/cvs is just not responsive enough... i want to see
their edits *now*... not when i ask to show me updates (which i have to
merge with what i have just done in the last 5 minutes, which gets mega
complicated if we even went near each other).

Collaborative editing of plain text is a very different experience than
with code. With code it is structured and everyone knows which bits
they are working on... and if you both end up committing something to
svn at the same time, merge usually has no problems if you worked on
different functions. But with plain text, you could have two people
editing the same paragraph... you also have vocal (or aim, if remote)
communication and feedback... but it's mostly in the form of nods of
approval or disapproval at what they just did on the screen.

The alternative to collaborative editing would be to have everyone
huddle round the same screen and designate one person to do the edits,
but in practice this is difficult and a lot slower. You might know what
you want to write, but you don't know how it looks until it is written.

I'm really surprised that collaborative editing isn't a bigger deal in
the Free Software Community... you could have hackathons on a single
file to rewrite something. So long as everyone has a good idea what
they are doing up front (i.e. template, specification or badly written
file as a base), it is an incredibly fast way to produce work! No more
waiting a day/hour to hear back before you can go change that
algorithm...

  reply	other threads:[~2006-03-15 16:54 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 [this message]
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
  -- 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=1142441657.075475.315230@p10g2000cwp.googlegroups.com \
    --to=shug.boabby@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).