From: Cecil Westerhof <Cecil@decebal.nl>
To: help-gnu-emacs@gnu.org
Subject: define-key
Date: Mon, 07 Nov 2011 22:23:33 +0100 [thread overview]
Message-ID: <87wrbbaap6.fsf@Compaq.site> (raw)
For one reason or another C-M-k does not work in gnus-summary-mode. I
tried the following:
(define-key gnus-summary-mode-map [?\C-?\M-k]
'gnus-summary-kill-thread)
But this gives:
Debugger entered--Lisp error: (invalid-read-syntax "?")
read(#<buffer *scratch*>)
preceding-sexp()
eval-last-sexp-1(nil)
eval-last-sexp(nil)
call-interactively(eval-last-sexp nil nil)
When I use:
(define-key gnus-summary-mode-map [?\C-?\M-k]
'gnus-summary-kill-thread)
I do not get an error, but the key combination does not work also.
What is the correct way to define the key combination?
--
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof
next reply other threads:[~2011-11-07 21:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 21:23 Cecil Westerhof [this message]
[not found] ` <jwvobwntl1s.fsf-monnier+gnu.emacs.help@gnu.org>
[not found] ` <87sjlzdltx.fsf@Compaq.site>
[not found] ` <jwv39dysphw.fsf-monnier+gnu.emacs.help@gnu.org>
2011-11-08 15:12 ` define-key Cecil Westerhof
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=87wrbbaap6.fsf@Compaq.site \
--to=cecil@decebal.nl \
--cc=help-gnu-emacs@gnu.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.
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).