all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 27490@debbugs.gnu.org
Subject: bug#27490: 24.5; Elisp manual explanation of `function-key-map' and its inheritors
Date: Sun, 21 Jul 2019 20:54:11 +0300	[thread overview]
Message-ID: <83o91nqnng.fsf@gnu.org> (raw)
In-Reply-To: <87blxn47lq.fsf@mouse.gnus.org> (message from Lars Ingebrigtsen on Sun, 21 Jul 2019 19:31:45 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: drew.adams@oracle.com,  27490@debbugs.gnu.org
> Date: Sun, 21 Jul 2019 19:31:45 +0200
> 
> >> The only way to affect the behavior of keys within Emacs is through
> >> @code{xmodmap} (outside Emacs) or @code{define-key} (inside Emacs).  The
> >> @code{define-key} command should be used in conjunction with the
> >> @code{function-key-map} map.  For instance,
> >> 
> >> @lisp
> >> (define-key function-key-map [M-@key{TAB}] [?\M-\t])
> >> @end lisp
> >
> > Where did you find this?  I must be blind, because I don't see this
> > passage in the manual.
> 
> It's in the "X key translations for Emacs" node in misc/efaq.texi, which
> I guess isn't part of the manual.

Ah, okay.  Yes, that part of the FAQ is obsolete and should be fixed.





  reply	other threads:[~2019-07-21 17:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-25 20:33 bug#27490: 24.5; Elisp manual explanation of `function-key-map' and its inheritors Drew Adams
2019-07-21 15:33 ` Lars Ingebrigtsen
2019-07-21 16:39   ` Eli Zaretskii
2019-07-21 17:31     ` Lars Ingebrigtsen
2019-07-21 17:54       ` Eli Zaretskii [this message]
2019-07-21 18:16         ` Lars Ingebrigtsen
2019-07-23 14:58           ` Eli Zaretskii
2019-07-23 17:16             ` Lars Ingebrigtsen

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=83o91nqnng.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=27490@debbugs.gnu.org \
    --cc=larsi@gnus.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.