unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jose A. Ortega Ruiz" <jao@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: problem with font lock
Date: Fri, 15 Jan 2010 21:15:59 +0100	[thread overview]
Message-ID: <87bpgvf7k0.fsf@newton.homeunix.net> (raw)
In-Reply-To: 27179603.post@talk.nabble.com

"alin.s" <alinsoar@voila.fr> writes:

> begin by understanding which module tries to paint the region you expect.
>
> There are many different  : overlays, font-lock based on classes of syntax,
> font-lock based on regular expressions, etc.
>
> You must have patience and discover which of these modules paints every
> character/word from the buffer where you are interested.
>
> Look into the elisp manual.
>
> When you comment a line you should expect that the author of the minor/major
> modes actives defined the fontification using the font lock for the
> "comment" syntax class; its color is defined in font-lock-comment-face'. But
> it is not sure that the commented line was fontified so.

When it appears, the problem happens with many different modes (elisp,
c, c++, my own variants of those two, haskell, scheme) and not only
for comments: fontification of any syntactical element only happens when
explicitly requested. So looking for a problem with font lock sounds as
a good, if not sure, bet for now.

Thanks for the advice!
jao





      reply	other threads:[~2010-01-15 20:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-15 12:14 problem with font lock Jose A. Ortega Ruiz
2010-01-15 14:19 ` Stefan Monnier
2010-01-19 21:54   ` Jose A. Ortega Ruiz
2010-01-15 14:43 ` Eli Zaretskii
2010-01-15 16:27   ` Jose A. Ortega Ruiz
2010-01-15 17:49     ` Stefan Monnier
2010-01-15 16:24 ` alin.s
2010-01-15 20:15   ` Jose A. Ortega Ruiz [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=87bpgvf7k0.fsf@newton.homeunix.net \
    --to=jao@gnu.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).