unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: LemonBreezes <look@strawberrytea.xyz>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>,
	"Eli Zaretskii" <eliz@gnu.org>
Cc: 65896@debbugs.gnu.org
Subject: bug#65896: 30.0.50; folding text with text properties prevents background from extending past the newline
Date: Tue, 12 Sep 2023 16:35:16 -0500	[thread overview]
Message-ID: <40b4f4d3-34ae-4631-bebd-eefcd034d87e@app.fastmail.com> (raw)
In-Reply-To: <87il8fm7x2.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2355 bytes --]

This might not sound too clever, but why don't we just make the extend
property be determined by the first character in the line rather than
the last character / newline character? 

On Tue, Sep 12, 2023, at 3:51 PM, Kévin Le Gouguec wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > tags 65896 wishlist
> > thanks
> 
> This seems related to bug#52587, maybe so much so that it might make
> sense to merge them?  IIUC, given this Org buffer…
> 
> --8<---------------cut here---------------start------------->8---
> * foo
> #+begin_stuff
> bar
> #+end_stuff
> * baz
> --8<---------------cut here---------------end--------------->8---
> 
> … and folding "* foo",
> 
> * bug#52587 is about "#+end_stuff"'s :extended background "bleeding
>   into" the header line,
> 
> * bug#65896 (this report) is about the header line's :extended
>   background getting "cut short" once folded.
> 
> AFAIU those are two aspects of the same problem people have with
> outlines: the effective :extended background comes from the last line of
> the folded content (because that's the newline that is actually
> displayed) whereas one might expect it to come from the header line (but
> it can't, because the header line's newline is invisible).
> 
> So I'd expect addressing one report will also address the other.
> 
> >> From: StrawberryTea <look@strawberrytea.xyz>
> >> Date: Tue, 12 Sep 2023 13:00:45 -0500
> >> 
> >> 
> >> Hi. This issue comes from Reddit,
> >> https://www.reddit.com/r/emacs/comments/v0i4js/extend_org_heading_background_face_past_the/.
> >> Basically, if I fold text using text properties, the heading background
> >> does not extend to the end of the window. To quote /u/yantar92: "This is
> >> because the trailing newline in the folded heading gets hidden. If the
> >> trailing newline is invisible, :extend t has no effect. It is Emacs
> >> limitation, AFAIK." It would be great if we could make the :extend
> >> property work with invisible text.
> >
> > It cannot.  Text properties of invisible text are ignored because the
> > display engine skips invisible text and doesn't consider it and its
> > properties at all.
> >
> > I'm not closing this bug in the hope that someone will have a clever
> > idea for how to work around this, or maybe (gasp!) even submits a
> > patch.
> 

[-- Attachment #2: Type: text/html, Size: 3558 bytes --]

  reply	other threads:[~2023-09-12 21:35 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12 18:00 bug#65896: 30.0.50; folding text with text properties prevents background from extending past the newline StrawberryTea
2023-09-12 18:51 ` Eli Zaretskii
2023-09-12 20:51   ` Kévin Le Gouguec
2023-09-12 21:35     ` LemonBreezes [this message]
2023-09-13 11:54       ` Eli Zaretskii
2023-09-20 12:50         ` Ihor Radchenko
2023-09-21 11:07           ` Eli Zaretskii
2023-09-22 10:12             ` Ihor Radchenko
2023-09-22 11:56               ` Eli Zaretskii
2023-09-22 12:00                 ` Ihor Radchenko
2023-09-22 12:48                   ` Eli Zaretskii
2023-09-23 10:51                     ` Ihor Radchenko
2023-09-23 11:11                       ` Eli Zaretskii
     [not found]                         ` <871qep2l2z.fsf@localhost>
2023-09-23 12:38                           ` Eli Zaretskii
2023-09-23 12:59                             ` Ihor Radchenko
2023-09-23 13:10                               ` Eli Zaretskii
2023-09-23 14:06                                 ` Ihor Radchenko
2023-09-23 18:33                                   ` StrawberryTea
2023-09-23 19:05                                     ` Eli Zaretskii
2023-09-23 19:05                                       ` StrawberryTea
2023-09-24  5:00                                         ` Eli Zaretskii
2023-09-24  7:53                                           ` StrawberryTea
2023-09-24 10:19                                             ` Ihor Radchenko
2023-09-24 11:59                                               ` Eli Zaretskii
2023-09-24 18:30                                                 ` StrawberryTea
2023-09-25  4:38                                                   ` Eli Zaretskii
2023-09-26  8:18                                                 ` Ihor Radchenko
2023-09-29  5:47                                                   ` Eli Zaretskii
2024-01-22 14:45                                                   ` Ihor Radchenko
2024-01-23 19:14                                                     ` Kévin Le Gouguec
2024-01-24 16:42                                                       ` Ihor Radchenko
2024-01-25  7:46                                                         ` Kévin Le Gouguec
2024-01-25 13:47                                                           ` Ihor Radchenko
2023-09-21 12:54           ` Eli Zaretskii
2023-09-21 21:07             ` Kévin Le Gouguec
2023-09-22  6:40               ` Juri Linkov
2023-09-22  7:20                 ` Eli Zaretskii
2023-09-29  7:12                 ` Kévin Le Gouguec
2023-09-29 15:41                   ` Juri Linkov
2023-09-29 19:07                     ` StrawberryTea
2023-09-30 13:49                       ` Eli Zaretskii
2023-09-30 22:55                         ` StrawberryTea
2023-10-01  8:42                           ` Eli Zaretskii
2023-10-02  4:28                             ` StrawberryTea
2023-10-02  6:05                               ` Eli Zaretskii
2023-10-05 20:59                                 ` StrawberryTea
2023-09-13 11:48     ` 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=40b4f4d3-34ae-4631-bebd-eefcd034d87e@app.fastmail.com \
    --to=look@strawberrytea.xyz \
    --cc=65896@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=kevin.legouguec@gmail.com \
    /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).