From: Juanma Barranquero <lekktu@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Defaults for elisp-mode files
Date: Thu, 4 Oct 2012 02:59:07 +0200 [thread overview]
Message-ID: <CAAeL0SSeFJxRO6sA-yW8v0ow8sQMmLTcmfM8jnqhD_i737d_Og@mail.gmail.com> (raw)
In-Reply-To: <jwvr4pfbfm7.fsf-monnier+emacs@gnu.org>
On Wed, Oct 3, 2012 at 8:06 PM, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> But for the lexical-binding setting, it seems less obvious how to handle
> such a switch (other than start warning any file which doesn't set it
> explicitly to t or nil, and after a while change the default, and after
> yet another while remove the warning, the whole process taking probably
> more than 10 years). Any suggestion would be welcome.
Why can't we set lexical-binding from .dir-locals, so it would
automatically "convert" all the lisp packages in the sources (meaning,
we will soon discover the ones that break and we can protect them with
-*- lexical-binding: nil -*-).
That has the advantadge that it wouldn't impact third-party code
unless the maintainters chose to add lexical-bindings to their
.dir-locals or their files.
Juanma
next prev parent reply other threads:[~2012-10-04 0:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 18:06 Defaults for elisp-mode files Stefan Monnier
2012-10-03 18:22 ` Drew Adams
2012-10-03 18:41 ` Christopher Schmidt
2012-10-04 0:59 ` Juanma Barranquero [this message]
2012-10-04 1:29 ` Stephen J. Turnbull
2012-10-04 3:48 ` Stefan Monnier
2012-10-04 3:56 ` Christopher Monsanto
2012-10-04 14:15 ` Juanma Barranquero
2012-10-04 15:37 ` Christopher Monsanto
2012-10-04 16:24 ` Juanma Barranquero
2012-10-04 17:00 ` Andreas Schwab
2012-10-04 17:12 ` Juanma Barranquero
2012-10-04 17:07 ` Stephen J. Turnbull
2012-10-04 6:01 ` Stephen J. Turnbull
2012-10-04 19:10 ` Andreas Röhler
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=CAAeL0SSeFJxRO6sA-yW8v0ow8sQMmLTcmfM8jnqhD_i737d_Og@mail.gmail.com \
--to=lekktu@gmail.com \
--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 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.