From: Psionic K <psionik@positron.solutions>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Psionic K <psionik@positron.solutions>, help-gnu-emacs@gnu.org
Subject: Re: How to Display a Zero Height Line
Date: Thu, 12 Dec 2024 18:00:15 +0900 [thread overview]
Message-ID: <CADQMGATTpn4m73oM5O+Fx=8Yef=UJnQXUdzdEbBa1YW3nPTvAQ@mail.gmail.com> (raw)
In-Reply-To: <86cyhx1jpu.fsf@gnu.org>
> > The background of TODO extends vertically in a graphical client. I
> > want the space between the two lines. I do not want the background of
> > the TODO to extend to the previous line. Any and all intended
> > workarounds are acceptable. I am merely choosing an implementation of
> > an effect in Dslide and it doesn't matter how it works.
> I still don't understand, but did you try to use the :extend
> attribute?
Why would I be in such a rush to horizontally :extend that which must
be vertically truncated?
I have further inspected the possibility of using empty lines with
actual newlines in the buffer text. No combination of assigning the
current line, an extraneous line used to create space, and the newline
before the next heading, via overlays with line-height, face height,
and line-spacing of zero, appear to overcome the font locking
behavior.
Directly manipulating the font locking behavior is acceptable if there
is a precise means of targeting. I have in the past applied
properties independent of font locking and then read these via new
font locking rules. As an implementation I prefer to avoid it because
if org learns tree-sitter, my solution will break depending on the
font locking in use.
next prev parent reply other threads:[~2024-12-12 9:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 6:37 How to Display a Zero Height Line Psionic K
2024-12-12 6:47 ` Eli Zaretskii
2024-12-12 9:00 ` Psionic K [this message]
2024-12-12 9:23 ` Eli Zaretskii
2024-12-12 12:25 ` Psionic K
-- strict thread matches above, loose matches on Subject: below --
2024-12-04 5:08 Psionic K
2024-12-04 13:10 ` Eli Zaretskii
2024-12-01 1:04 Psionic K
2024-12-01 6:41 ` Eli Zaretskii
2024-12-03 13:30 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-11-30 3:02 Psionic K
2024-11-30 7:35 ` 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='CADQMGATTpn4m73oM5O+Fx=8Yef=UJnQXUdzdEbBa1YW3nPTvAQ@mail.gmail.com' \
--to=psionik@positron.solutions \
--cc=eliz@gnu.org \
--cc=help-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.
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).