From: David Kastrup <dak@gnu.org>
To: Miles Bader <miles@gnu.org>
Cc: Karoly Lorentey <karoly@lorentey.hu>, emacs-devel@gnu.org
Subject: Re: multi-tty branch created
Date: Sun, 13 May 2007 18:13:20 +0200 [thread overview]
Message-ID: <85646wpuqn.fsf@lola.goethe.zz> (raw)
In-Reply-To: <85abw8pyk7.fsf@lola.goethe.zz> (David Kastrup's message of "Sun\, 13 May 2007 16\:50\:48 +0200")
David Kastrup <dak@gnu.org> writes:
> Miles Bader <miles@gnu.org> writes:
>
>> Ok, I've put the multi-tty sources into CVS and arch branches on
>> savannah.
>>
>> The CVS branch tag is called "multi-tty".
>>
>> The arch branch is "emacs@sv.gnu.org/emacs--multi-tty--0".
>
> Good!
I've checked it out, compiled it, not yet used it. README.multi-tty
does not yet reflect the availability on Savannah. It also sports
quite a list of problematic areas, but those seem to be no regressions
per se and should not make things worse mostly. Is the GTK+ situation
as described in there? My current version is 2.10.11, so it _might_
work for the multiple X case, but README.multi-tty basically mentions
2.10 as something to come into being only in the future:
Update: I am still having problems with GTK+ 2.8.10. I have the
impression that the various multidisplay fixes will only get
released in GTK+ 2.10.
One thing that is mentioned that calling emacsclient from a different
user will not work. I think that this is really a non-issue since
file accessibility from a different user would also be different and
there is no really useful strategy short of using tramp for getting
this to work.
It might be at some point be interesting to write a "trampclient"
which pingpongs the data across an emacsclient socket or a pseudotty
or whatever, but I don't think that this should for now be considered.
emacsclient operation in multitty is different as compared to
previously. So people can't avoid multitty completely, meaning that
we can't bluntly state "situation can't be worse than previously, no
regression" but need to evaluate multitty somewhat more closely before
finding it suited for trunk, even if the compilation problems on
DOS/Windows/Mac have been tackled.
The precondition for trunk in my opinion would be that it does not
impede workability for those people who are working on different parts
of Emacs.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2007-05-13 16:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-13 13:31 multi-tty branch created Miles Bader
2007-05-13 14:50 ` David Kastrup
2007-05-13 16:12 ` Miles Bader
2007-05-13 16:14 ` David Kastrup
2007-05-13 16:13 ` David Kastrup [this message]
2007-05-13 19:28 ` Robert J. Chassell
2007-05-16 13:24 ` Károly Lo"rentey
2007-05-16 13:46 ` Juanma Barranquero
2007-05-16 15:04 ` Károly Lőrentey
2007-05-16 15:34 ` David Kastrup
2007-05-16 16:11 ` Károly Lőrentey
2007-05-16 21:17 ` Jason Rumney
2007-05-16 16:20 ` Dan Nicolaescu
2007-05-16 17:39 ` David Kastrup
2007-05-16 20:48 ` Károly Lőrentey
2007-05-17 14:02 ` Stefan Monnier
2007-05-17 16:04 ` Károly Lo"rentey
2007-05-17 23:24 ` Stefan Monnier
2007-05-18 18:02 ` Károly Lo"rentey
2007-05-19 14:07 ` Stefan Monnier
2007-05-13 20:07 ` Jason Rumney
2007-05-14 10:21 ` Karoly Lorentey
2007-05-14 11:55 ` Jason Rumney
2007-05-15 13:03 ` Karoly Lorentey
2007-05-15 22:05 ` Ken Raeburn
2007-05-14 6:00 ` Manoj Srivastava
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85646wpuqn.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=karoly@lorentey.hu \
--cc=miles@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.