From: Juanma Barranquero <lekktu@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: emacs-devel@gnu.org
Subject: Re: Defaults for elisp-mode files
Date: Thu, 4 Oct 2012 19:12:40 +0200 [thread overview]
Message-ID: <CAAeL0STNUYqz0pc1Ub-KXGAPDgsKQeVmbtvHWZaGPeJ2Zy5_og@mail.gmail.com> (raw)
In-Reply-To: <m2ipaqqijm.fsf@igel.home>
On Thu, Oct 4, 2012 at 7:00 PM, Andreas Schwab <schwab@linux-m68k.org> wrote:
>> variables (byte-compile-dynamic, generated-autoload-file,
>> no-byte-compile, no-update-autoloads, lexical-binding itself) through
>> the same mechanism.
>
> You need to make sure that such settings are copied together with the
> file when installing it somewhere else.
Yes, and no, I think. If you're copying an entire project, presumably
you would copy any .dir-locals (or .compilation-whatever-its-name).
But, if you're copying an elisp file to fork it or add it to another
project, many of these variables could change value easily, even
lexical-binding if you're adding it to a back-compatible package.
There's nothing really specific to a given elisp file in the
assignation of autoload file, or whether update autoloads or not, for
example; that's more likely project-specific. Some properties are on
the fence, like no-byte-compile (which usually depends more on the
size of the file that anything else) .
That it's not to say that my idea was particulary good, but if you
want, as Stefan wanted, to get rid of marking individually each file
for a given property, either you change the default (and resort to
marking the hopefully fewer files that so require it), or you add
metada externally to the files.
Juanma
next prev parent reply other threads:[~2012-10-04 17:12 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
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 [this message]
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=CAAeL0STNUYqz0pc1Ub-KXGAPDgsKQeVmbtvHWZaGPeJ2Zy5_og@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.org \
/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.