From: David Kastrup <dak@gnu.org>
Subject: Re: risky local variables
Date: Mon, 02 Oct 2006 12:26:17 +0200 [thread overview]
Message-ID: <857izjxbcm.fsf@lola.goethe.zz> (raw)
In-Reply-To: mailman.7667.1159783825.9609.help-gnu-emacs@gnu.org
Seweryn Kokot <skokot@po.opole.pl> writes:
> Hello,
>
> Normally my text files are visited with auto-fill mode but I need one
> text file that should not be auto-filled so I put in this file:
>
> %%% Local Variables:
> %%% mode: text
> %%% auto-fill-function: nil
> %%% End:
>
> but when I open this file I get the following information:
>
> The local variables list in file.txt
> contains variables that are risky (**).
>
> Do you want to apply it? You can type
> y -- to apply the local variables list
> n -- to ignore the local variables list
>
> It is a bit irritating to type y all the time. How to get rid of this
> question?
%%% auto-fill-mode: nil
would probably work.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next parent reply other threads:[~2006-10-02 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.7667.1159783825.9609.help-gnu-emacs@gnu.org>
2006-10-02 10:26 ` David Kastrup [this message]
2006-10-02 10:09 risky local variables Seweryn Kokot
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=857izjxbcm.fsf@lola.goethe.zz \
--to=dak@gnu.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.
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).