unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tim X <timx@spamto.devnul.com>
Subject: Re: howto: 2 users interactively edit the same file ?
Date: 03 Nov 2005 17:25:54 +1100	[thread overview]
Message-ID: <87zmomdz7x.fsf@tiger.rapttech.com.au> (raw)
In-Reply-To: mailman.13482.1130789736.20277.help-gnu-emacs@gnu.org

Eli Zaretskii <eliz@gnu.org> writes:

> > From: Tim X <timx@spamto.devnul.com>
> > Date: 31 Oct 2005 19:04:16 +1100
> > 
> > I find it amazing this will work. The big problem is how can emacs,
> > which doesn't support threads, handle simultaneous input from two
> > distinct frames? I can't see how it can handle input from two
> > different input devices simultaneously either.
> 
> I don't see why you cannot see that: quite simply, Emacs tries to read
> from every possible input source, one after the other (that includes
> any subprocesses that happen to run in some Emacs buffers, such as
> compilation, Grep, spell-checker, etc.).  Emacs uses the system call
> `select' or its equivalent to do that; `select' actually allows you to
> set up a kind of ``poor man's threading'' in a single thread.
> 
> > The physical displaying
> > of the frame on another display is easy enough to understand - this is
> > a feature of X windows which emacs is able to take advantage of when
> > it is built with X lib support - but coping with input from two
> > sources at the same time is a very different matter. 
> 
> Not really.  Provided that you know what source each input even came
> from, it's quite easy to DTRT with each one of them.

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.

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?

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.

Tim


-- 
Tim Cross
The e-mail address on this message is FALSE (obviously!). My real e-mail is
to a company in Australia called rapttech and my login is tcross - if you 
really need to send mail, you should be able to work it out!

  parent reply	other threads:[~2005-11-03  6:25 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 [this message]
2005-11-03  7:05           ` Pascal Bourguignon
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=87zmomdz7x.fsf@tiger.rapttech.com.au \
    --to=timx@spamto.devnul.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).