unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: Copying preserves font-lock-face
Date: Sun, 24 Sep 2006 11:43:10 +0200	[thread overview]
Message-ID: <4516532E.8040906@gmx.at> (raw)
In-Reply-To: <17686.8709.23521.874061@kahikatea.snap.net.nz>

 > Yes but face and font-lock-face are different character properties and I'm
 > talking about the latter.

I don't understand where you get a `font-lock-face' (sic) property from
but you can add it to `font-lock-extra-managed-props'.

 >  >  > Is there a reason why font-lock-face should be preserved on copying?
 >  >
 >  > In some rare cases, I find it useful to see remnants of faces assigned
 >  > by font-lock when I copy a stretch of code to a plain text buffer.
 >  > Hence, in principle, preserving such face properties does not seem
 >  > wrong.
 >
 > Are faces assigned by font-lock and font-lock-faces the same thing?

`font-lock-apply-highlight' and the functions that append or prepend
text properties do things like (put-text-property start end 'face val),
hence they assign a `face' property, not a `font-lock-face' property.
Can you find out how a `font-lock-face' text property gets assigned on
your system?

  reply	other threads:[~2006-09-24  9:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-23  0:43 Copying preserves font-lock-face Nick Roberts
2006-09-23 16:12 ` martin rudalics
2006-09-24  6:13   ` Nick Roberts
2006-09-24  9:43     ` martin rudalics [this message]
2006-09-24 21:07       ` Nick Roberts
2006-09-25  2:22       ` Miles Bader
2006-09-25  3:17       ` Richard Stallman
2006-09-25 22:02         ` Chong Yidong
2006-09-26 15:41           ` Richard Stallman
2006-09-26 17:02             ` Stefan Monnier
2006-09-26 22:10               ` Richard Stallman
2006-09-23 18:01 ` Richard Stallman
2006-09-25 22:32   ` Kevin Rodgers
2006-09-26 15:41     ` Richard Stallman
2006-10-02  4:04       ` Richard Stallman

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=4516532E.8040906@gmx.at \
    --to=rudalics@gmx.at \
    --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).