From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 23966@debbugs.gnu.org
Subject: bug#23966: 25.1.50; Frame resizing due to tool bar + Gnus
Date: Thu, 12 Apr 2018 17:01:35 +0200 [thread overview]
Message-ID: <874lkgtqnk.fsf@mouse.gnus.org> (raw)
In-Reply-To: <87eg6wghgl.fsf@gmx.net> (Stephen Berman's message of "Thu, 14 Jul 2016 21:14:34 +0200")
Stephen Berman <stephen.berman@gmx.net> writes:
>> suppose that just enabling ‘tool-bar-mode’ is not sufficient to make a
>> gnus tool bar once gnus has started. Maybe this deficiency is inherent
>> to ‘tool-bar-mode’ itself. But it would be interesting to find out
>> who's responsible for making such small (8 pixels in your, 35 pixels in
>> my case) tool bars in the first place.
>
> Indeed.
Do you still see this on Emacs master now? There have been quite a few
pixel-sizing fixes applied to Emacs over the past year...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2018-04-12 15:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 12:16 bug#23966: 25.1.50; Frame resizing due to tool bar + Gnus Stephen Berman
2016-07-13 17:34 ` martin rudalics
2016-07-13 19:21 ` Stephen Berman
2016-07-14 9:01 ` martin rudalics
2016-07-14 9:55 ` Stephen Berman
2016-07-14 17:33 ` martin rudalics
2016-07-14 19:14 ` Stephen Berman
2018-04-12 15:01 ` Lars Ingebrigtsen [this message]
2018-04-13 9:16 ` Stephen Berman
2020-07-19 16:02 ` Lars Ingebrigtsen
2020-07-20 9:10 ` Stephen Berman
2020-07-20 9:31 ` Lars Ingebrigtsen
2020-07-20 9:50 ` Stephen Berman
2020-07-23 15:25 ` Lars Ingebrigtsen
2020-07-20 9:33 ` Lars Ingebrigtsen
2020-07-20 9:43 ` Lars Ingebrigtsen
2020-08-04 9:29 ` Lars Ingebrigtsen
[not found] ` <87mu3arc6u.fsf@gnus.org>
2022-04-30 16:18 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874lkgtqnk.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=23966@debbugs.gnu.org \
--cc=stephen.berman@gmx.net \
/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.