From: Colin Baxter <m43cap@yandex.com>
To: Visuwesh <visuweshm@gmail.com>
Cc: Po Lu <luangruo@yahoo.com>, Lars Ingebrigtsen <larsi@gnus.org>,
46990@debbugs.gnu.org
Subject: bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build
Date: Mon, 20 Jun 2022 13:29:38 +0100 [thread overview]
Message-ID: <87r13ja571.fsf@yandex.com> (raw)
In-Reply-To: <87edzjr0pp.fsf@gmail.com> (Visuwesh's message of "Mon, 20 Jun 2022 17:44:26 +0530")
>>>>> Visuwesh <visuweshm@gmail.com> writes:
> [திங்கள் ஜூன் 20, 2022] Lars Ingebrigtsen wrote:
>> Colin Baxter <m43cap@yandex.com> writes:
>>
>>> I suppose the Lucid issue with no key-navigation of a popup menu
>>> is not so important since the problem disappears (for me) once
>>> the Lucid compiled emacs is installed.
>>
>> It's just interesting to find out what's going on here -- there
>> might be other problems in the same area.
>>
>> Copying src/emacs and src/emacs.pdmp to /tmp and executing
>> /tmp/emacs also makes the problem disappear.
> Weird... I can use arrow keys just fine here in a Lucid build. My
> emacs executable lives in src/emacs and my PATH contains,
> ~/lib/ports/emacs/lib-src:~/lib/ports/emacs/src
> where ~/lib/ports/emacs is where I have the Emacs repo cloned.
> The way I launch Emacs doesn't seem to matter either: I tried
> `./src/emacs -Q' and `emacs -Q' and both don't show the problem.
> If it is of any help, `xrdb -query' prints,
> *customization: -color
> [ To be clear, I have no Xresources file anywhere in my home
> directory. ]
No ~/.Xresource? That's interesting. I think the common factor for those
who see the problem is that they have such a file, even though emacs
settings may have been commented out. I'll remove my Xresources and see
what happens.
Best wishes,
next prev parent reply other threads:[~2022-06-20 12:29 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 16:57 bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build Colin Baxter
2021-03-08 8:26 ` martin rudalics
2021-03-08 10:05 ` Colin Baxter
2021-03-08 10:56 ` Basil L. Contovounesios
2021-03-08 14:29 ` Colin Baxter
2021-03-08 20:36 ` Glenn Morris
2021-03-10 18:59 ` Colin Baxter
2021-03-10 19:12 ` Eli Zaretskii
2021-03-10 18:41 ` Eli Zaretskii
2021-03-10 19:39 ` Colin Baxter
2021-03-10 20:03 ` Eli Zaretskii
2021-03-10 20:30 ` Colin Baxter
2021-03-10 20:49 ` Eli Zaretskii
2021-03-10 23:34 ` Gregory Heytings
2021-03-11 5:07 ` Eli Zaretskii
2021-03-11 12:56 ` Colin Baxter
2021-03-11 13:23 ` Colin Baxter
2021-03-11 14:02 ` Eli Zaretskii
2021-03-11 14:25 ` Gregory Heytings
2021-03-11 14:50 ` Eli Zaretskii
2022-06-20 8:27 ` Lars Ingebrigtsen
2022-06-20 9:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20 9:53 ` Lars Ingebrigtsen
2022-06-20 10:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20 10:08 ` Lars Ingebrigtsen
2022-06-20 10:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20 10:40 ` Lars Ingebrigtsen
2022-06-20 13:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20 15:39 ` Lars Ingebrigtsen
2022-06-22 8:29 ` Colin Baxter
2022-06-20 10:08 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20 10:28 ` Lars Ingebrigtsen
2022-06-20 11:02 ` Colin Baxter
2022-06-20 11:07 ` Lars Ingebrigtsen
2022-06-20 12:14 ` Visuwesh
2022-06-20 12:29 ` Colin Baxter [this message]
2022-06-20 13:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20 13:16 ` Visuwesh
2022-06-20 13:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20 13:26 ` Visuwesh
2022-06-20 13:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20 15:38 ` Lars Ingebrigtsen
2022-06-20 15:54 ` Eli Zaretskii
2022-06-21 10:16 ` Lars Ingebrigtsen
2022-06-21 12:30 ` Manuel Giraud
2022-06-21 12:36 ` Eli Zaretskii
2022-06-21 13:58 ` Manuel Giraud
2022-06-21 12:36 ` Lars Ingebrigtsen
2022-06-21 1:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20 13:01 ` 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
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=87r13ja571.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=46990@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=visuweshm@gmail.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 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).