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: ;; Local variables: (was: Re: The function =?utf-8?Q?=E2=80=98cl-?= =?utf-8?Q?set-difference=E2=80=99?= might not be defined at runtime) Date: Wed, 15 Apr 2020 19:14:03 +0200 Message-ID: <87zhbcfz8k.fsf_-_@ebih.ebihd> References: <877dyi2btk.fsf@disroot.org> <87zhbe7x87.fsf@gmail.com> <874ktl3oxb.fsf@disroot.org> <87v9m19a63.fsf@gmail.com> <871rop3mj0.fsf@disroot.org> <87r1wp95u3.fsf@gmail.com> <87y2qx237b.fsf@disroot.org> <87tv1l8iz6.fsf@ebih.ebihd> <20200415070046.GA17630@tuxteam.de> 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="69401"; 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:TKylHkM9b+LPgPNVCyZmCiT+17s= Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Wed Apr 15 19:14:57 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 1jOlcm-000Hwx-TT for geh-help-gnu-emacs@m.gmane-mx.org; Wed, 15 Apr 2020 19:14:56 +0200 Original-Received: from localhost ([::1]:52884 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jOlcl-0007QJ-Vv for geh-help-gnu-emacs@m.gmane-mx.org; Wed, 15 Apr 2020 13:14:56 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41620) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jOlc5-0007NZ-MH for help-gnu-emacs@gnu.org; Wed, 15 Apr 2020 13:14:14 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jOlc4-0007RR-Cc for help-gnu-emacs@gnu.org; Wed, 15 Apr 2020 13:14:13 -0400 Original-Received: from ciao.gmane.io ([159.69.161.202]:42224) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1jOlc4-0007QR-6C for help-gnu-emacs@gnu.org; Wed, 15 Apr 2020 13:14:12 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1jOlc1-000H4T-2G for help-gnu-emacs@gnu.org; Wed, 15 Apr 2020 19:14:09 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: help-gnu-emacs@gnu.org Mail-Copies-To: never X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [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:122833 Archived-At: tomas wrote: >> [...] what does this mean? >> >> ;; Local variables: >> ;; byte-compile-dynamic: t >> ;; End: > > Quoth "describe-variable" (aka C-h v): > > byte-compile-dynamic is a variable defined in > ‘bytecomp.el’. Its value is nil > > This variable is obsolete since 27.1; not > worthwhile any more. This variable is safe as > a file local variable if its value satisfies the > predicate ‘booleanp’. Probably introduced at or > before Emacs version 19.29. > > Documentation: > If non-nil, compile function bodies so they load > lazily. They are hidden in comments in the compiled > file, and each one is brought into core when the > function is called. > > To enable this option, make it a file-local variable > in the source file you want it to apply to. > For example, add -*-byte-compile-dynamic: t;-*- on > the first line. > > When this option is true, if you load the compiled > file and then move it, the functions you loaded will > not be able to run. > > So, if your Emacs is new enough, it's just a comment. > Otherwise, it hides functions in comments ;-D Yes, but I meant the comment/variable syntax, which I haven't see before. In the particular variable's docstring, they mention -*- byte-compile-dynamic: t -*- so how does that differ from ;; Local variables: ;; byte-compile-dynamic: t ;; End: ? As for the syntax, I tried with this and then did `emacs-lisp-mode', what happened was it popped up a warning telling me the values were possibly unsafe - what does that mean? ;; Local variables: ;; local-test-var: t ;; End: When I replied they were safe this line appeared in the `custom-file' file, which I don't care for and prefer to be blank or not in use '(safe-local-variable-values (quote ((local-test-var . t)))) I tried to do it manually like this, with a new variable name to prevent possible interference, but it didn't work (safe-local-variable-values '((local-test-var-1 . t))) ;; Local variables: ;; local-test-var-1: t ;; End: because safe-local-variable-values isn't a defined function, maybe custom just looks for it when it parses custom-file. Maybe one can disable custom's operations altogether by setting custom-file to nil? -- underground experts united http://user.it.uu.se/~embe8573 https://dataswamp.org/~incal