all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: 8332@debbugs.gnu.org, rubikitch <rubikitch@ruby-lang.org>,
	Thierry Volpiatto <thierry.volpiatto@gmail.com>
Subject: bug#8332: Acknowledgement (24.0.9999; lexbind-new branch errors on M-x describe-variable lexical-binding)
Date: Thu, 24 Mar 2011 11:01:33 -0400	[thread overview]
Message-ID: <jwvr59wh8l8.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87mxklufp8.fsf@member.fsf.org> (Tassilo Horn's message of "Thu,  24 Mar 2011 08:42:59 +0100")

> After some bisectioning, I found out the culprit is anything.
> Commenting out
>   (require 'anything)
> in my .emacs, so I'll Cc-ed Thierry and Rubykitch.

Please try to only set lexical-binding via file-local variables.
This should be 100% backward compatible (i.e. only affect the files
where you've set that variable), so any new error like the above
is not normal.  There are a few rare backward incompatibilities, but
they are fairly rare (e.g. the `byte-compile' property works a bit
differently, and there are new representations for functions, so if the
code checks (eq (car foo) 'lambda) instead of using `functionp' it might
bump into problems).


        Stefan





  reply	other threads:[~2011-03-24 15:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23 20:34 bug#8332: 24.0.9999; lexbind-new branch errors on M-x describe-variable lexical-binding Tassilo Horn
     [not found] ` <handler.8332.B.130091282523164.ack@debbugs.gnu.org>
2011-03-24  7:42   ` bug#8332: Acknowledgement (24.0.9999; lexbind-new branch errors on M-x describe-variable lexical-binding) Tassilo Horn
2011-03-24 15:01     ` Stefan Monnier [this message]
2011-03-24 15:27       ` Tassilo Horn
2011-03-24 22:23         ` rubikitch
2011-03-25  1:03           ` Stefan Monnier
2011-03-25  6:58           ` Tassilo Horn

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvr59wh8l8.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=8332@debbugs.gnu.org \
    --cc=rubikitch@ruby-lang.org \
    --cc=tassilo@member.fsf.org \
    --cc=thierry.volpiatto@gmail.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.