unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Magnar Sveen <magnar@kodemaker.no>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Bug with lexical-binding and package-install?
Date: Mon, 19 Nov 2012 22:10:37 +0100	[thread overview]
Message-ID: <CALVcYyDnh=Vz0VvQ4KsQgQVRF21B8g+Ty201irHMw0iDwHc86A@mail.gmail.com> (raw)
In-Reply-To: <jwv4nklz6df.fsf-monnier+emacs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]

Sorry about that, I have sent a proper bug report with reproducible steps.



On Mon, Nov 19, 2012 at 9:31 PM, Stefan Monnier <monnier@iro.umontreal.ca>wrote:

> > It appears as though your first instinct about lexical-binding is
> > correct. I had a ;;; -*- lexical-binding: t -*- directive in my
> > init-packages.el file, which is responsible for downloading the
> installing
> > missing packages (of which multiple-cursors.el is one).
>
> What is "init-packages.el"?
> "grep init-package **/*.el" doesn't find anything in Emacs's trunk.
>
> I'm trying to understand how this could happen, which I find difficult
> to imagine: lexical-binding is made buffer-local in every file that is
> byte-compiled, so for an external lexical-binding setting to affect
> byte-compilation, you'd have to call `byte-compile' directly rather than
> via byte-compile-file.
> At least that's the way the code should behave.
>
> Oh, and please make it an actual bug-report rather than sending it here
> on emacs-devel.
>
>
>         Stefan
>

[-- Attachment #2: Type: text/html, Size: 1522 bytes --]

      reply	other threads:[~2012-11-19 21:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-19  6:50 Bug with lexical-binding and package-install? Magnar Sveen
2012-11-19 20:31 ` Stefan Monnier
2012-11-19 21:10   ` Magnar Sveen [this message]

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='CALVcYyDnh=Vz0VvQ4KsQgQVRF21B8g+Ty201irHMw0iDwHc86A@mail.gmail.com' \
    --to=magnar@kodemaker.no \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).