From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 51049@debbugs.gnu.org
Subject: bug#51049: 28.0.50; tool-bar :vert-only property is broken, not documented and of limited use
Date: Wed, 06 Oct 2021 21:27:11 +0300 [thread overview]
Message-ID: <831r4y2em8.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkqqADM=Uwsaxh94zsGZ1QnBsPwQQ428pfbf_ezBs4Yfg@mail.gmail.com> (message from Stefan Kangas on Wed, 6 Oct 2021 14:10:52 -0400)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Wed, 6 Oct 2021 14:10:52 -0400
> Cc: 51049@debbugs.gnu.org
>
> > It's fine to introduce new features, but why remove old ones while at
> > that? What is not useful to you could be useful to someone else.
>
> I'm just asking the question based on my observations. I don't see a
> use-case for this feature, and if it is indeed broken then the fact that
> no one has complained might be some indication.
>
> If you think that this feature could be useful, then I have no objection
> to keeping it. But if it is indeed broken, it should at least be fixed
> to work as intended, and then documented; preferably in that order.
I suggested to step through the code, in order to understand what
happens there. Then we will have a better idea of whether it works
and when. I understand that you don't intend to do that, but perhaps
someone else will. (I myself don't have access to a system where I
can run a GTK build on GUI display, so I unfortunately cannot do this
myself.)
next prev parent reply other threads:[~2021-10-06 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 23:57 bug#51049: 28.0.50; tool-bar :vert-only property is broken, not documented and of limited use Stefan Kangas
2021-10-06 16:32 ` Eli Zaretskii
2021-10-06 18:10 ` Stefan Kangas
2021-10-06 18:27 ` Eli Zaretskii [this message]
2022-09-12 10:55 ` 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=831r4y2em8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51049@debbugs.gnu.org \
--cc=stefan@marxist.se \
/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).