all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: Feng Shu <tumashu@163.com>, 58771@debbugs.gnu.org
Subject: bug#58771: 29.0.50; context submenu can not click when run emacs lucid build.
Date: Wed, 26 Oct 2022 17:55:35 +0800	[thread overview]
Message-ID: <87tu3q9aeg.fsf@yahoo.com> (raw)
In-Reply-To: <87o7tyx6qw.fsf@gmx.net> (Stephen Berman's message of "Wed, 26 Oct 2022 11:40:39 +0200")

Stephen Berman <stephen.berman@gmx.net> writes:

> I can't check right now because I'm on the older system and need to do
> work there.  But it occurred to it that I can try compiling the Lucid
> build here as I did on the new system, i.e. only --with-x-toolkit=lucid,
> and it still has the menu problems, so the build configuration does not
> account for the difference.
>
> But I also have a number of emacs executables of the Lucid build and I
> found that menu problems do not occur in my build from commit
> 177811ac0c0e5e41d4f661e8e5553e46f0019b9a (Sept 2) but do occur in my
> next build, from commit c6fc00f5d75a28fd4e99050ccc1af9ad82f66b2b (Sept
> 15, more recently than I remembered).  In the build from Sept 2 the
> context menu seems to hang for several seconds, during which there is no
> response, but then it seems to work ok, as do the menu bar menus, while
> the build from Sept 15 has the problems I still see now.  When I have
> more time I can try bisecting.
>
> Steve Berman

Please do that, thanks.





  reply	other threads:[~2022-10-26  9:55 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25  5:28 bug#58771: 29.0.50; context submenu can not click when run emacs lucid build Feng Shu
2022-10-25  7:43 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-25  8:35   ` Feng Shu
2022-10-25 10:30     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-25 13:58       ` Stephen Berman
2022-10-26  0:42         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-26  8:00           ` Stephen Berman
2022-10-26  8:18             ` Visuwesh
2022-10-26  9:40               ` Stephen Berman
2023-01-11  6:57               ` Mike Kupfer
2023-01-11  9:47                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-11 20:44                   ` Mike Kupfer
2023-01-12  1:22                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-12  2:16                       ` Mike Kupfer
2023-01-12  3:44                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-12  8:05                           ` Eli Zaretskii
2023-01-12 10:34                             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-13  2:43                               ` Mike Kupfer
2023-01-13  7:19                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-13  7:32                                   ` Eli Zaretskii
2023-01-14  2:28                                     ` Paul Eggert
2023-01-14  7:25                                       ` Eli Zaretskii
2023-01-14  7:48                                         ` Paul Eggert
2023-01-13  7:35                                   ` Jean Louis
2023-01-12  8:56                     ` Eli Zaretskii
2023-01-13  5:23                       ` Mike Kupfer
2022-10-26  8:20             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-26  9:40               ` Stephen Berman
2022-10-26  9:55                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-10-26  2:14   ` Feng Shu

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=87tu3q9aeg.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=58771@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=stephen.berman@gmx.net \
    --cc=tumashu@163.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.