From: bojohan+news@dd.chalmers.se (Johan Bockgård)
To: emacs-devel@gnu.org
Subject: Re: Fwd: overlay face property not used for after-string property
Date: Sun, 28 Oct 2007 16:21:11 +0100 [thread overview]
Message-ID: <yoij3avvuuxk.fsf@remote1.student.chalmers.se> (raw)
In-Reply-To: 86r6jfz3bb.fsf@macs.hw.ac.uk
Joe Wells <jbw@macs.hw.ac.uk> writes:
> Also, fixing this issue this way leaves behind the difficulty of
> adding a face property manually to a property string (before-string,
> after-string, or display) which already has face properties.
In font-lock.el we find
;;; Additional text property functions.
;; The following text property functions should be builtins. This
;; means they should be written in C and put with all the other text
;; property functions. In the meantime, those that are used by
;; font-lock.el are defined in Lisp below and given a `font-lock-'
;; prefix. Those that are not used are defined in Lisp below and
;; commented out. sm.
(defun font-lock-prepend-text-property ([...])
"Prepend to one property of the text from START to END.
Arguments PROP and VALUE specify the property and value to prepend
to the value already in place. The resulting property values are
always lists. Optional argument OBJECT is the string or buffer
containing the text."
[...]
(let ((s (propertize "abc" 'face 'bar)))
(font-lock-prepend-text-property 1 2 'face 'foo s)
s)
=> #("abc" 0 1 (face bar) 1 2 (face (foo bar)) 2 3 (face bar))
--
Johan Bockgård
next prev parent reply other threads:[~2007-10-28 15:21 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 9:00 [jbw@macs.hw.ac.uk: overlay face property not used for after-string property] Richard Stallman
2007-10-22 15:44 ` Fwd: overlay face property not used for after-string property Stefan Monnier
2007-10-24 9:49 ` Joe Wells
[not found] ` <E1Im8Y2-0000zW-Tn@fencepost.gnu.org>
2007-10-28 15:06 ` Joe Wells
2007-10-28 15:21 ` Johan Bockgård [this message]
2007-10-29 9:22 ` Richard Stallman
2007-10-29 9:57 ` Joe Wells
2007-11-03 3:58 ` Richard Stallman
2007-11-03 16:03 ` Joe Wells
2007-11-04 19:56 ` Richard Stallman
2007-11-04 23:03 ` Joe Wells
2007-11-05 8:47 ` Richard Stallman
2007-11-05 9:30 ` David Kastrup
2007-11-05 11:51 ` Joe Wells
2007-11-05 12:05 ` Joe Wells
2007-11-06 2:16 ` Richard Stallman
2007-11-06 3:30 ` Joe Wells
2007-11-06 8:30 ` Stefan Monnier
2007-11-06 9:18 ` David Kastrup
2007-11-06 10:05 ` Stefan Monnier
2007-11-07 0:15 ` Richard Stallman
2007-11-07 0:15 ` Richard Stallman
2007-11-06 2:15 ` Richard Stallman
2007-11-06 3:19 ` Joe Wells
2007-11-05 14:55 ` Stefan Monnier
2007-11-05 15:04 ` David Kastrup
2007-11-05 16:35 ` Joe Wells
2007-11-05 16:53 ` David Kastrup
2007-11-05 22:06 ` Joe Wells
2007-11-05 16:29 ` Joe Wells
2007-11-05 19:38 ` Stefan Monnier
2007-11-05 21:59 ` Joe Wells
2007-11-06 8:37 ` Richard Stallman
2007-11-06 2:16 ` Richard Stallman
2007-11-05 11:55 ` Joe Wells
2007-11-06 2:16 ` Richard Stallman
2007-11-04 19:56 ` Richard Stallman
2007-11-04 23:10 ` Joe Wells
2007-11-03 19:21 ` Stefan Monnier
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=yoij3avvuuxk.fsf@remote1.student.chalmers.se \
--to=bojohan+news@dd.chalmers.se \
--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).