unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Defaults for elisp-mode files
Date: Thu, 04 Oct 2012 19:00:13 +0200	[thread overview]
Message-ID: <m2ipaqqijm.fsf@igel.home> (raw)
In-Reply-To: <CAAeL0SScYbCno8p0E9+xB2YcXp5OZUEw7eO0vtrBezDqvdrYJA@mail.gmail.com> (Juanma Barranquero's message of "Thu, 4 Oct 2012 18:24:05 +0200")

Juanma Barranquero <lekktu@gmail.com> writes:

> But, if we have a (external-to-the-file) way to set variables for
> editing files, why not for compiling them? In fact, we already mix
> editing-time variables (like mode or tab-width) and compile-time
> 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.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."



  reply	other threads:[~2012-10-04 17:00 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 [this message]
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

  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=m2ipaqqijm.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@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 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).