home *** CD-ROM | disk | FTP | other *** search
- James Farley writes:
- >
- > I've converted from 19.4 to 19.6, and have begun using font-lock-mode
- > in lieu of lhilit, which is no longer supported. I'm trying to override
- > the default font-lock-mode highlighting (e.g. strings and comments), because
- > it interferes with other regions I have defined. It seems that, in addition
- > to the font-lock-keywords variable which is provided for the user to
- > specify customized highlighting, the font-lock-mode also gets information
- > from the "major" mode (c-mode, c++-mode, etc.) about regions which are
- > considered strings, comments, etc. I have been unable to prevent these
- > regions from being recognized and "font-locked" by font-lock-mode. Does
- > anyone have any idea how this could be done? More importantly, is there
- > any better documentation of the font-lock-mode than the comments in the
- > elisp file?
- >
- > Please email responses directly to me, since I haven't been added to the
- > Lucid Emacs mailing lists yet, and we don't receive the newsgroups at our
- > site any longer. Thanks for any help.
- >
- > Jim Farley
- > GE Corporate R&D
- > farleyja@thuban.crd.ge.com
-
- Please mail responses to the groups as well, as other people (me :-) are
- interested in taming font-lock-mode as well.
-
- --
- Danny.
-
- -------------------------------
- Dan Bar Dov
-
- Applied Materials (Israel)
- Currently at Applied Materials - Santa Clara, CA
-
- Email: danny@amil.co.il
- Phone: office (408) 235-6514
- home (408) 739-5281
- TimeZone: PST
- -------------------------------
-
-