From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, martin rudalics <rudalics@gmx.at>
Cc: 39360@debbugs.gnu.org
Subject: bug#39360: Add :extend attribute to show-paren-mode expression face
Date: Fri, 31 Jan 2020 11:12:37 -0500 [thread overview]
Message-ID: <c7cea50a-07e2-c304-b60c-a0f9e63466a7@gmail.com> (raw)
In-Reply-To: <831rrflixt.fsf@gnu.org>
On 2020-01-31 10:55, Eli Zaretskii wrote:
> What we have now is similar to how other
> programs behave, including highlighting of the space beyond EOL. Does
> it irritate you in those other programs as well?
On my machine at least, none of vim, nano, or thunderbird highlights the EOL space.
Firefox does highlight the end-of-line space on line wraps, but not when the newline is due to a paragraph change or an explicit <br /> in the source. LibreOffice and gedit highlight past the end of the line, stretching to the end of the window like Emacs does for the region.
If I highlight a region in LibreOffice using the highlighter tool to apply a background color, that color extends over one space to the right of the text when there's a line wrap (because the space over which the line is broken is before the break), but explicit newlines are not highlighted.
I couldn't find a program on my machine that behave like Emacs now does (highlighting explicit newlines).
Clément.
next prev parent reply other threads:[~2020-01-31 16:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 21:08 bug#39360: Add :extend attribute to show-paren-mode expression face Clément Pit-Claudel
2020-01-30 23:35 ` Dmitry Gutov
2020-01-31 7:38 ` Eli Zaretskii
2020-01-31 14:52 ` Clément Pit-Claudel
2020-01-31 15:32 ` Eli Zaretskii
2020-01-31 15:51 ` Clément Pit-Claudel
2020-01-31 17:03 ` Eli Zaretskii
2020-02-07 0:27 ` Dmitry Gutov
2020-02-07 0:40 ` Juri Linkov
2020-02-07 8:13 ` Eli Zaretskii
2020-02-07 8:02 ` Eli Zaretskii
2020-01-31 15:44 ` martin rudalics
2020-01-31 15:55 ` Eli Zaretskii
2020-01-31 16:12 ` Clément Pit-Claudel [this message]
2020-01-31 17:12 ` Eli Zaretskii
2020-01-31 17:19 ` Dmitry Gutov
2020-01-31 19:19 ` Eli Zaretskii
2020-01-31 17:22 ` Eli Zaretskii
2020-02-01 20:54 ` Clément Pit-Claudel
2020-01-31 16:45 ` martin rudalics
2020-01-31 16:03 ` Stephen Berman
2020-01-31 16:45 ` martin rudalics
2020-01-31 17:15 ` Eli Zaretskii
2020-01-31 17:07 ` Eli Zaretskii
2020-01-31 16:07 ` Stephen Berman
2020-09-20 10:01 ` Lars Ingebrigtsen
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=c7cea50a-07e2-c304-b60c-a0f9e63466a7@gmail.com \
--to=cpitclaudel@gmail.com \
--cc=39360@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rudalics@gmx.at \
/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).