From: Tim X <timx@spamto.devnul.com>
Subject: Re: howto: 2 users interactively edit the same file ?
Date: 30 Oct 2005 18:11:47 +1100 [thread overview]
Message-ID: <87hdazv5qk.fsf@tiger.rapttech.com.au> (raw)
In-Reply-To: 1130305405.843028.221790@z14g2000cwz.googlegroups.com
"PT" <spamfilteraccount@gmail.com> writes:
> After years of using Emacs I accidentally discovered M-x
> make-frame-on-display which can do what you want if memory serves me
> right.
>
> I don't know if it works on Windows, but it was seamless on Unix.
>
I don't think this will work. The problem will be getting input. I
suspect that as this would involve redirecting a frame from an
existing emacs session to a different display, while the second user
would be able to see the frame, they would not be able to input data
as the application itself is still associated with the input from the
user who started the session.
It would probably be possible to start emacs and have all its i/o
directed to the second display, but then the first user who started
emacs won't have any way to input commands/characters etc.
I think the root of the problem here is that the OP wants to be able
to setup emacs in such a way that two users can be usinig it at the
same time - it simply is not designed to achieve this - don't forget
emacs doesn't have thread support either, so I doubt you could even
modify emacs itself to achieve this.
The best you could do wold be -
1. Use CVS as the repository for the files
2. Each user checks out their own copy
3. Each user starts emacs and opens their own copy
4. Each user creates a second frame with a copy of the file they
are editing and redirects this frame to the other users display
5. Each user checks in their document once editing has finished.
The two users would be editing *different* copies of the file and
there would still be a need to merge them together, but CVS will take
care of the trivial merging problems. The two users will have to
resolve more complex merges. The redirected frame would at least allow
each user to see what the other has done - but I suspect the
functionality here will be limited as I don't think the second user
will be able to manipulate the contents of the window i.e. scroll
up/down etc.
--
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!
next prev parent reply other threads:[~2005-10-30 7:11 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 [this message]
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
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=87hdazv5qk.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).