unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Colin Baxter <m43cap@yandex.com>
To: Gregory Heytings <gregory@heytings.org>
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 12:56:07 +0000	[thread overview]
Message-ID: <87k0qdsvbs.fsf@yandex.com> (raw)
In-Reply-To: <9914d67ab1e37ee22af8@heytings.org> (Gregory Heytings's message of "Wed, 10 Mar 2021 23:34:46 +0000")

>>>>> Gregory Heytings <gregory@heytings.org> writes:

    >>>> Can you or someone who sees the problem please bisect this?
    >>>> I'm delaying the release of Emacs 27.2 in the hope that we
    >>>> could fix it, if indeed this was introduced between 27.1.90 and
    >>>> 27.1.91.
    >>> 
    >>> I may be guilty of crying wolf when there is none. If I
    >>> configure the 27.1.91 pretest for lucid and "make", the effect
    >>> does occur on launching emacs via src/emacs. However if I go the
    >>> next step and "make install", the effect does not occur when I
    >>> launch the installed emacs. I will double-check this by
    >>> installing from the git master branch and report back.
    >>> 
    >>> I am sorry. I stupidly assumed launching emacs from an src
    >>> directory would give the same beast as launching from the
    >>> installed bin directory.
    >> 
    >> No need to be sorry: your assumption was correct.  Emacs should
    >> generally work the same when you run it uninstalled.  It is
    >> strange that it doesn't in this case.
    >> 

    > It seems that what Colin describes is an old (and indeed strange)
    > behavior.  I just tried (on Debian GNU/Linux) various revisions of
    > the trunk (up to 5b464a9cea from three years ago), and with
    > --with-x-toolkit=lucid the menu cannot be navigated with arrow
    > keys with an uninstalled emacs, and can be navigated with an
    > installed one.

Investigating further, I find that if I launch a lucid "emacs-28" via

src/temacs -Q

and evaluate (menu-bar-mode -1) then the popup menu, formed from <f10>,
does indeed allow navigation from the arrow keys (as well as the
mouse). Only launching "emacs-28" from the following

1. src/emacs -Q
2. src/bootstrap-emacs -Q
3. src/emacs-28.0.50.1 -Q

fails to allow the popup menu-bar to be navigable from the arrow keys.


I hope this helps.

Best wishes,

Colin Baxter.





  parent reply	other threads:[~2021-03-11 12:56 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 [this message]
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
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=87k0qdsvbs.fsf@yandex.com \
    --to=m43cap@yandex.com \
    --cc=46990@debbugs.gnu.org \
    --cc=gregory@heytings.org \
    /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).