unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: emacs-devel@gnu.org
Subject: Re: set-text-properties and jit-lock-mode
Date: Sun, 21 Feb 2016 22:30:31 +0200	[thread overview]
Message-ID: <83d1rpn6vs.fsf@gnu.org> (raw)
In-Reply-To: <m24md20wnc.fsf@polytechnique.org> (message from Alan Schmitt on Sun, 21 Feb 2016 19:02:31 +0100)

> From: Alan Schmitt <alan.schmitt@polytechnique.org>
> Date: Sun, 21 Feb 2016 19:02:31 +0100
> 
> The problem: if jit-lock-mode it t, then using set-text-properties to
> change the face does not work.
> 
> To reproduce: start emacs with -Q. In the scratch buffer, type "foo".
> Then evaluate:
> (set-text-properties 192 195 (list 'face 'italic))
> 
> Nothing changes, and when I do a `describe-char' on one letter of "foo"
> I don't see the face.
> 
> If I then evaluate
> (setq jit-lock-mode nil)
> (set-text-properties 192 195 (list 'face 'italic))
> 
> then I see the face change to italic, confirmed by `describe-char'.
> 
> As `set-text-properties' is a function in C, I don't know how to look at
> its source (any pointers on how to do this would be great).

You don't need to look at its source.  The documentation clearly says
that it completely replaces the property list of the specified region
with the properties you specify as its arguments.

> Is it supposed not to work for faces when jit-lock is on?

Yes.  Font-lock overwrites the 'face' text properties with its own,
because it uses set-text-properties.



  parent reply	other threads:[~2016-02-21 20:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-21 18:02 set-text-properties and jit-lock-mode Alan Schmitt
2016-02-21 19:04 ` Alan Mackenzie
2016-02-22  7:29   ` Alan Schmitt
2016-02-24  3:40   ` Stefan Monnier
2016-02-21 20:30 ` Eli Zaretskii [this message]
2016-02-22  7:38   ` Alan Schmitt
2016-02-22  8:51     ` Anders Lindgren
2016-02-22  9:02       ` Alan Schmitt

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=83d1rpn6vs.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=alan.schmitt@polytechnique.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).