unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Colin Baxter <m43cap@yandex.com>
Cc: 46990@debbugs.gnu.org
Subject: bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build
Date: Thu, 11 Mar 2021 16:02:02 +0200	[thread overview]
Message-ID: <83mtv9n605.fsf@gnu.org> (raw)
In-Reply-To: <87a6r9su29.fsf@yandex.com> (message from Colin Baxter on Thu, 11 Mar 2021 13:23:26 +0000)

> From: Colin Baxter <m43cap@yandex.com>
> Date: Thu, 11 Mar 2021 13:23:26 +0000
> 
>     Colin> Investigating further, I find that if I launch a lucid
>     Colin> "emacs-28" via
> 
>     Colin> src/temacs -Q
> 
>     Colin> and evaluate (menu-bar-mode -1) then the popup menu, formed
>     Colin> from <f10>, does indeed allow navigation from the arrow keys
>     Colin> (as well as the mouse). Only launching "emacs-28" from the
>     Colin> following
> 
>     Colin> 1. src/emacs -Q 2. src/bootstrap-emacs -Q
>     Colin> 3. src/emacs-28.0.50.1 -Q
> 
>     Colin> fails to allow the popup menu-bar to be navigable from the
>     Colin> arrow keys.
> 
> 
> If I miss out the batch option and make an emacs by
> 
> ./temacs -l loadup --temacs=pdump
> 
> then ./emacs -Q will allow the popup menu to be navigable via the arrow
> keys.

This could point to the portable dumper as the culprit (more
accurately, something we do wrongly when producing the pdmp file), but
then why does the installed Emacs behave correctly: it also starts
from the same pdmp file as when you invoke it uninstalled.  Hmm...

Thanks for the data points, anyway.





  reply	other threads:[~2021-03-11 14:02 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 [this message]
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
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=83mtv9n605.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=46990@debbugs.gnu.org \
    --cc=m43cap@yandex.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).