all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: xah@xahlee.org, 1111@debbugs.gnu.org, stefan@marxist.se,
	npostavs@gmail.com
Subject: bug#1111: describe-key's key notation display inconsistency
Date: Fri, 09 Aug 2019 09:38:38 +0300	[thread overview]
Message-ID: <83mugialn5.fsf@gnu.org> (raw)
In-Reply-To: <76f8d8ae-83ef-4062-881d-8e60a2a148a6@default> (message from Drew Adams on Thu, 8 Aug 2019 17:14:44 -0700 (PDT))

> From: Drew Adams <drew.adams@oracle.com>
> Cc: xah lee <xah@xahlee.org>, 1111@debbugs.gnu.org,
>  Stefan Kangas <stefan@marxist.se>
> 
> (elisp) `Function Keys':
> 
>   Function keys are represented in Emacs Lisp as
>   symbols; the symbol's name is the function key's
>   label, in lower case.
> 
>   For example, pressing a key labeled <F1> generates
>   an input event represented by the symbol 'f1'.
> 
> (Note: not the symbol `<f1>' - see my statement that
> I think the doc that says that the angle brackets
> are part of the event name is incorrect, per this
> doc passage.)

You are mixing keys with events produced by those keys and with the
description of those keys and events.  They are all different.





  reply	other threads:[~2019-08-09  6:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-07 15:12 bug#1111: describe-key's key notation display inconsistency xah lee
2019-08-08 12:35 ` Stefan Kangas
2019-08-08 15:47   ` Drew Adams
2019-08-08 16:03     ` Noam Postavsky
2019-08-08 17:25       ` Drew Adams
2019-08-08 18:06         ` Noam Postavsky
2019-08-08 22:15           ` Drew Adams
2019-08-08 23:05             ` Noam Postavsky
2019-08-09  0:14               ` Drew Adams
2019-08-09  6:38                 ` Eli Zaretskii [this message]
2021-09-24 22:00 ` Stefan Kangas
2021-09-24 22:49   ` bug#1111: [External] : " Drew Adams
2021-09-26  5:07   ` Xah Lee

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=83mugialn5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=1111@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=npostavs@gmail.com \
    --cc=stefan@marxist.se \
    --cc=xah@xahlee.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 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.