From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.help Subject: Re: confusion with defining keys Date: Thu, 12 Jun 2014 03:39:10 +0200 Organization: Aioe.org NNTP Server Message-ID: <87sina6h4x.fsf@debian.uxu> References: <8761k8hw8s.fsf@yun.yagibdah.de> <87mwdjsejg.fsf@debian.uxu> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1402537225 17027 80.91.229.3 (12 Jun 2014 01:40:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 12 Jun 2014 01:40:25 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Jun 12 03:40:19 2014 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Wuu02-00043r-4v for geh-help-gnu-emacs@m.gmane.org; Thu, 12 Jun 2014 03:40:18 +0200 Original-Received: from localhost ([::1]:50049 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wuu01-0008Ca-Ix for geh-help-gnu-emacs@m.gmane.org; Wed, 11 Jun 2014 21:40:17 -0400 Original-Path: usenet.stanford.edu!news.kjsl.com!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 39 Original-NNTP-Posting-Host: SIvZRMPqRkkTHAHL6NkRuw.user.speranza.aioe.org Original-X-Complaints-To: abuse@aioe.org User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) X-Notice: Filtered by postfilter v. 0.8.2 Cancel-Lock: sha1:uOR5sl4xOkMXLIr3kFeRkHs6Imo= Mail-Copies-To: never Original-Xref: usenet.stanford.edu gnu.emacs.help:205891 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:98161 Archived-At: Stefan Monnier writes: >> The reason I do "..." is simply it is easier to >> type. So if there is some gain switching I'll do >> that, of course. > > Using [...] or (kbd "...") gains you the fact that > these work for *any* key, whereas "..." only works in > some cases. It would seem there are some exceptions to that rule! Check out the below experimentation: (global-set-key (kbd "RET") 'newline-and-indent) ; works (global-set-key "\r" 'newline-and-indent) ; works (global-set-key [RET] 'newline-and-indent) ; (error "To bind the key RET, use \"\\r\", not [RET]") (global-set-key (kbd "M-SPC") 'eat-space) ; works (global-set-key "\M- " 'eat-space) ; works (global-set-key [M-SPC] 'eat-space) ; (error "To bind the key M-SPC, use \"\\M- \", not [M-SPC]") Also, with the [...], it seems you shouldn't include the <...> for custom keys - which is good, because you don't define them that way, so it is only confusing having to use that later: (define-key input-decode-map [?\u010F] [C-semi-colon]) (global-set-key [C-semi-colon] 'string-to-cmd) (global-unset-key (kbd "")) ; everything works A (minor) drawback with [...] is less readability as the keys don't get the font-lock-string-face - customizable, of course (but watch out I guess so not lots of [stuff] get affected). -- underground experts united: http://user.it.uu.se/~embe8573