git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] git.el: Don't use font-lock-compile-keywords

From
KRKevin Ryde <user42@zip.com.au>
Date
Apr 4, 2011, 23:15 UTC
Message-ID
<871v1h38wy.fsf@blah.blah>
In-Reply-To
<20110403001902.GA25671@elie>
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.
Previous: Junio C Hamano
Message 6 of 6 in “git.el: Don't use font-lock-compile-keywords”
  1. git.el: Don't use font-lock-compile-keywordsLawrence Mitchell, Feb 4, 2011
  2. Jonathan NiederApr 3, 2011
  3. Alexandre JulliardApr 3, 2011
  4. Jonathan NiederApr 3, 2011
  5. Junio C HamanoApr 3, 2011
  6. Kevin RydeApr 4, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.