From: bojohan+news@dd.chalmers.se (Johan Bockgård)
To: bug-gnu-emacs@gnu.org
Subject: Re: display property as display spec vector behavior unclear
Date: Wed, 19 Sep 2007 01:54:35 +0200 [thread overview]
Message-ID: <yoijfy1bil6s.fsf@gamma02.me.chalmers.se> (raw)
In-Reply-To: 86odfzfxne.fsf@macs.hw.ac.uk
Joe Wells <jbw@macs.hw.ac.uk> writes:
> The documentation in the Emacs Lisp manual on the display property
> states this:
>
> The value of the `display' property should be a display
> specification, or a list or vector containing several display
> specifications.
>
> Unfortunately, this is the only thing it states about the case where
> the display property is a list or vector of display specs.
> I searched for all occurrences of the words “list” and “vector” in
> that section of the manual and could not find more precise details.
>
> I would guess from the above description that if the display property
> were a vector of display specs, then all of the things specified to be
> displayed would be shown from left to right. However, it seems that
> only the first one is used, which seems strange.
A vector or list is used for combining properties (where is makes
sense), not laying things out in sequence.
This passage from the comment of handle_single_display_spec is
relevant:
DISPLAY_REPLACED_P non-zero means that we previously saw a
display specification which already replaced text display
with something else, for example an image; we ignore such
properties after the first one has been processed.
Properties that don't "replace text with something else" include
`height', `raise', `space-width'. These can be combined.
Image slices use `slice' together with `image'.
--
Johan Bockgård
prev parent reply other threads:[~2007-09-18 23:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 21:53 display property as display spec vector behavior unclear Joe Wells
2007-09-18 23:54 ` Johan Bockgård [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yoijfy1bil6s.fsf@gamma02.me.chalmers.se \
--to=bojohan+news@dd.chalmers.se \
--cc=bug-gnu-emacs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.