From: Visuwesh <visuweshm@gmail.com>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: Po Lu <luangruo@yahoo.com>, 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 13:48:57 +0530 [thread overview]
Message-ID: <877d0n3slq.fsf@gmail.com> (raw)
In-Reply-To: <87wn8nvwto.fsf@gmx.net> (Stephen Berman's message of "Wed, 26 Oct 2022 10:00:19 +0200")
Isn't this yet another duplicate of bug#57320?
[புதன் அக்டோபர் 26, 2022] Stephen Berman wrote:
> I've done only elementary debugging with gdb and never from a different
> machine, so I will need explicit instructions for how to set it up and
> what to enter, and if it's not straightforward, I probably can't do it
> soon.
I ssh'd into my laptop from my phone to do the debugging. More info on
what I did can be found in bug#57320, and specific instructions are in
https://yhetil.org/emacs-bugs/87k06gby3w.fsf@gmail.com. HTH.
> But there may be a (for me) quicker way to investigate the issue: I'm in
> the process of building a new system on this machine, which is an
> updated version of my current system (on a different partition), and one
> of the first programs I built after installing the basic system is
> Emacs, first before installing X, then again with X but before
> installing GTK. On this system, the X build used the Lucid toolkit, and
> with it I did not observe the menu problems I described. Aside from
> different versions of system libraries like glibc and build tools like
> gcc, the two builds differ in their Emacs-specific configurations. The
> build with the menu problems used
IME, this bug goes away when you re-./configure Emacs so there's no
surprise this disappeared in your case. It would be of help if I could
run the debug build all the time and wait for the menu bug to eventually
show up but alas it is far too slow for me to use it daily...
> [configure lines.]
> I'll try using the other configuration on the new system and see if that
> makes a difference (though I probably won't get to that till this
> evening.)
I don't think the specifics of the configuration options matter as long
as you run the Lucid build.
next prev parent reply other threads:[~2022-10-26 8:18 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 [this message]
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
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=877d0n3slq.fsf@gmail.com \
--to=visuweshm@gmail.com \
--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.