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 21:50:40 +0200 [thread overview]
Message-ID: <834jqv3tv3.fsf@gnu.org> (raw)
In-Reply-To: <87y1o7cd6a.fsf@localhost> (message from Ihor Radchenko on Wed, 08 Mar 2023 18:26:21 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: 62048@debbugs.gnu.org
> Date: Wed, 08 Mar 2023 18:26:21 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I've updated the manual to be more accurate about this. But other
> > than that, this is not a bug in the code.
>
> Thanks!
>
> I agree that the current newline 'line-height property behaviour makes sense.
> However, I still see `insert-sliced-image' inserting image with gaps as
> a bug. Would it be possible to change `insert-sliced-image' so that it
> overrides buffer-local `line-spacing' and forces no gaps?
Not easily, because the fact that the line-spacing variable affects
_all_ lines is deeply entrenched in the implementation: it computes
the corresponding metrics once and never changes that through the
entire redisplay of the window.
next prev parent reply other threads:[~2023-03-08 19:50 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
2023-03-08 18:26 ` Ihor Radchenko
2023-03-08 19:50 ` Eli Zaretskii [this message]
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=834jqv3tv3.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).