unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: lekktu@gmail.com, 38007@debbugs.gnu.org
Subject: bug#38007: scroll-lock binding on Windows
Date: Tue, 08 Feb 2022 14:25:28 +0200	[thread overview]
Message-ID: <83pmnxwnnr.fsf@gnu.org> (raw)
In-Reply-To: <87pmnxvqmi.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue,  08 Feb 2022 07:06:45 +0100)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: lekktu@gmail.com,  38007@debbugs.gnu.org
> Date: Tue, 08 Feb 2022 07:06:45 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Did you succeed in figuring out where does the "Scroll_Lock" text come
> > from?  It isn't in lispy_function_keys[] array.  On MS-Windows,
> > "scroll" does come from that array.  That's what I meant by that
> > remark.
> 
> Oh, I see.  No, I don't know where it's coming from.  I thought that we
> (under X) got the key symbols for (some) keys from X, and didn't
> maintain the database ourselves?  So we can basically get any symbol
> that the X people dream up.
> 
> I thought that was the conclusion the last time keyboard events was
> discussed, but my memory may well be faulty.

Maybe.  I simply don't know, and was quite bewildered at the time.





  parent reply	other threads:[~2022-02-08 12:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-31 17:46 bug#38007: scroll-lock binding on Windows Juanma Barranquero
2019-10-31 18:07 ` Eli Zaretskii
2019-10-31 22:59   ` Juanma Barranquero
2019-11-01  6:17     ` Eli Zaretskii
2019-11-13 16:50       ` Juanma Barranquero
2019-11-13 19:46         ` Eli Zaretskii
2019-11-22  9:06           ` Juanma Barranquero
2019-11-22  9:16             ` Eli Zaretskii
2019-11-22  9:44               ` Juanma Barranquero
2019-11-22 10:00                 ` Eli Zaretskii
2022-02-07  3:58               ` Lars Ingebrigtsen
2022-02-07 12:44                 ` Eli Zaretskii
2022-02-08  6:06                   ` Lars Ingebrigtsen
2022-02-08  9:07                     ` Andreas Schwab
2022-02-08 12:45                       ` Eli Zaretskii
2022-02-08 12:25                     ` Eli Zaretskii [this message]
2022-02-08 14:09                     ` 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=83pmnxwnnr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=38007@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=lekktu@gmail.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).