emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Support "\n" in icomplete-separator


From: Stephen Berman
Subject: Re: [PATCH] Support "\n" in icomplete-separator
Date: Fri, 13 Nov 2020 16:09:59 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)

On Fri, 13 Nov 2020 15:52:29 +0200 Eli Zaretskii <eliz@gnu.org> wrote:

>> Date: Fri, 13 Nov 2020 13:36:41 +0000
>> From: Gregory Heytings <ghe@sdf.org>
>> cc: rudalics@gmx.at, spacibba@aol.com, monnier@iro.umontreal.ca,
>>         andreyk.mad@gmail.com, emacs-devel@gnu.org
>>
>> > No, I mean what would happen if we displayed a menu simulation by
>> > showing menu items one below the other in a buffer, instead of using the
>> > toolkit menus, or even instead of the TTY menus we have nowadays.
>>
>> Okay, now I see what you mean.  Indeed doing this for menus would not make
>> sense / would be ugly.  But of course the essential difference here is
>> that menus are not meant to be used with a keyboard
>
> Actually, menus (even GUI toolkit menus) work with the keyboard very
                   ^^^^^^^^^^^^^^^^^^^^^^
> well.  Including in Emacs.  It's true that interaction with GUI

I frequently use the keyboard to open, navigate and select items from
menues in GTK builds of Emacs, but in my no-toolkit build, I can pop
open the global menu with F10 but it responds to no further keyboard
action, only to the mouse (this is under GNU/Linux).  Is this a known
limitation of no-toolkit menues?

Steve Berman



reply via email to

[Prev in Thread] Current Thread [Next in Thread]