unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Tip: tty mode-line popup menus
Date: Mon, 09 Dec 2024 16:15:54 +0100	[thread overview]
Message-ID: <m2zfl4zy39.fsf@gmail.com> (raw)
In-Reply-To: <86y10odied.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 09 Dec 2024 16:45:46 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>> Date: Mon, 09 Dec 2024 09:01:46 +0100
>> 
>> When clicking on, say, the major mode indicator in the mode-line
>> different things happen, depending on whether I'm using a GUI or tty
>> Emacs (-nw):
>> 
>> - GUI (NS In may case): a popup menu opens on down-mpuse-1 and stays
>>   open when I release the mouse button.
>> 
>> - Tty: a popup menu opens on down-mouse-1 and is closed as soon as I
>>   release the mouse button. If the mouse is over a menu item[B releasing
>>   the button also selects the menu item.
>
> Yes.  TTY menus behave like the no-toolkit build of Emacs behaves,
> because they share some of the code and the general design.
>
>> I don't like the tty behavior.
>
> You don't like it because you are used to how the various GUI toolkits
> behave: they leave the menu displayed when you release the mouse
> button.  But Emacs has always produced both kinds of behaviors,
> depending on the toolkit (or lack thereof).  The reason for popping
> down a menu on mouse release is that otherwise one needs a separate
> event loop (which toolkits have and TTY mouse doesn't).

Yes, I remember the times. I didn't like it then either, with a mouse
:-).

>
>> It is fiddly with a track pad, which I normally use, leading to
>> inadvertent menu selections. Furthermore, keyboard operation of the
>> menu seems impossible.
>
> ??? Of course, it possible: type F10, and then use arrow keys to
> navigate and RET to select.

Doesn't work for me.

Without doing the changes I posted, I down-mouse-1 on something in the
mode-line having a menu. When I release the mouse, the menu is gone, as
I described. When I press F10, keeping the mouse button pressed, the
menu also disappears.

With the changes applied, mouse-1 opens the menu, and I then can use
cursor keys, RET, and so on. No F10 needed. 



  reply	other threads:[~2024-12-09 15:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-09  8:01 Tip: tty mode-line popup menus Gerd Möllmann
2024-12-09 10:40 ` Jean Louis
2024-12-09 14:58   ` Eli Zaretskii
2024-12-09 14:45 ` Eli Zaretskii
2024-12-09 15:15   ` Gerd Möllmann [this message]
2024-12-09 16:24     ` Eli Zaretskii
2024-12-09 21:54 ` Petteri Hintsanen
2024-12-10  3:32   ` Gerd Möllmann
2024-12-09 22:59 ` Stefan Kangas
2024-12-10  6:14   ` Gerd Möllmann
2024-12-10  9:32     ` Gerd Möllmann
2024-12-10 10:09       ` Gerd Möllmann
2024-12-10 13:15         ` Gerd Möllmann

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=m2zfl4zy39.fsf@gmail.com \
    --to=gerd.moellmann@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.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).