Gnus development mailing list
 help / color / mirror / Atom feed
From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: local variables and Gnus security
Date: 11 Mar 1999 18:44:26 +0100	[thread overview]
Message-ID: <rjpv6fj4zp.fsf@my.dina.kvl.dk> (raw)
In-Reply-To: <m2aexl4k6z.fsf@pc.sunweb.ch>

Robert Epprecht <epprecht@sunweb.ch> writes:

> Felix Lee <flee@teleport.com> writes:
> 
> > what version emacs are you using?  in emacs 20.3 there's no
> > `inhibit-local-variables'.  it's `enable-local-variables'
> > (and there's also `enable-local-eval').
> 
> uups...
> Yes, I'm running emacs 20.3 and didn't notice that this variable
> isn't there any more...

It is not nice of Stallman to remove a security related option like
that.

In any case, Gnus should bind `enable-local-eval' to nil before
loading any files.


  reply	other threads:[~1999-03-11 17:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-09  0:02 article won't display, errors says article buffer read-only Doug Bagley
1999-03-09 19:55 ` local variables and Gnus security Robert Epprecht
1999-03-10  9:47   ` Felix Lee
1999-03-10 12:12     ` Robert Epprecht
1999-03-11 17:44       ` Per Abrahamsen [this message]
1999-03-11 20:29         ` Karl Eichwalder
1999-03-11 21:56         ` Felix Lee
1999-03-12 11:35         ` Jan Vroonhof
1999-03-14 16:08         ` Lars Magne Ingebrigtsen
1999-03-10 13:42   ` Per Abrahamsen
1999-03-10 18:52     ` François Pinard
1999-03-10 19:04       ` François Pinard
1999-03-11 15:37         ` empiric
1999-03-11 15:55           ` Kai.Grossjohann
1999-03-11 18:01           ` Hallvard B Furuseth
1999-03-10 20:01       ` Alan Shutko
1999-03-10 21:55     ` Robert Epprecht
1999-03-14 16:04   ` Lars Magne Ingebrigtsen
1999-03-12 15:34 ` article won't display, errors says article buffer read-only Doug Bagley
1999-03-14 16:03 ` Lars Magne Ingebrigtsen

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=rjpv6fj4zp.fsf@my.dina.kvl.dk \
    --to=abraham@dina.kvl.dk \
    /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 NNTP newsgroup(s).