From: Chong Yidong <cyd@stupidchicken.com>
To: David Koppelman <koppel@ece.lsu.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Changes to hi-lock before release.
Date: Fri, 20 Apr 2007 15:29:31 -0400 [thread overview]
Message-ID: <87slaux2sk.fsf@stupidchicken.com> (raw)
In-Reply-To: <7wejmekgrd.fsf@ece.lsu.edu> (David Koppelman's message of "Fri\, 20 Apr 2007 14\:06\:14 -0500")
David Koppelman <koppel@ece.lsu.edu> writes:
> I believe the following changes should be made to hi-lock before
> release. The problem is that hi-lock can automatically add font-lock
> keywords when a buffer is loaded, allowing for some mischief. The
> patch sets the loading of patterns from files off by default, but
> by setting a variable the user can be prompted or can provide
> a function to determine safety. The user can still add the patterns
> by using a key sequence.
I double-checked the patch, and it looks right. So I checked it in.
Thanks very much.
next prev parent reply other threads:[~2007-04-20 19:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 19:06 Changes to hi-lock before release David Koppelman
2007-04-20 19:29 ` Chong Yidong [this message]
2007-04-21 9:20 ` Eli Zaretskii
2007-04-21 10:12 ` Johan Bockgård
2007-04-21 18:25 ` Richard Stallman
2007-04-21 19:26 ` Chong Yidong
2007-04-22 3:13 ` Eli Zaretskii
[not found] ` <E1HfGbN-0006PL-IH@fencepost.gnu.org>
2007-04-21 17:32 ` Chong Yidong
2007-04-22 0:46 ` Richard Stallman
2007-04-22 1:47 ` Glenn Morris
2007-04-23 3:48 ` Richard Stallman
2007-04-22 0:46 ` Richard Stallman
2007-04-22 2:45 ` Chong Yidong
2007-04-23 3:47 ` Richard Stallman
2007-04-23 14:39 ` Chong Yidong
2007-04-24 21:10 ` Alan Mackenzie
2007-04-24 21:34 ` David Koppelman
2007-04-25 11:53 ` Changes to hi-lock before release. PATCH Alan Mackenzie
2007-04-25 14:51 ` Changes to hi-lock before release Richard Stallman
2007-04-25 15:18 ` David Koppelman
2007-04-27 5:59 ` 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=87slaux2sk.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=koppel@ece.lsu.edu \
/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).