emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: copyrights to be fixed


From: Jan Djärv
Subject: Re: copyrights to be fixed
Date: Sun, 11 Feb 2007 15:53:45 +0100
User-agent: Thunderbird 1.5.0.9 (Macintosh/20061207)



David Kastrup skrev:
address@hidden writes:

Richard Stallman <address@hidden> writes:

        Are there major gaps in the features?

    No, not that I have seen.

A small number of people can't tell the answer to this question by
running the program.

We need the people who implemented the multi-tty code to tell us
whether there are cases they have not handled yet that need to be
handled to avoid loss of functionality.
This readme contains a list of known issues:

http://lorentey.hu/downloads/emacs/multi-tty/README.multi-tty

For convenience I paste the Known Problems list here:

Known problems:

        * GTK support.  If you compile your Emacs with the GTK
          toolkit, some functionality of multi-tty will be lost.  In
          particular, you will not be able to work on multiple X
          displays at once.  Current releases of GTK have limitations
          and bugs that prevent full-blown multi-display support in
          Emacs.  (GTK crashes when Emacs tries to disconnect from an
          X server.)  Use the Lucid toolkit if you want to see a
          complete feature set.

Ok, perhaps people will call me a lunatic for that, but I think this
would be a rather compelling reason to merge multi-tty support rather
sooner than later after releasing Emacs 22: there are rather few
applications for which multi-tty support and disconnecting from an X
server would be relevant.  GTK and/or Gnome are supposed to be GNU
desktop components, and we want to get problems with them ironed out.
Merging multi-tty early in the Emacs 23 process gives appropriate GTK
bug fixes a chance to make it out into the real world before Emacs 23
follows.  In contrast, I don't think that we have similar
"sympathetic" software releases to take into consideration in
connection with unicode2.

The Gtk guys are aware of the problem, see http://bugzilla.gnome.org/show_bug.cgi?id=85715.

The issue is still not fixed as far as I can tell.

        Jan D.






reply via email to

[Prev in Thread] Current Thread [Next in Thread]