unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Emacs-Devel <emacs-devel@gnu.org>
Subject: Re: how to prevent font-lock from messing with a portion of text?
Date: Sat, 24 Mar 2007 02:57:07 +0100	[thread overview]
Message-ID: <46048573.4010305@gmail.com> (raw)
In-Reply-To: <EIENLHALHGIMHGDOLMIMIEBJDAAA.drew.adams@oracle.com>

Drew Adams wrote:

>> - add a font-lock-fontify-region-function so that after fontifying
>>   the region normally, you scan the region for `persistent-face'
>>   properties and copy those to the `face' property.
> 
> Right (ridiculous). Move all of `face' to `persistent-face' and then back
> again. And besides such a convoluted, heavy workaround?


Maybe just add the wanted face as 'persistent-face, remove 'fontified 
and then use a function like above? (But I am not sure how to 
"refontify". Is not turning font-lock-mode off/on a bit heavy? Though 
that new font-lock-fontify-region-function could be called directly of 
course. With some twistes then to avoid making the buffer modified.)

A problem with this solution is however that fontification must use 
font-lock-fontify-region-function etc. All major modes does not do that.

  reply	other threads:[~2007-03-24  1:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22 16:56 how to prevent font-lock from messing with a portion of text? Drew Adams
2007-03-22 18:35 ` Stefan Monnier
2007-03-22 19:20   ` Drew Adams
2007-03-22 20:09     ` Lennart Borgman (gmail)
2007-03-22 20:49       ` Drew Adams
2007-03-22 21:40         ` Lennart Borgman (gmail)
2007-03-22 21:57     ` Miles Bader
2007-03-23 16:07     ` Stefan Monnier
2007-03-23 17:13       ` Drew Adams
2007-03-23 17:31         ` Lennart Borgman (gmail)
2007-03-23 22:36         ` Stefan Monnier
2007-03-24  1:33           ` Drew Adams
2007-03-24  1:57             ` Lennart Borgman (gmail) [this message]
2007-03-24  4:21               ` Stefan Monnier
2007-03-24  8:20                 ` Lennart Borgman (gmail)
2007-03-25  3:11                   ` Stefan Monnier
2007-03-25  3:31                     ` Lennart Borgman (gmail)
2007-03-24  4:20             ` Stefan Monnier
2007-03-26  1:48               ` Drew Adams
2007-03-26  1:59                 ` Lennart Borgman (gmail)
2007-03-26  5:52                   ` Drew Adams
2007-03-26  8:47                     ` Lennart Borgman (gmail)
2007-03-26 14:49                       ` Drew Adams
2007-03-26 13:01                 ` Stefan Monnier
2007-03-26 13:26                   ` Miles Bader
2007-03-26 15:56                     ` Drew Adams
2007-03-26 15:56                   ` Drew Adams
2007-03-26 19:11                     ` Stefan Monnier
2007-03-26 20:14                       ` Drew Adams

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=46048573.4010305@gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=drew.adams@oracle.com \
    --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).