Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
emacs
emacs
Commits
9600ac7c
Commit
9600ac7c
authored
Sep 19, 2007
by
Richard M. Stallman
Browse files
(Display Property): Clarify when multiple display specs work in
parallel and when one overrides. Fix error in example.
parent
14b4fdfb
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
16 additions
and
9 deletions
+16
-9
lispref/ChangeLog
lispref/ChangeLog
+2
-0
lispref/display.texi
lispref/display.texi
+14
-9
No files found.
lispref/ChangeLog
View file @
9600ac7c
2007
-
09
-
19
Richard
Stallman
<
rms
@
gnu
.
org
>
*
display
.
texi
(
Display
Property
):
Explain
multiple
display
specs
.
Clarify
when
they
work
in
parallel
and
when
one
overrides
.
Fix
error
in
example
.
2007
-
08
-
30
Martin
Rudalics
<
rudalics
@
gmx
.
at
>
...
...
lispref/display.texi
View file @
9600ac7c
...
...
@@ -3237,15 +3237,20 @@ to use the value specified by the frame.
insert images into text, and also control other aspects of how text
displays. The value of the @code{display} property should be a
display specification, or a list or vector containing several display
specifications (which apply in parallel to the text they cover).
specifications. Display specifications generally apply in parallel to
the text they cover.
Some kinds of @code{display} properties specify something to display
instead of the text that has the property. In this case, ``the text''
means all the consecutive characters that have the same Lisp object as
their @code{display} property; these characters are replaced as a
single unit. By contrast, characters that have similar but distinct
Lisp objects as their @code{display} properties are handled
separately. Here's a function that illustrates this point:
Some kinds of @code{display} specifications specify something to
display instead of the text that has the property. If a list of
display specifications includes more than one of this kind, the first
is effective and the rest are ignored.
For these specifications, ``the text that has the property'' means
all the consecutive characters that have the same Lisp object as their
@code{display} property; these characters are replaced as a single
unit. By contrast, characters that have similar but distinct Lisp
objects as their @code{display} properties are handled separately.
Here's a function that illustrates this point:
@smallexample
(defun foo ()
...
...
@@ -3273,7 +3278,7 @@ results:
(goto-char (point-min))
(dotimes (i 5)
(let ((string (concat "A")))
(put-text-property (point) (
2
+ (point)) 'display string)
(put-text-property (point) (+
2
(point)) 'display string)
(put-text-property (point) (1+ (point)) 'display string)
(forward-char 2))))
@end smallexample
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment