unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: bob@rattlesnake.com, emacs-devel@gnu.org
Subject: Re: groupware question
Date: 03 Oct 2003 11:00:44 -0400	[thread overview]
Message-ID: <jwvsmmaml30.fsf-monnier+emacs/devel@vor.iro.umontreal.ca> (raw)
In-Reply-To: <87ad8ibtb5.fsf@tleepslib.sk.tsukuba.ac.jp>

> We also found that it was hard (in XEmacs, GNU Emacs might do better)
> to keep the window-frame mapping consistent across frames (eg, if one
> of you does find-tag, the other doesn't automatically see the result
> if it's a different buffer).

The technical problems I've had with "one Emacs for two people" had
mostly to do with multiple simultaneous minibuffer activations.

Or also with pieces of code which try to reuse an existing window/buffer if
it already exists, leading to the problem such as your *Help* buffer is
shown on the other guy's display and you just sit there wondering what is
Emacs waiting for.

But it was mostly irrelevant because in the end, either we wanted really
close interaction, in which case "one typist, 4 eyes" worked better (the
typing part was never the bottleneck), or otherwise a system based on
CVS-with-frequent-commit worked just as well if not better by decoupling us
just enough (this way we could edit the same text and compare afterwards to
resolve the conflict, rather than fight over who'd get to write his code,
without the other being able to show concretely what he intended to write).


        Stefan

  parent reply	other threads:[~2003-10-03 15:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-02 20:44 groupware question Robert J. Chassell
2003-10-03  8:48 ` Stephen J. Turnbull
2003-10-03 14:33   ` Robert J. Chassell
2003-10-04  8:17     ` Stephen J. Turnbull
2003-10-03 15:00   ` Stefan Monnier [this message]
2003-10-04  0:50     ` Robert J. Chassell
2003-10-04 22:35     ` Richard Stallman

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=jwvsmmaml30.fsf-monnier+emacs/devel@vor.iro.umontreal.ca \
    --to=monnier@iro.umontreal.ca \
    --cc=bob@rattlesnake.com \
    --cc=emacs-devel@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).