From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 23966@debbugs.gnu.org, ding@gnus.org
Subject: Re: bug#23966: 25.1.50; Frame resizing due to tool bar + Gnus
Date: Tue, 04 Aug 2020 11:29:45 +0200 [thread overview]
Message-ID: <87mu3arc6u.fsf@gnus.org> (raw)
In-Reply-To: <87y2neikt1.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 20 Jul 2020 11:43:06 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> As somebody who doesn't use tool bars normally, I'm wondering -- do we
> really need two different tool bar styles in Gnus? Can't we just rip
> out the `retro' stuff and thing will possibly be less confusing?
Perhaps somebody on the Gnus mailing list has some input here.
To recap -- there's some bugs in enabling the Summary mode tool bar,
because there's some setup being done at Gnus load time. This can be
fixed, I'm just wondering whether the proper fix here is to simplify the
code.
There's currently two tool bars for Gnus summary mode:
gnus-summary-tool-bar-retro
gnus-summary-tool-bar-gnome
I propose to get rid of the -retro one. Does anybody object to that?
Or is the -gnome tool bar really specific to Gnome, and it won't work on
other OS-es or something?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next parent reply other threads:[~2020-08-04 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87vb09u40u.fsf@gmx.net>
[not found] ` <57867BB6.1020601@gmx.at>
[not found] ` <87r3axtkcf.fsf@gmx.net>
[not found] ` <578754F3.9060800@gmx.at>
[not found] ` <87a8hkpmq8.fsf@gmx.net>
[not found] ` <5787CCF5.3000404@gmx.at>
[not found] ` <87eg6wghgl.fsf@gmx.net>
[not found] ` <874lkgtqnk.fsf@mouse.gnus.org>
[not found] ` <87h8ofcvqb.fsf@gmx.net>
[not found] ` <87wo2zmr20.fsf@gnus.org>
[not found] ` <87eep6a6w7.fsf@rub.de>
[not found] ` <877duyjzsr.fsf@gnus.org>
[not found] ` <87y2neikt1.fsf@gnus.org>
2020-08-04 9:29 ` Lars Ingebrigtsen [this message]
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=87mu3arc6u.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=23966@debbugs.gnu.org \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).