From: Stephen Berman <stephen.berman@gmx.net>
To: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
Cc: 39360@debbugs.gnu.org
Subject: bug#39360: Add :extend attribute to show-paren-mode expression face
Date: Fri, 31 Jan 2020 17:03:41 +0100 [thread overview]
Message-ID: <87pnezehpe.fsf@gmx.net> (raw)
In-Reply-To: <a69304fb-c650-f0fe-aeba-749f26867d6a@gmail.com> ("Clément Pit-Claudel"'s message of "Fri, 31 Jan 2020 09:52:25 -0500")
[-- Attachment #1: Type: text/plain, Size: 974 bytes --]
On Fri, 31 Jan 2020 09:52:25 -0500 Clément Pit-Claudel <cpitclaudel@gmail.com> wrote:
> On 2020-01-31 02:38, Eli Zaretskii wrote:
>>> From: Clément Pit-Claudel <cpitclaudel@gmail.com>
>>> Date: Thu, 30 Jan 2020 16:08:50 -0500
[...]
>>> I might have missed discussions about this; is there a reason why :extend t
>>> isn't the default?
>>
>> Because the whole idea of introducing :extend was that almost all
>> faces don't need this attribute.
>
> I see. The new default looks weird to me, but I'm sure I'll get used to it.
What also looks weird and infelicitous to me is that a nonextending
background color face on multiple lines shows up on the empty space at
the beginning of a line, i.e., it appears to extend into this space, see
attached screenshot. I think this only happens with white space
characters, not with lines indented e.g. with wrap-prefix. It would be
nice to treat all "empty" space the same in this respect.
Steve Berman
[-- Attachment #2: show-paren.png --]
[-- Type: image/png, Size: 22170 bytes --]
next prev parent reply other threads:[~2020-01-31 16:03 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
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 [this message]
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=87pnezehpe.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=39360@debbugs.gnu.org \
--cc=cpitclaudel@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).