unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard M Stallman <rms@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: sdl.web@gmail.com, emacs-devel@gnu.org
Subject: Re: Should `auto-fill-function' be a safe local variable?
Date: Thu, 08 Jan 2009 06:38:01 -0500	[thread overview]
Message-ID: <E1LKtD7-0005Qp-Rb@fencepost.gnu.org> (raw)
In-Reply-To: <jwv1vvfg4i0.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Tue, 06 Jan 2009 22:49:31 -0500)

    > If nobody makes use of the potential to specify different kinds of
    > auto-filling functions, perhaps we should replace it with a boolean
    > variable `auto-fill-mode'.

    Several major modes do make use of this potential.

We could also add a local variable `auto-fill-mode' to enable
and disable the mode, and have `auto-fill-function' by default
have the usual function for auto-filling.  Then a major mode
could set `auto-fill-function' to specify HOW to do auto-fill
when it is enabled.

However...

I think it is a bad idea for a file to enable auto filling
in its local variables list, because that's a user preference
rather than a description of the file's format.

I think the OP wanted to a file disable auto filling, not enable it.
MAYBE that really does represent some info about the file's format.
We could make nil a safe value for `auto-fill-function'
and it would allow this.




  reply	other threads:[~2009-01-08 11:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06 18:27 Should `auto-fill-function' be a safe local variable? Leo
2009-01-06 21:39 ` Stefan Monnier
2009-01-07  4:01   ` Leo
2009-01-06 22:59 ` Richard M Stallman
2009-01-07  3:49   ` Stefan Monnier
2009-01-08 11:38     ` Richard M Stallman [this message]
2009-01-09  5:33       ` Leo
2009-01-09 23:58         ` Richard M Stallman
2009-01-10  4:18           ` Leo
2009-01-10 20:33             ` Richard M Stallman
2009-01-11  3:46               ` Leo
2009-01-11 19:12                 ` Richard M Stallman
2009-01-11 21:56                   ` Reiner Steib
2009-01-12  5:28                   ` Leo
2009-01-12  6:34                     ` Miles Bader
2009-01-22  3:51   ` Leo
2009-03-31 16:22   ` Leo
2009-04-02  1:56     ` Stefan Monnier
2009-04-02 14:36       ` Leo

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=E1LKtD7-0005Qp-Rb@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=sdl.web@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).