From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 58406@debbugs.gnu.org, manuel@ledu-giraud.fr
Subject: bug#58406: 29.0.50; Bars refactoring?
Date: Mon, 10 Oct 2022 21:42:37 +0800 [thread overview]
Message-ID: <87czazlrqq.fsf@yahoo.com> (raw)
In-Reply-To: <83ilkrhqfd.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 10 Oct 2022 14:24:38 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> I just tried that, and saw nothing suspicious. What should I watch
> for? what do you see in that case?
Moving the mouse back onto the tab bar button will lead to it not being
highlighted as expected, until you click on the tab bar.
But as I said, that was fixed. Messing with the *bar code has a very
real potential to introduce similar nasty bugs again.
next prev parent reply other threads:[~2022-10-10 13:42 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87czazlrqq.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=58406@debbugs.gnu.org \
--cc=eliz@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 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.