From: Steven L Baur <steve@xemacs.org>
Subject: Re: Possible security hole? nnfolder evaluates local variables..
Date: 16 May 1997 22:22:16 -0700 [thread overview]
Message-ID: <m2bu6awu47.fsf@altair.xemacs.org> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 17 May 1997 05:36:07 +0200
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> I have no idea why nnheaderxm.el includes the copies of these
> functions at all. Steven, you're the one who put them back in after I
> removed them -- was it an XEmacs 19.13 thing or something?
I recall that (digging ...) September Gnus v0.27 removed by you,
September Gnus v0.28 restored by me.
Tue Jan 16 17:25:28 1996 Steven L. Baur <steve@miranova.com>
...
* gnus-xmas.el (insert-file-contents-literally): Restored from
v0.26 nnheader.el since XEmacs 19.13 doesn't have this function.
This was the period I was working around an extremely ugly XEmacs
internals bug that interacted very badly with nnmh.
If this is the reason those functions are still there, I think it's
safe to kill them now. :-)
> In comparison, the function used under Emacs is rather small and
> straightforward:
> (defun nnheader-find-file-noselect (&rest args)
> (let ((format-alist nil)
> (auto-mode-alist (nnheader-auto-mode-alist))
> (default-major-mode 'fundamental-mode)
> (enable-local-variables nil)
> (after-insert-file-functions nil))
> (apply 'find-file-noselect args)))
> Shouldn't this work under XEmacs as well?
It looks O.K. to me.
--
steve@calag.com baur
Unsolicited commercial e-mail will be billed at $250/message.
next prev parent reply other threads:[~1997-05-17 5:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2oham11cj.fsf@proletcult.slip.ifi.uio.no>
1997-05-08 16:15 ` vroonhof
1997-05-08 19:54 ` Steven L Baur
1997-05-09 10:10 ` Jan Vroonhof
1997-05-17 3:36 ` Lars Magne Ingebrigtsen
1997-05-17 5:22 ` Steven L Baur [this message]
1997-05-19 0:06 ` Lars Magne Ingebrigtsen
1997-05-17 14:19 ` Hrvoje Niksic
1997-05-17 3:34 ` 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=m2bu6awu47.fsf@altair.xemacs.org \
--to=steve@xemacs.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 NNTP newsgroup(s).