From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: tex-mode.el dependency on (cl) every?
Date: Mon, 17 Sep 2007 15:04:08 +0200 [thread overview]
Message-ID: <86ir69mojb.fsf@lola.quinscape.zz> (raw)
I see that we have
+(put 'tex-verbatim-environments 'safe-local-variable
+ (lambda (x) (require 'cl) (every 'stringp x)))
Couldn't we rather use the equivalent
(lambda (x) (null (delq t (mapcar 'stringp x))))
instead?
And why is this needed at all? tex-verbatim-environments is only ever
passed to regexp-opt and member, so any old value will be _safe_. So
it should be ok just to do
(put 'tex-verbatim-environments 'safe-local-variable t)
shouldn't it?
--
David Kastrup
next reply other threads:[~2007-09-17 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 13:04 David Kastrup [this message]
2007-09-17 14:07 ` tex-mode.el dependency on (cl) every? David Kastrup
2007-09-17 14:17 ` Stefan Monnier
2007-09-17 14:36 ` David Kastrup
2007-09-17 22:24 ` 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=86ir69mojb.fsf@lola.quinscape.zz \
--to=dak@gnu.org \
--cc=emacs-devel@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).