From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 23144@debbugs.gnu.org, matthias.clasen@gmail.com
Subject: bug#23144: shrinking windows with gtk 3.20
Date: Sat, 02 Apr 2016 10:01:33 +0300 [thread overview]
Message-ID: <83r3eosdde.fsf@gnu.org> (raw)
In-Reply-To: <56FF0C5B.1020201@cs.ucla.edu> (message from Paul Eggert on Fri, 1 Apr 2016 17:03:39 -0700)
> Cc: 23144@debbugs.gnu.org, Matthias Clasen <matthias.clasen@gmail.com>
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Fri, 1 Apr 2016 17:03:39 -0700
>
> > . On the release branch, provide some safe workaround, triggered by
> > an option users could set if they encounter this problem with a
> > future GTK version. This assumes such a safe workaround is
> > possible, of course; I thought along the lines of the user
> > specifying the initial size explicitly in some way.
> >
>
> Another possibility is to ask builders not to combine GTK+4 (or will
> this be GTK+ 3.22? it's not clear), whenever it comes out, with Emacs 25
> whenever it comes out; and to instead stick with GTK+ 3.20 or earlier
> when building Emacs 25. If that's a reasonable request then the problem
> goes away.
Such a request, if we agree to that, should be in the form of
configure rejecting GTK+4. I don't believe in our ability to reach
all of the package maintainers and convince them.
But if we can find a reasonable fire escape without rejecting new
versions of GTK, I think it would be a better alternative.
next prev parent reply other threads:[~2016-04-02 7:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 20:52 bug#23144: shrinking windows with gtk 3.20 Matthias Clasen
2016-03-29 15:18 ` martin rudalics
2016-03-29 16:02 ` Eli Zaretskii
2016-03-29 17:20 ` martin rudalics
2016-03-31 16:09 ` John Wiegley
2016-04-01 7:48 ` martin rudalics
2016-04-01 9:46 ` Eli Zaretskii
2016-04-02 0:03 ` Paul Eggert
2016-04-02 7:01 ` Eli Zaretskii [this message]
2016-04-02 15:19 ` Matthias Clasen
2016-04-02 15:47 ` Eli Zaretskii
2016-04-02 16:06 ` martin rudalics
2016-04-02 16:28 ` Eli Zaretskii
2016-04-02 17:27 ` Matthias Clasen
2016-04-02 17:32 ` Eli Zaretskii
2016-04-02 23:20 ` Matthias Clasen
2016-04-03 2:36 ` Eli Zaretskii
2016-05-16 6:53 ` Paul Eggert
2016-05-16 8:21 ` martin rudalics
2016-05-16 15:53 ` Eli Zaretskii
2016-05-16 17:11 ` Paul Eggert
2017-03-24 13:01 ` Ken Brown
2017-03-24 13:24 ` martin rudalics
2017-03-24 13:38 ` Ken Brown
2017-03-24 18:52 ` martin rudalics
2017-03-24 13:35 ` Eli Zaretskii
2017-03-24 14:08 ` Ken Brown
2017-03-24 14:27 ` Eli Zaretskii
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=83r3eosdde.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23144@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=matthias.clasen@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).