From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Emanuel Berg via Users list for the GNU Emacs text editor Newsgroups: gmane.emacs.help Subject: Re: Proper use of function form Date: Mon, 27 Apr 2020 10:06:20 +0200 Message-ID: <87pnbt2w03.fsf@ebih.ebihd> References: Reply-To: Emanuel Berg Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="80644"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) To: help-gnu-emacs@gnu.org Cancel-Lock: sha1:dq3bXIT4/71D1jno5pHLq74QOMI= Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Mon Apr 27 10:07:21 2020 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jSynR-000Kuf-CO for geh-help-gnu-emacs@m.gmane-mx.org; Mon, 27 Apr 2020 10:07:21 +0200 Original-Received: from localhost ([::1]:55906 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jSynQ-0001nz-Dt for geh-help-gnu-emacs@m.gmane-mx.org; Mon, 27 Apr 2020 04:07:20 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42954) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jSymc-0001nK-CL for help-gnu-emacs@gnu.org; Mon, 27 Apr 2020 04:06:30 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.90_1) (envelope-from ) id 1jSymb-000056-P0 for help-gnu-emacs@gnu.org; Mon, 27 Apr 2020 04:06:30 -0400 Original-Received: from ciao.gmane.io ([159.69.161.202]:58586) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jSymb-0008Vx-32 for help-gnu-emacs@gnu.org; Mon, 27 Apr 2020 04:06:29 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1jSymZ-000Jyv-9g for help-gnu-emacs@gnu.org; Mon, 27 Apr 2020 10:06:27 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: help-gnu-emacs@gnu.org Mail-Copies-To: never Received-SPF: pass client-ip=159.69.161.202; envelope-from=geh-help-gnu-emacs@m.gmane-mx.org; helo=ciao.gmane.io X-detected-operating-system: by eggs.gnu.org: First seen = 2020/04/27 03:50:54 X-ACL-Warn: Detected OS = Linux 3.11 and newer [fuzzy] X-Received-From: 159.69.161.202 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:122953 Archived-At: Tim Johnson wrote: > Here is a key definition: > > (define-key jinja2-mode-map (kbd "C-c i") #'jinja2-insert-var) > > As I understand it, the sharp-quote (#') tells the > compiler that jinja2-insert-var is meant to be > a function Yes, that's what happens. I don't know what the byte-compiler does with that information tho, maybe it is just a matter of it being able to warn you if that function doesn't exist, since with the hash-quote, it knows where to look specifically... But there is also the advantage of you being able to see that something is, or supposed to be, a function. Perhaps font-lock could also be told to give it a special color, e.g. `font-lock-function-name-face', if desired - to increase seeing/reduce reading even further. > The following quotation: > > "it is always good practice to sharp quote every > symbol that is the name of a function, whether it's > going into a mapcar, an apply, a funcall, or > anything else." Well, that's what I do and it always worked. But if you seek a more scientific documentation and practical HOWTO, surely this is documented in the official manual(s)? > (setq my-keypairs '("h" my-h-func "g" my-g-func "f" my-f-func)) > > and using iteration to *programmatically* call > define-key for multiple key definitions as in > > (define-key mymap                          ;; add to keymap >     (kbd (concat ldr (nth ndx mylist)))    ;; sequence as in "g" >     (nth (+ ndx 1) mylist))                ;; > command as in my-g-func > > The form above is indeed a snippet from a defun that > I have used for years > > Would it be better to change (nth (+ ndx 1) mylist) to > (function (nth (+ ndx 1) mylist)) ? But even if that had worked all the advantages mentioned so far would be lost, right? Maybe you could initially instead of the quote use the backquote/comma, or `list', with hash-quote? -- underground experts united http://user.it.uu.se/~embe8573 https://dataswamp.org/~incal