From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>,
Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 23574@debbugs.gnu.org, john.b.mastro@gmail.com, cwoodbury@azavea.com
Subject: bug#23574: 24.5; Overzealous underlining in emacs-nox
Date: Mon, 06 Jun 2016 18:54:38 +0200 [thread overview]
Message-ID: <5755AACE.8030303@gmx.at> (raw)
In-Reply-To: <83h9d6tl3j.fsf@gnu.org>
> Going back to the bug report, there's still one issue to consider:
> should we add underline (and then also overline and strikethrough) to
> the list of face attributes that cause face extension on GUI frames.
> The logic behind the current code seems to be to extend attributes
> that are related to background of the text. The above 3 seem to be a
> kind-of background, so maybe we should add them.
It would make my life much easier if face extension were, in general,
customizable. I would immediately turn it off everywhere.
My motivation is that I have font-lock distinguish things like comments
and strings mainly by their background face. Since these look awful
when extending to the end of a window, I have to provide my own
‘font-lock-fontify-syntactically-region’ function which assures that
newline characters within strings and comments never get the
corresponding face. This consumes resources and, for example, disallows
using text properties to skip the rest of a comment or a string. It
goes without saying, that my version of this function is never in synch
with the one of the repository.
I also use separate background colors for editable fields, buttons,
links and the like which also look awful when spanning two or more
lines. No font-locking can help me here.
martin
next prev parent reply other threads:[~2016-06-06 16:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 17:03 bug#23574: 24.5; Overzealous underlining in emacs-nox Colin Woodbury
2016-05-30 15:04 ` Colin Woodbury
2016-06-04 7:48 ` Eli Zaretskii
[not found] ` <CAHuwsfihHJ8WHwmHvMDF7Ynns4YOJSKEEbjhpbYrw0V=5aYXEQ@mail.gmail.com>
2016-06-04 16:20 ` Eli Zaretskii
2016-06-04 21:37 ` John Mastro
2016-06-05 15:54 ` Eli Zaretskii
2016-06-05 17:05 ` Noam Postavsky
2016-06-05 17:56 ` Eli Zaretskii
2016-06-05 18:20 ` Colin Woodbury
2016-06-05 18:36 ` Eli Zaretskii
2016-06-05 19:13 ` Noam Postavsky
2016-06-06 2:27 ` Eli Zaretskii
2016-06-06 11:42 ` Noam Postavsky
2016-06-06 15:04 ` Eli Zaretskii
2016-06-06 16:54 ` martin rudalics [this message]
2016-06-06 18:25 ` Colin Woodbury
2016-06-06 19:18 ` Eli Zaretskii
2016-06-07 0:18 ` Noam Postavsky
2016-06-07 15:55 ` Eli Zaretskii
2016-06-08 2:52 ` Noam Postavsky
2016-06-06 18:55 ` Eli Zaretskii
2016-06-07 9:10 ` martin rudalics
2016-06-07 15:50 ` Eli Zaretskii
2016-06-08 6:33 ` martin rudalics
2016-06-08 17:05 ` Eli Zaretskii
2016-06-09 8:38 ` martin rudalics
2016-06-09 12:26 ` Eli Zaretskii
2016-06-10 7:16 ` martin rudalics
2016-06-10 8:10 ` Eli Zaretskii
2016-06-10 8:24 ` martin rudalics
2016-06-10 9:50 ` Eli Zaretskii
2016-06-10 13:59 ` martin rudalics
2016-06-10 14:24 ` Eli Zaretskii
2019-10-21 11:49 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-08 5:32 ` 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=5755AACE.8030303@gmx.at \
--to=rudalics@gmx.at \
--cc=23574@debbugs.gnu.org \
--cc=cwoodbury@azavea.com \
--cc=eliz@gnu.org \
--cc=john.b.mastro@gmail.com \
--cc=npostavs@users.sourceforge.net \
/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).