From: Michael Heerdegen <michael_heerdegen@web.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Bookmarks in EWW
Date: Mon, 27 Apr 2020 04:43:57 +0200 [thread overview]
Message-ID: <871ro9abrm.fsf@web.de> (raw)
In-Reply-To: <jwvlfmr62i1.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 19 Apr 2020 09:18:21 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Oh, right `byte-hunk-handler` is to handle top-level uses only
> (e.g. top-level uses of `require` trigger loading the file at
> compilation time, whereas they don't when not at top-level).
>
> I think you want to use `(byte-defop-compiler-1 make-local-variable)`
> and then define `byte-compile-make-local-variable`.
And now I also understand why in
#+begin_src emacs-lisp
(defun byte-compile-make-variable-buffer-local (form)
(if (and (eq (car-safe (car-safe (cdr-safe form))) 'quote)
(byte-compile-warning-enabled-p 'make-local))
(byte-compile-warn ;; <--
"`make-variable-buffer-local' not called at toplevel"))
(byte-compile-normal-call form))
#+end_src
the warning seems to be raised unconditionally. There is an additional
byte-hunk-handler for `make-variable-buffer-local', and first it seemed
redundant to me, but AFAIU it shadows the above byte-defop-compiler-1
function for top-level calls.
Michael.
next prev parent reply other threads:[~2020-04-27 2:43 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 11:26 Bookmarks in EWW Marcin Borkowski
2020-03-23 14:56 ` Drew Adams
2020-03-25 11:48 ` Marcin Borkowski
2020-03-23 20:41 ` Michael Heerdegen
2020-03-24 14:46 ` Stefan Monnier
2020-03-25 3:05 ` Michael Heerdegen
2020-03-25 3:45 ` `declare-function' docu (was: Re: Bookmarks in EWW) Emanuel Berg via Users list for the GNU Emacs text editor
2020-03-28 17:59 ` `declare-function' docu Bruno Félix Rezende Ribeiro
2020-03-28 18:38 ` Drew Adams
2020-04-09 12:30 ` Bruno Félix Rezende Ribeiro
2020-04-09 15:47 ` Drew Adams
2020-03-28 21:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-03-25 14:06 ` Bookmarks in EWW Stefan Monnier
2020-03-26 1:09 ` Michael Heerdegen
2020-03-26 4:07 ` Stefan Monnier
2020-03-27 2:07 ` Michael Heerdegen
2020-03-27 3:44 ` Stefan Monnier
2020-03-28 2:31 ` Michael Heerdegen
2020-03-28 2:55 ` Stefan Monnier
2020-04-19 3:42 ` Michael Heerdegen
2020-04-19 13:18 ` Stefan Monnier
2020-04-20 3:17 ` Michael Heerdegen
2020-04-20 13:24 ` Stefan Monnier
2020-04-21 0:59 ` Michael Heerdegen
2020-04-29 22:53 ` Michael Heerdegen
2020-04-30 1:25 ` Stefan Monnier
2020-04-30 2:08 ` Michael Heerdegen
2020-04-30 3:08 ` Stefan Monnier
2020-04-30 20:09 ` Michael Heerdegen
2020-04-27 2:43 ` Michael Heerdegen [this message]
2020-03-27 4:32 ` buffer-localness (was: Re: Bookmarks in EWW) Emanuel Berg via Users list for the GNU Emacs text editor
2020-03-25 21:48 ` Bookmarks in EWW Drew Adams
2020-03-26 2:29 ` Michael Heerdegen
2020-03-26 3:21 ` Drew Adams
2020-03-26 3:53 ` Michael Heerdegen
2020-03-26 14:02 ` Drew Adams
2020-03-26 22:33 ` Michael Heerdegen
2020-03-26 8:41 ` Marcin Borkowski
2020-03-25 11:49 ` Marcin Borkowski
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=871ro9abrm.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).