From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65990-done@debbugs.gnu.org, awrhygty@outlook.com
Subject: bug#65990: 29.1; show-paren-mode should not highlight line-prefix area
Date: Fri, 22 Dec 2023 06:52:45 -0800 [thread overview]
Message-ID: <CADwFkmmugKrmFVQn-MTNKeCE_coKkkycUgdMMsnF9sm=6qt73w@mail.gmail.com> (raw)
In-Reply-To: <83r0myihlr.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 16 Sep 2023 12:37:36 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: awrhygty@outlook.com
>> Date: Fri, 15 Sep 2023 18:26:12 +0900
>>
>>
>> Evaluate the form below,
>> the blank area on the left of the open parensis is highlighted,
>> while the blank area on the left of the close parensis is not.
>> Then type 'C-l C-l' to make the close parensis placed at the window
>> start, the area on the left of the close parensis is highlighted.
>>
>> (let ((buf (generate-new-buffer "*temp*")))
>> (switch-to-buffer buf)
>> (insert (propertize "(x\n)" 'line-prefix '(space :width 8))))
>
> Normally, none of the line-prefix should be highlighted. And that is
> what happens when the show-paren face is anywhere but at the first
> visible character in the window. When the face _is_ on the first
> visible character in the window, it is not clear whether the face
> should be considered as starting before the window or not; the current
> display code considers it to start before the window-start.
>
> I tend to close this bug as wontfix, since it seems to happen in rare
> situations, and fixing it will likely be messy. If you can show that
> it happens in more than just these rare cases, or if you have any
> suggestions for how to fix that or even can just point to the code
> which causes this, I might change my mind.
>
> Thanks.
No further comments within 3 months, so I'm closing this bug.
prev parent reply other threads:[~2023-12-22 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 9:26 bug#65990: 29.1; show-paren-mode should not highlight line-prefix area awrhygty
2023-09-16 9:37 ` Eli Zaretskii
2023-12-22 14:52 ` Stefan Kangas [this message]
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='CADwFkmmugKrmFVQn-MTNKeCE_coKkkycUgdMMsnF9sm=6qt73w@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=65990-done@debbugs.gnu.org \
--cc=awrhygty@outlook.com \
--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.