unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23574@debbugs.gnu.org, Colin Woodbury <cwoodbury@azavea.com>,
	John Mastro <john.b.mastro@gmail.com>
Subject: bug#23574: 24.5; Overzealous underlining in emacs-nox
Date: Mon, 6 Jun 2016 20:18:06 -0400	[thread overview]
Message-ID: <CAM-tV-_uahaVxGnNJCoNYV1ACpcoBm7dors0VjNh8bESFbC=YQ@mail.gmail.com> (raw)
In-Reply-To: <83vb1mrura.fsf@gnu.org>

On Mon, Jun 6, 2016 at 3:18 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> And I don't think what you get is the desired effect, you just get a
> side effect of a particular implementation detail.  E.g., what happens
> if a line fits exactly on a line, i.e. the cursor at its end will be
> displayed on the fringe?

The underlining does reach the end of the screen in this case, but it
still looks okay because the underlining doesn't extend too far away
from the text.

>
>> In TTY this places the face over everything, which we don't agree is a bug or not.
>
> It isn't a bug, because that's how the display engine was coded to
> work.  Of course, we can make it behave differently if we want.

I think it makes sense to not do the face extension by default. If I
take a sheet of paper and underline lines 3 to 10, I'm going to stop
drawing at the end of the text, not go all the way to end of the
paper.

For the case I mentioned earlier, magit isn't actually underlining
text, it just wants to make some horizontal lines. It would be nice to
have some way to ask the display engine to do this directly.





  reply	other threads:[~2016-06-07  0:18 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
2016-06-06 18:25                           ` Colin Woodbury
2016-06-06 19:18                             ` Eli Zaretskii
2016-06-07  0:18                               ` Noam Postavsky [this message]
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='CAM-tV-_uahaVxGnNJCoNYV1ACpcoBm7dors0VjNh8bESFbC=YQ@mail.gmail.com' \
    --to=npostavs@users.sourceforge.net \
    --cc=23574@debbugs.gnu.org \
    --cc=cwoodbury@azavea.com \
    --cc=eliz@gnu.org \
    --cc=john.b.mastro@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).