From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: 58406@debbugs.gnu.org
Subject: bug#58406: 29.0.50; Bars refactoring?
Date: Mon, 10 Oct 2022 21:41:11 +0800 [thread overview]
Message-ID: <87h70blrt4.fsf@yahoo.com> (raw)
In-Reply-To: <87wn9798ww.fsf@elite.giraud> (Manuel Giraud's message of "Mon, 10 Oct 2022 14:10:07 +0200")
Manuel Giraud <manuel@ledu-giraud.fr> writes:
> I find it useful to have some visual feed back that some text is
> clickable (the mode-line is a good example of this IMO). What do you
> mean by "no program does that anymore"? Do you that this is done by the
> widget library?
No, I meant that no other program has highlightable menu items in their
menu bars.
>>> I understand that it is too close to Emacs 29. Do you think the menu
>>> bar could be made to mimic some feature of the tool bar (like tab bar
>>> did)? Or do you think it would add to the cargo cult?
>>
>> I'd rather not touch any of the *bar code before Emacs 29 is cut. Most
>> people do not use the bars, leading to many latent bugs. Examples:
>> mouse face not being cleared when tooltips are enabled and the mouse
>> moves outside the frame, last_tool_bar_item not being cleared in the
>> same case, and last_tab_bar_item not being cleared, leading to mouse
>> highlight not working after the mouse is released outside a frame.
>>
>> These bugs are particularly nasty because they only happen in rare
>> situations, but can completely ruin the visual appearance of a frame
>> when they do.
>
> Ok, maybe I could look into them as an exercise on xdisp.c
The bugs previously mentioned were fixed, I'm just afraid that trying to
merge the tool bar and tab bar code will introduce more similar, nasty,
bugs.
next prev parent reply other threads:[~2022-10-10 13:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 7:37 bug#58406: 29.0.50; Bars refactoring? Manuel Giraud
2022-10-10 8:08 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-10 8:37 ` Manuel Giraud
2022-10-10 8:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-10 9:01 ` Eli Zaretskii
2022-10-10 10:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-10 11:24 ` Eli Zaretskii
2022-10-10 13:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-10 12:10 ` Manuel Giraud
2022-10-10 13:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-10-10 14:30 ` Manuel Giraud
2022-10-10 16:08 ` Eli Zaretskii
2022-10-11 0:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-10 8:58 ` Eli Zaretskii
2022-10-10 8:45 ` Eli Zaretskii
2022-10-10 11:58 ` Manuel Giraud
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=87h70blrt4.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=58406@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=manuel@ledu-giraud.fr \
/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).