From: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: trivial bug of font-lock in Change Log mode.
Date: Fri, 27 May 2005 14:45:29 +0300 [thread overview]
Message-ID: <87psvcx5yk.fsf@jurta.org> (raw)
In-Reply-To: <E1Db6jn-0004kV-00@etlken> (Kenichi Handa's message of "Thu, 26 May 2005 10:00:39 +0900")
> For instance, emacs/src/ChangeLog has this line near the
> end.
>
> See ChangeLog.9 for earlier changes.
>
> When I visit this file and turn on font-lock mode, "See
> Change" (the first 10 characters) gets change-log-data-face.
>
> It seems that the attached change fix the problem, but, it
> may fail if there are some other old style than these two:
>
> Wed Aug 21 03:51:42 1996
> 2005-05-16
>
> Could someone verify it?
This will cover most ChangeLog files, but I'd rather move your new
restricted date regexp to a new special variable `change-log-date-regexp'
(and using it in `change-log-font-lock-keywords'), thus allowing users
to override it by file local variables in ChangeLog files with a different
date format.
Also it seems that the format for arbitrary text in ChangeLog files is
a line beginning with two spaces. Look for example in the same file
emacs/src/ChangeLog for the copyright statement. It is indented with
two spaces, probably with the intention to not highlight it as a date:
Copyright (C) 2001, 02, 04 Free Software Foundation, Inc.
Copying and distribution of this file, with or without modification,
are permitted provided the copyright notice and this notice are preserved.
--
Juri Linkov
http://www.jurta.org/emacs/
prev parent reply other threads:[~2005-05-27 11:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 1:00 trivial bug of font-lock in Change Log mode Kenichi Handa
2005-05-26 14:54 ` Richard Stallman
2005-05-27 0:32 ` Kenichi Handa
2005-05-27 14:20 ` Richard Stallman
2005-05-28 0:48 ` Kenichi Handa
2005-05-28 11:52 ` Richard Stallman
2005-06-10 2:25 ` Kenichi Handa
2005-05-27 11:45 ` Juri Linkov [this message]
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=87psvcx5yk.fsf@jurta.org \
--to=juri@jurta.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).