unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Pascal Bourguignon <spam@mouse-potato.com>
Subject: Re: howto: 2 users interactively edit the same file ?
Date: Thu, 03 Nov 2005 08:05:44 +0100	[thread overview]
Message-ID: <87hdauky7r.fsf@thalassa.informatimago.com> (raw)
In-Reply-To: 87zmomdz7x.fsf@tiger.rapttech.com.au

Tim X <timx@spamto.devnul.com> writes:
> OK, I'm quite willing to accept all of that, though I'd still have
> concerns about how performance would be. If I understand you
> corrrectly, wouldn't there be a high likelihood of one input source
> "hogging" things - effectively causing a sort of starvation for the
> other user? There doesn't seem to be any sense of "fair" access in the
> model your describing and I still feel this would be problematic.

Indeed.  What's more, emacs imposes a "mutex" on the mini-buffer.  If
you type M-x in one frame, you cannot do anything else on the other
frame before you cancel the M-x or complete a command.


> I also wonder how emacs will handle things like local variables when
> you have two different users editing in the same buffer. Wouldn't this
> have consequences for things like point and region related commands?

point and region are frame local, not buffer local.


> I guess I'm over stating the complexities or something as the weight
> of opinion is against me. I have no problem with that, but my past
> experiences working on systems which have a similar model of operation
> where two users are affecting the same resource concurrently tells me
> its not as simple as just opening a second window on another display
> and everything else will just sort of magically work - I guess its my
> gut telling me there is a lot more too it and its a lot more complex -
> no real specific proof of this though.

Since there's no multithreading, there's no problem of accessing the
same resources concurrently.  It works exactly the same way with frame
on different display and several pointers & keyboards on different
displays than with several pointers & keyboards on the _same_ display,
or even one pointer & keyboard on one display with several frames: you
cannot type a key into two frames at the same "time": it'd produce two
distinct and ordered events and they're processed one after the other,
so there's no problem.

-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
Small brave carnivores
Kill pine cones and mosquitoes
Fear vacuum cleaner

  reply	other threads:[~2005-11-03  7:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.12726.1130303098.20277.help-gnu-emacs@gnu.org>
2005-10-26  5:43 ` howto: 2 users interactively edit the same file ? PT
2005-10-26  6:08   ` Matt Carlson
2005-10-30  7:11   ` Tim X
2005-10-30  4:29 ` Tim X
2005-10-30  5:06   ` Pascal Bourguignon
2005-10-30  7:46     ` Bernard Adrian
     [not found]     ` <mailman.13285.1130658471.20277.help-gnu-emacs@gnu.org>
2005-10-30  8:33       ` Johan Bockgård
2005-10-30  8:47         ` Bernard Adrian
2005-10-31  7:38       ` Tim X
2005-10-31 18:06         ` Bernard Adrian
     [not found]         ` <mailman.13469.1130782270.20277.help-gnu-emacs@gnu.org>
2005-11-03  6:51           ` Tim X
2005-10-31  8:04     ` Tim X
2005-10-31 20:15       ` Eli Zaretskii
2005-10-31 21:48       ` kgold
2005-11-01  4:50         ` Matt Carlson
     [not found]       ` <mailman.13482.1130789736.20277.help-gnu-emacs@gnu.org>
2005-11-03  6:25         ` Tim X
2005-11-03  7:05           ` Pascal Bourguignon [this message]
2005-11-04 10:52           ` Eli Zaretskii
2005-10-26  5:04 Matt Carlson
2005-10-26  5:22 ` Neon Absentius

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=87hdauky7r.fsf@thalassa.informatimago.com \
    --to=spam@mouse-potato.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).