From: Kevin Ryde <user42@zip•com.au>
To: Jonathan Nieder <jrnieder@gmail•com>
Cc: "Lawrence Mitchell" <wence@gmx•li>,
"Alexandre Julliard" <julliard@winehq•org>,
git@vger•kernel.org, "David Kågedal" <davidk@lysator•liu.se>
Subject: Re: [PATCH] git.el: Don't use font-lock-compile-keywords
Date: Tue, 05 Apr 2011 09:15:41 +1000 [thread overview]
Message-ID: <871v1h38wy.fsf@blah.blah> (raw)
In-Reply-To: <20110403001902.GA25671@elie> (Jonathan Nieder's message of "Sat, 2 Apr 2011 19:19:02 -0500")
Jonathan Nieder <jrnieder@gmail•com> writes:
>
> Lawrence Mitchell wrote:
>> font-lock-add-keywords rather than font-lock-compile-keywords.
>> However, it doesn't exist in XEmacs,
Oh, I didn't realize that. In my own code I think I've only ever
set font-lock-defaults and left it at that ...
--
Newton's first law elucidated for the layman:
A body in motion continues in motion, unless it doesn't.
prev parent reply other threads:[~2011-04-04 22:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 10:59 [PATCH] git.el: Don't use font-lock-compile-keywords Lawrence Mitchell
2011-04-03 0:19 ` Jonathan Nieder
2011-04-03 17:44 ` Alexandre Julliard
2011-04-03 19:25 ` Jonathan Nieder
2011-04-03 19:26 ` Junio C Hamano
2011-04-04 23:15 ` Kevin Ryde [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871v1h38wy.fsf@blah.blah \
--to=user42@zip$(echo .)com.au \
--cc=davidk@lysator$(echo .)liu.se \
--cc=git@vger$(echo .)kernel.org \
--cc=jrnieder@gmail$(echo .)com \
--cc=julliard@winehq$(echo .)org \
--cc=wence@gmx$(echo .)li \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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