From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: jwiegley@gmail.com, matthias.clasen@gmail.com, 23144@debbugs.gnu.org
Subject: bug#23144: shrinking windows with gtk 3.20
Date: Fri, 01 Apr 2016 12:46:13 +0300 [thread overview]
Message-ID: <83h9flu0ey.fsf@gnu.org> (raw)
In-Reply-To: <56FE27E2.2030307@gmx.at> (message from martin rudalics on Fri, 01 Apr 2016 09:48:50 +0200)
> Date: Fri, 01 Apr 2016 09:48:50 +0200
> From: martin rudalics <rudalics@gmx.at>
> Cc: 23144@debbugs.gnu.org, Matthias Clasen <matthias.clasen@gmail.com>
>
> I think we have two possibilites to deal with this issue: Ignore it or
> implement a fix. If we ignore it, we might run into difficulties later
> when gtk developers eventually decide to apply the change in question or
> we find a case where our code does not DTRT anyway. As Eli already
> mentioned, after Jan's departure nobody here is in grade to maintain the
> gtk interface reliably.
>
> If we try to fix it, we could possibly rely on Matthias to give us clues
> on how to proceed and what to do if the fix causes problems. If the fix
> goes into master, there are chances that any such problems will pass by
> unnoticed for some time since currently most people here seem to use the
> release version.
How about the following course:
. On master, accept what Matthias suggests and deal with bug reports
if and when they come.
. 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.
Would that work?
next prev parent reply other threads:[~2016-04-01 9:46 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 [this message]
2016-04-02 0:03 ` Paul Eggert
2016-04-02 7:01 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h9flu0ey.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23144@debbugs.gnu.org \
--cc=jwiegley@gmail.com \
--cc=matthias.clasen@gmail.com \
--cc=rudalics@gmx.at \
/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.