all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Madhu <enometh@meer.net>
To: luangruo@yahoo.com
Cc: 59733@debbugs.gnu.org
Subject: bug#59733: 29.0.50; unrespnsive Xaw menus
Date: Thu, 01 Dec 2022 18:26:24 +0530 (IST)	[thread overview]
Message-ID: <20221201.182624.1393910185732679610.enometh@meer.net> (raw)
In-Reply-To: <87a647toxs.fsf@yahoo.com>

*  Po Lu <87a647toxs.fsf@yahoo.com>
> If you run "make extraclean" and then rebuild Emacs, is it still fixed?

I did did a new checkout of the latest master and did a build and I
don't see the bug. i.e. menus work as expected.  I should've checked
before reporting.

I believe this bug can be closed, thanks, (but I'm still curious: why
do you think I am seeing the bad behaviour on the
tree-with-previous-build-artefacts I that I have?)









  reply	other threads:[~2022-12-01 12:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-01  2:35 bug#59733: 29.0.50; unrespnsive Xaw menus Madhu
2022-12-01  7:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-01  9:34   ` Madhu
2022-12-01 10:10     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-01 12:56       ` Madhu [this message]
2022-12-01 13:11         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-01 13:55           ` Visuwesh
2022-12-01 14:24           ` Madhu
2022-12-02  1:04             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04  5:24               ` Madhu
2022-12-04  6:36                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-05  8:05                   ` bug#59733: 29.0.50; unresponsive " Madhu
2022-12-05  8:58                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=20221201.182624.1393910185732679610.enometh@meer.net \
    --to=enometh@meer.net \
    --cc=59733@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    /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.