unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 46773@debbugs.gnu.org, rpluim@gmail.com, dgutov@yandex.ru
Subject: bug#46773: 28.0.50; Different heights for toolbar
Date: Sat, 27 Feb 2021 15:20:28 +0100	[thread overview]
Message-ID: <875z2diocz.fsf@gnus.org> (raw)
In-Reply-To: <83pn0loegr.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 27 Feb 2021 14:57:40 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> If we can do that, yes.  I assumed that the font used by the GTK tool
> bar is not our default font, is it?  If it isn't, how can we know its
> size?

Oh, yeah, I'd forgotten that we leave all that to the toolkit.  So
that's no good.  We could use heuristics -- that is, look at the default
font size and try to size up the min height based on that.  Not very
satisfactory, though.

This reminds me of bug#40978, which is about scaling images in toolbars
and the like based on the same heuristics as we do for in-buffer images
-- I was somewhat leery about going down that path because the
repercussions seem unpredictable, but that would probably have fixed
what I'm seeing in this bug report...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-02-27 14:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25 15:30 bug#46773: 28.0.50; Different heights for toolbar Lars Ingebrigtsen
2021-02-25 15:37 ` Eli Zaretskii
2021-02-25 16:36   ` Robert Pluim
2021-02-25 18:23     ` Eli Zaretskii
2021-02-26  9:13       ` Robert Pluim
2021-02-26 12:03         ` Eli Zaretskii
2021-02-26 15:48           ` Dmitry Gutov
2021-02-26 16:08             ` bug#46773: [External] : " Drew Adams
2021-02-26 16:23               ` Dmitry Gutov
2021-02-26 17:02                 ` Robert Pluim
2021-02-26 18:13                   ` Dmitry Gutov
2021-02-26 19:53                   ` Eli Zaretskii
2021-02-27  4:13             ` Lars Ingebrigtsen
2021-02-27  7:35               ` Eli Zaretskii
2021-02-27 11:52                 ` Lars Ingebrigtsen
2021-02-27 12:57                   ` Eli Zaretskii
2021-02-27 14:20                     ` Lars Ingebrigtsen [this message]
     [not found]                       ` <87blc4nwl8.fsf@gnus.org>
2021-02-28 18:21                         ` Eli Zaretskii
2021-02-28 19:40                           ` Colin Baxter
2021-03-01 12:39                             ` Lars Ingebrigtsen
2021-03-01 15:18                               ` Colin Baxter
2021-02-27 16:41               ` Dmitry Gutov
     [not found]                 ` <87h7lwnws5.fsf@gnus.org>
2021-02-28 22:06                   ` Dmitry Gutov
2021-02-28 22:19                     ` Lars Ingebrigtsen
2021-02-28 22:31                       ` Lars Ingebrigtsen

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=875z2diocz.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=46773@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=rpluim@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).