From: Eli Zaretskii <eliz@gnu.org>
To: Colin Woodbury <cwoodbury@azavea.com>
Cc: 23574@debbugs.gnu.org, john.b.mastro@gmail.com,
npostavs@users.sourceforge.net
Subject: bug#23574: 24.5; Overzealous underlining in emacs-nox
Date: Sun, 05 Jun 2016 21:36:01 +0300 [thread overview]
Message-ID: <83shwrtre6.fsf@gnu.org> (raw)
In-Reply-To: <CAHuwsfhRt5i2J25Po8fcRsJSsw9uutfmvMF_Cus=Ej=aynHbZQ@mail.gmail.com> (message from Colin Woodbury on Sun, 5 Jun 2016 11:20:24 -0700)
> From: Colin Woodbury <cwoodbury@azavea.com>
> Date: Sun, 5 Jun 2016 11:20:24 -0700
> Cc: Noam Postavsky <npostavs@users.sourceforge.net>, john.b.mastro@gmail.com,
> 23574@debbugs.gnu.org
>
> Interesting that you consider the the GUI _not_ displaying the face all the way to end of screen to be a bug.
It's not a bug, it's the intended behavior. On GUI frames, the
display engine only makes sure to extend the face if it has one or
more of the following attributes:
. background color
. stipple
. box
> I think only displaying to the end of the characters (as shown in images in the Github issue) is the expected
> behaviour. Otherwise, the screen (at least with underlining) gets quite noisy.
Why would you have underlining span several lines if you don't want
that effect? (I admit I didn't really understand the original use
case which prompted this report.)
Anyway, you've just heard of another application which would like the
GUI frames behave like TTYs, not the other way around.
next prev parent reply other threads:[~2016-06-05 18:36 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 [this message]
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
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=83shwrtre6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23574@debbugs.gnu.org \
--cc=cwoodbury@azavea.com \
--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).