From: Ihor Radchenko <yantar92@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
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 20:39:13 +0000 [thread overview]
Message-ID: <87v8jbc70u.fsf@localhost> (raw)
In-Reply-To: <834jqv3tv3.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> 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.
I see.
The real problem I am trying to solve is scrolling images with large
heights. C-n/C-p and default scrolling jumps over the whole images as
they appear on a single line. It is annoying, especially when the image
is taller than the window height.
I was hoping to use `insert-sliced-image', but this `line-spacing' issue
makes the idea unreliable.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-03-08 20:39 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
2023-03-08 20:39 ` Ihor Radchenko [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8jbc70u.fsf@localhost \
--to=yantar92@posteo.net \
--cc=62048@debbugs.gnu.org \
--cc=eliz@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.