unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 38007@debbugs.gnu.org
Subject: bug#38007: scroll-lock binding on Windows
Date: Fri, 22 Nov 2019 12:00:28 +0200	[thread overview]
Message-ID: <83d0dkw7r7.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SRrn3C5LG0es64Zk83K89yXCgVM20wwD2tOobU93JznDA@mail.gmail.com> (message from Juanma Barranquero on Fri, 22 Nov 2019 10:44:55 +0100)

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Fri, 22 Nov 2019 10:44:55 +0100
> Cc: 38007@debbugs.gnu.org
> 
> AFAICS, the X Window System Protocol (https://www.x.org/releases/X11R7.6/doc/xproto/x11protocol.html)
> defines the keysyms as numeric codes with a conventional name, in this case 
> 
> #xFF14   SCROLL LOCK
> 
> which is represented in /usr/include/X11/keysymdef.h as
> 
> #define XK_Scroll_Lock                   0xff14
> 
> but I don't know how that is converted into a keyboard event.

Yes, the latter is the missing piece.  Maybe put all of the above into
that comment.






  reply	other threads:[~2019-11-22 10:00 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 [this message]
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
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=83d0dkw7r7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=38007@debbugs.gnu.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).