unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tomas Hlavaty <tom@logand.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, 57372@debbugs.gnu.org
Subject: bug#57372: no-toolkit menu popups do not respect emacs font configuration
Date: Thu, 25 Aug 2022 00:59:22 +0200	[thread overview]
Message-ID: <87zgftgsdx.fsf@logand.com> (raw)
In-Reply-To: <83tu614f1k.fsf@gnu.org>

On Wed 24 Aug 2022 at 22:28, Eli Zaretskii <eliz@gnu.org> wrote:
>> >> TTY menus seem fine except the extra > in menu-bar overlaps the next
>> >> menu-bar item text.
>> >
>> > That's by design, btw.
>> 
>> Strange design.  Say I want to open the Edit menu.  I press F10 and
>> suddenly I cannot see the Edit menu anymore.
>
> ??? The drop-down menu also hides part of the window's text, doesn't
> it?  More generally, _something_ has to be hidden, because this is a
> text-mode terminal: the menu cannot move outside of the frame, where
> it wouldn't overlap any of the windows.

That is not the issue.
Why does the Edit menu dissappear?
Because there are three extra charactes drawn over it.
Say the menu-bar looks like this:
File Edit Options
Press F10 and it looks like this:
 File > t Options
Where is my Edit menu?
What should I do now?

> So why is it important that the Edit menu is hidden, but not that the
> whole text below the File menu is suddenly unreadable.

Because when I want to open the Edit menu, my attention is on the Edit
menu and not on some other stuff somewhere else.  After pressing F10,
the Edit menu I saw earlier disappears.  I expect to see the Edit menu
the whole time I am trying to navigate to it.

>> What about doing it differently?  For no-toolkit Emacs, it would be
>> enough for me if the menu simply opened a *Menu* buffer with the
>> relevant menu items.  All those issues would suddenly disappear.
>
> That already exists: use tmm-menubar.

Thank you for the pointer.
It looks like the thing that pops up on F10 when menu-bar-mode is nil.
iirc I haven't used it because I found it unuseable
but a solution like that could probably work for me.
I'll have to try it a bit more.

Is there a reason, why is tmm-menubar restricted to tty?
The choice seems hardcoded in menu-bar-open.
I had to do this:
(defun x-menu-bar-open (frame)
  (with-selected-frame (or frame (selected-frame))
    (tmm-menubar)))
in order to use tmm-menubar on no-toolkit Emacs.
It would be nicer, if the cond in menu-bar-open was replaced
with run-hook-with-args-until-success and a customizable
open-menu-bar-functions variable.





  reply	other threads:[~2022-08-24 22:59 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23 20:47 bug#57372: no-toolkit menu popups do not respect emacs font configuration Tomas Hlavaty
2022-08-24  2:29 ` Eli Zaretskii
2022-08-24  8:15   ` Tomas Hlavaty
2022-08-24 10:56     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-24 11:23       ` Eli Zaretskii
2022-08-24 12:11         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-24 12:27           ` Eli Zaretskii
2022-08-24 12:34             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-24 12:43               ` Eli Zaretskii
2022-08-24 13:01                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-24 13:21                   ` Eli Zaretskii
2022-08-24 13:23                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-24 13:25                       ` Eli Zaretskii
2022-08-24 13:39                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-24 14:23                           ` Eli Zaretskii
2022-08-24 19:07                             ` Tomas Hlavaty
2022-08-24 19:36                               ` Eli Zaretskii
2022-08-24 23:10                                 ` Stefan Kangas
2022-08-25  1:08                             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-24 17:49             ` Tomas Hlavaty
2022-08-24 17:59               ` Eli Zaretskii
2022-08-24 19:01                 ` Tomas Hlavaty
2022-08-24 19:33                   ` Eli Zaretskii
2022-08-24 21:57                     ` Tomas Hlavaty
2022-08-25  1:40                       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-25  6:42                       ` Eli Zaretskii
2022-08-25 18:21                         ` Tomas Hlavaty
2022-08-25 19:02                           ` Eli Zaretskii
2022-08-26  7:13                             ` Tomas Hlavaty
2022-08-26  7:42                               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-13 20:06                             ` Tomas Hlavaty
2022-09-14  1:59                               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26  1:13                           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-25  1:28                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-25  1:26                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-25  1:25               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-24 16:15         ` Tomas Hlavaty
2022-08-24 16:32           ` Eli Zaretskii
2022-08-24 18:54             ` Tomas Hlavaty
2022-08-24 19:28               ` Eli Zaretskii
2022-08-24 22:59                 ` Tomas Hlavaty [this message]
2022-08-25  6:51                   ` Eli Zaretskii
2022-08-25 19:07                     ` Tomas Hlavaty
2022-08-25 19:15                       ` Eli Zaretskii
2022-08-26  7:19                         ` Tomas Hlavaty
2022-08-26 10:35                           ` Eli Zaretskii
2022-08-26 10:54                             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26 11:00                               ` Eli Zaretskii
2022-08-26 11:18                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26 11:31                                   ` Eli Zaretskii
2022-08-24 11:47       ` Lars Ingebrigtsen
2022-08-24 16:09       ` Tomas Hlavaty
2022-08-25  1:09         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-25 19:18           ` Tomas Hlavaty
2022-08-26  1:11             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26  6:54               ` Tomas Hlavaty

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=87zgftgsdx.fsf@logand.com \
    --to=tom@logand.com \
    --cc=57372@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.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).