[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GtkPlug patch
Re: GtkPlug patch
Tue, 03 Jan 2006 19:37:17 +0100
Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux)
"Richard M. Stallman" <address@hidden> writes:
> But even if it is very simple in the Gtk+ case, and only a bit more
> complicated in the general case, there are other issues here. Like for
> instance, what should an embedded Emacs do when someone tries to
> move or resize the window from lisp?
> These operations could do nothing in a reparented window.
> Therefore I think this should wait
> to the next release.
Question: would this stuff make any difference unless Emacs was called
in a special way? Is there some protocol advertising the possibility
for embedding that might be used by window managers or other
applications to check for embeddability?
If all of this is not the case, then the respective code paths would
basically just get exercised when one explicitly does something that
one could not do before. If there are just a few such code spaces,
the impact on the general release quality would be negligible.
How hard will it be to integrate those patches (or the respective
functionality) after the release? Would it make sense to integrate
them already in the multi-tty branch, or should we rather store them
somewhere separately after the release? Separate branch?
Does this make sense? Or would the authors of this patch prefer to
try their hand again from a clean head after release?
David Kastrup, Kriemhildstr. 15, 44793 Bochum
- Re: GtkPlug patch, Jan Djärv, 2006/01/01
- Re: GtkPlug patch, Richard M. Stallman, 2006/01/01
- Re: GtkPlug patch, Jan D., 2006/01/03
- Re: GtkPlug patch, Jan D., 2006/01/04
- Re: GtkPlug patch, Timo Savola, 2006/01/05
- Re: GtkPlug patch, Jan D., 2006/01/05