unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>,
	Richard Stallman <rms@gnu.org>,
	kfogel@red-bean.com, emacs-devel@gnu.org
Subject: Re: [PATCH] allow function values for `enable-local-eval'
Date: Thu, 04 Jul 2002 14:46:49 -0400	[thread overview]
Message-ID: <200207041846.g64Iknu30886@rum.cs.yale.edu> (raw)
In-Reply-To: 5xy9crb7wv.fsf@kfs2.cua.dk

> "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> writes:
> 
> > >     I'm sure crackers will be happy about it.
> > >     The argument passed to `c-add-style' allows you to buffer-locally
> > >     set any variable to any value whatsoever.  Hardly "safe" in my book.
> > > 
> > > I didn't realize that.  It will be necessary then to check
> > > the arguments to c-add-style.  Still, it is better to install
> > > this checking by default than to make users install it as
> > > a customization.
> > 
> > Huh?  I personally don't see the point of using `c-add-style' in
> > the local variables section.  My understanding is that one guy did that
> > and mentioned it here, but I have seen no evidence that anybody
> > else does.
> > It seems simpler to just set the corresponding variables one by one
> > in the local variables section.
> 
> This requires that you are allowed to change the files!!!

My point is just that since it's simpler (and doesn't require confirmation)
to set the variables one by one it's unlikely that this `c-add-tyle'
is often used in local variables sections.

So I see no reason to provide special support for it.
(contrary to the case of `put', for example).


	Stefan

  reply	other threads:[~2002-07-04 18:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E17NLww-0005Cn-00@floss>
2002-06-28 17:41 ` [PATCH] allow function values for `enable-local-eval' Richard Stallman
     [not found]   ` <87u1nnnqlp.fsf@floss.i-did-not-set--mail-host-address--so-shoot-me>
2002-06-29  0:55     ` Kim F. Storm
2002-06-29 22:22       ` Richard Stallman
2002-06-30 21:37         ` Kim F. Storm
2002-07-01 14:10           ` Richard Stallman
2002-07-01 21:26             ` Kim F. Storm
2002-07-02 19:46               ` Richard Stallman
2002-07-02 20:11                 ` Stefan Monnier
2002-07-02 21:49                   ` Kim F. Storm
2002-07-04  7:07                   ` Richard Stallman
2002-07-04 15:28                     ` Stefan Monnier
2002-07-04 19:38                       ` Kim F. Storm
2002-07-04 18:46                         ` Stefan Monnier [this message]
2002-07-04 21:58                           ` Kim F. Storm
2002-07-05  1:26                           ` Miles Bader
2002-07-05 13:39                             ` Kai Großjohann
2002-07-04 19:36                     ` Kim F. Storm
2002-07-05 22:05                       ` Richard Stallman
2002-07-02 21:20                 ` Kim F. Storm
2002-07-04  7:06                   ` Richard Stallman
2002-07-04 15:13                     ` Stefan Monnier
2002-07-05 10:48                       ` Richard Stallman
2002-07-03  1:28             ` Kevin Ryde
2002-06-29 22:22     ` Richard Stallman
     [not found]       ` <877kkhlmgw.fsf@floss.i-did-not-set--mail-host-address--so-shoot-me>
2002-07-01 14:10         ` Richard Stallman

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=200207041846.g64Iknu30886@rum.cs.yale.edu \
    --to=monnier+gnu/emacs@rum.cs.yale.edu \
    --cc=emacs-devel@gnu.org \
    --cc=kfogel@red-bean.com \
    --cc=rms@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.
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).