unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Psionic K <psionik@positron.solutions>
Cc: 68793@debbugs.gnu.org
Subject: bug#68793: 29.2; Visual line mode line spacing text property
Date: Mon, 29 Jan 2024 14:30:16 +0200	[thread overview]
Message-ID: <86il3c490n.fsf@gnu.org> (raw)
In-Reply-To: <CADQMGAT-p26goDq1MAR=PMQbBot6tah7oA9=dKKjjFJ5QzhUGg@mail.gmail.com> (message from Psionic K on Mon, 29 Jan 2024 15:23:33 +0900)

tags 68793 notabug
thanks

> From: Psionic K <psionik@positron.solutions>
> Date: Mon, 29 Jan 2024 15:23:33 +0900
> 
> In visual line mode, setting `line-spacing' and `line-height' text
> property on whole lines only correctly displays lines terminating in a
> newline
> 
> Steps to reproduce:
> 
> 1. open a buffer in fundamental mode
> 2. M-x visual line mode
> 3. Write a bunch of text with no newlines
> 4. Evaluate (add-text-properties (mark) (point) '(line-spacing 2.0))
> 5. Press RET somewhere in the paragraph or at the end
> 
> Observe that only the line that terminates in newline respects the
> property and that this does not respect user intent with
> visual-line-mode.

This is the documented behavior.  From the ELisp manual:

     Finally, a newline can have a ‘line-spacing’ text or overlay property
  that can enlarge the default frame line spacing and the buffer local
  ‘line-spacing’ variable: if its value is larger than the buffer or frame
  defaults, that larger value is used instead, for the display line ending
  in that newline                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  ^^^^^^^^^^^^^^^

Note the part I underlined.  Only the last display line
(a.k.a. "screen line") preceding the newline is affected.  The same
happens without visual-line-mode, btw: only the last continuation line
has the line-spacing applied to it.

This is not a bug, surprising as it might be.





  reply	other threads:[~2024-01-29 12:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29  6:23 bug#68793: 29.2; Visual line mode line spacing text property Psionic K
2024-01-29 12:30 ` Eli Zaretskii [this message]
2024-10-05  1:18   ` Stefan Kangas

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=86il3c490n.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=68793@debbugs.gnu.org \
    --cc=psionik@positron.solutions \
    /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).