all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ergus <spacibba@aol.com>
To: tomas@tuxteam.de
Cc: emacs-devel@gnu.org
Subject: Re: xterm [menu] key definition
Date: Wed, 25 Aug 2021 13:31:36 +0200	[thread overview]
Message-ID: <20210825113136.xi6ed47hujm4uhkt@Ergus> (raw)
In-Reply-To: <20210825104717.GA22741@tuxteam.de>

On Wed, Aug 25, 2021 at 12:47:17PM +0200, tomas@tuxteam.de wrote:
>On Wed, Aug 25, 2021 at 11:32:12AM +0200, Ergus wrote:
>> On Wed, Aug 25, 2021 at 09:06:40AM +0200, tomas@tuxteam.de wrote:
>
>[...]
>
>> >I wouldn't expect an "xterm API". The "API" are the escape sequences :)
>> >
>> I meant an api to ask xterm about modifyFunctionKeys value for a general
>> solution.
>
>I see.
>
>> For this specific case kf16=\E[29~ unconditionally; so we don't care.
>
>FWIW, I am surprised about the correspondence "F16" to "menu". For
>one, most (PC) keyboards only go up to 12 [1], for the other, CUA [2]
>(the only "written" standard I can come up on those things) states
>that "menu" is F10. Probably some popular application started with
>it or something.
>
There is a miss understanding here. What is normally called menu in
  <f10> refers to the menu-bar in all the applications (usually the File
  section in the menu-bar; something emacs gui already has and works fine
  BTW)

The [menu] key we are discussing here is a completely different
beast. Associated normally with right click action. You can try on any
editor, office or graphical application around.

>> >When you say "emacs assumes" you are referring to some "GUI guts"?
>> >
>> I am referring to what emacs understand for the same key on gui or xterm.
>
>OK.
>
>> >>Part of my intention is to minimize the "special" customization required
>> >>when using xterm+emacs (either in Xdefaults or in init.el); any fancy
>> >>more specific customization can be made latter by the user when he gets
>> >>familiar with the rest of the environment (GNU/Linux, xterm, emacs,
>> >>Elisp, the command line interface, the OS configuration system...) for
>> >>new users it is like getting into Narnia the fist week/month.
>
>The best, IMO, would be to agree upon whatever escape sequences for
>those newer keys and convince terminal folks to implement that.
>
This is already in xterm give a look to the Yuri Khan email:

https://github.com/Maximus5/xterm/blob/master/src/input.c#L1429
https://github.com/Maximus5/xterm/blob/master/src/input.c#L1460

>Guessing around (aka "F16" == "menu") is only going to make the tangle
>deeper.  It is deep already :)

>> >The lowest common denominator would be to assume that there is no
>> >"print" (aka PrintSc) key, same for "menu", more so for "windows".
>> >
>> I started the thread asking because now I understand that in general the
>> [menu] key seems to emit the same than <f16>. What I don't know is if
>> the PrintSc does the same with a another key.
>
>See above.
>
>> The other think clear now is that \E[29~ is NOT [print]. It is either
>> <f16> (from xterm's source code and terminfo) or [menu] (as menu key
>> seems to emit the same X event in all the cases.)
>>
>> So [menu] in general seems to be a shortcut for <f16>? Probably you know
>> better than me about this conventions or where can be found in some X
>> sources?
>
>See above. I didn't know that and I can't even find hints about who
>has come up with it. If xterm maps both to the same escape sequence,
>perhaps one avenue could be to research whence that commit comes and
>ask the person whodunit. Perhaps she's still around :-)
>
>Who knows... perhaps that was the labeling on one particularly venerated
>workstation at some MIT lab ;-)
>
xterm maintenance is currently a single man effort; the other emulators
try to keep compatibility with it; including applications like tmux.

>> >>I expect that most of the emacs features work and behave as similar as
>> >>possible when using the xterm, tty or gui without customization,
>> >>everything out of the box.
>
>Don't get me wrong, I understand your goal and think it's a laudable
>one, but the layers you are talking to didn't know a "menu" key (or
>a "print" key, for that) exists when they were born. Some people
>(me included) don't have yet a "menu" key on their keyboards (nor an
>F16 key). So that kind of keyboards is around and will be with us
>for the next, say, 5 to 10 years. By then, we'll have a new key,
>this time it'll be Google's vanity key, say "search" [4].
>
The probably google will make it's kay an alias for fX where X is any
vale > 12 not taken already.

>Relying too much on a "menu" key being there doesn't look to me like
>a smart move just yet.
>
>But, of course, getting those exotic keys into the different terms
>(I'd try to include the Linux console) seems a worthy goal in
>itself.
>
>Perhaps a smart move would be to get a Linux distro (e.g. Debian)
>on board? They go to some lengths in making keyboard behaviour
>uniform across worlds (e.g. xterm/Linux console).
>
look at the links above.

>Cheers
>
>[1] https://xkcd.com/670/
>[2] https://en.wikipedia.org/wiki/Common_User_Access
>[3] It's a refurb Thinkpad X230, which was introduced around 2012.
>   So it's not /quite yet/ a museum piece. The last ones in refurb
>   shops seem to have been flushed out pretty recently, possibly
>   accelerated by pandemics.
>[4] I should set up a bet.
>
> - t





  reply	other threads:[~2021-08-25 11:31 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210819024728.kgnf6jmpakqdto4p.ref@Ergus>
2021-08-19  2:47 ` xterm [menu] key definition Ergus
2021-08-23 17:53   ` Ergus
2021-08-24  6:37   ` Juri Linkov
2021-08-24  8:19     ` Ergus
2021-08-24  8:34       ` tomas
2021-08-24  9:17         ` Ergus
2021-08-24 10:03           ` Andreas Schwab
2021-08-24 11:00           ` tomas
2021-08-24 15:30             ` Ergus
2021-08-25  7:06               ` tomas
2021-08-25  9:32                 ` Ergus
2021-08-25 10:47                   ` tomas
2021-08-25 11:31                     ` Ergus [this message]
2021-08-26  5:47                     ` chad
2021-08-26  7:14                       ` tomas
2021-08-26  8:16                       ` Andreas Schwab
2021-08-24  8:34       ` Andreas Schwab
2021-08-24  9:07         ` Ergus
2021-08-24 22:05       ` Stefan Monnier
2021-08-25  6:38         ` tomas
2021-08-25  9:04           ` Ergus
2021-08-24 16:40     ` Ergus via Emacs development discussions.
2021-08-24 17:28       ` Eli Zaretskii
2021-08-24 18:09         ` Juri Linkov
2021-08-24 20:23         ` Ergus
2021-08-25 11:27           ` Eli Zaretskii
2021-08-25 11:53             ` Ergus
2021-08-24 22:16       ` Stefan Monnier
2021-08-24 23:20         ` Ergus
2021-08-25  2:53           ` Stefan Monnier
2021-08-25  8:58             ` Ergus
2021-08-25 14:13               ` Stefan Monnier
2021-08-25 11:34             ` Eli Zaretskii
2021-08-25 22:41               ` Stefan Monnier
2021-08-26  6:55                 ` Eli Zaretskii
2021-08-26  7:17                   ` Ergus
2021-08-26  7:23                     ` Eli Zaretskii
2021-08-26 12:52                   ` Ergus
2021-08-26 13:48                     ` Eli Zaretskii
2021-08-26 13:59                   ` Stefan Monnier
2021-08-26 14:51                     ` Andreas Schwab
2021-08-26 15:52                     ` Eli Zaretskii
2021-08-25  7:10           ` tomas
2021-08-25  8:02           ` Andreas Schwab
2021-08-25  6:36         ` Yuri Khan
2021-08-25  7:17           ` tomas
2021-08-25  9:00           ` Ergus
2021-08-25 14:01         ` Olaf Rogalsky
     [not found]   ` <87k0kcovp4.fsf@no.workgroup>
2021-08-25 12:09     ` Gregor Zattler

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210825113136.xi6ed47hujm4uhkt@Ergus \
    --to=spacibba@aol.com \
    --cc=emacs-devel@gnu.org \
    --cc=tomas@tuxteam.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.