From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: 62048@debbugs.gnu.org
Subject: bug#62048: 30.0.50; Non-nil `line-spacing' takes precendence over 'line-height t text property
Date: Wed, 08 Mar 2023 19:31:44 +0200 [thread overview]
Message-ID: <83a60n40an.fsf@gnu.org> (raw)
In-Reply-To: <87ilfbe8r0.fsf@localhost> (message from Ihor Radchenko on Wed, 08 Mar 2023 12:18:59 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Date: Wed, 08 Mar 2023 12:18:59 +0000
>
> According to 41.11 Line Height section of Elisp manual,
>
> A newline can have a ‘line-height’ text or overlay property that
> controls the total height of the display line ending in that newline.
> The property value can be one of several forms:
>
> ‘t’
> If the property value is ‘t’, the newline character has no effect
> on the displayed height of the line—the visible contents alone
> determine the height. The ‘line-spacing’ property, described
> below, is also ignored in this case. This is useful for tiling
> small images (or image slices) without adding blank areas between
> the images.
>
> AFAIU, it implies that buffer-local `line-spacing' value is also
> ignored.
>
> Consider the following minimal example:
>
> 1. emacs -Q
> 2. (setq-default line-spacing 0.15)
> 3. (with-silent-modifications (insert-sliced-image (create-image "/path/to/some/image") nil nil 10 nil))
>
> Expected: the spliced image is displayed without gaps.
> Observed: visible gaps between image rows
>
> If I understand correctly, `insert-sliced-image' tries to avoid the gaps
> by (insert (propertize "\n" 'line-height t)). But it does not seem to be
> working.
>
> Am I missing something?
The above text in the manual is misleading: only the line-spacing
property of the same newline is ignored in this case. (It makes no
sense to ignore the buffer-local value of line-spacing due to a single
newline, because the buffer-local value of line-spacing affects all
the lines in the buffer, not just one line.) IOW, the line-height
property of the newline overrides the 'line-spacing' property of the
same newline.
I've updated the manual to be more accurate about this. But other
than that, this is not a bug in the code.
next prev parent reply other threads:[~2023-03-08 17:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 12:18 bug#62048: 30.0.50; Non-nil `line-spacing' takes precendence over 'line-height t text property Ihor Radchenko
2023-03-08 17:31 ` Eli Zaretskii [this message]
2023-03-08 18:26 ` Ihor Radchenko
2023-03-08 19:50 ` Eli Zaretskii
2023-03-08 20:39 ` Ihor Radchenko
2023-03-09 6:54 ` Eli Zaretskii
2023-03-09 9:13 ` Ihor Radchenko
2023-03-09 9:47 ` Eli Zaretskii
2023-03-09 10:55 ` Ihor Radchenko
2023-03-09 12:16 ` Eli Zaretskii
2023-03-11 11:10 ` Ihor Radchenko
2023-03-11 12:28 ` Eli Zaretskii
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=83a60n40an.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62048@debbugs.gnu.org \
--cc=yantar92@posteo.net \
/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).