unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Andrew Hyatt <ahyatt@gmail.com>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	4710@debbugs.gnu.org
Subject: bug#4710: 23.1.50; Bad display of underlines crossing line boundaries
Date: Thu, 14 Jul 2016 07:45:32 -0400	[thread overview]
Message-ID: <CAM-tV-_Jxs8LNGcicDraXLYt+HMn3jqSO8zZivtPi_8f03z=cg@mail.gmail.com> (raw)
In-Reply-To: <m260s8n9cj.fsf@Andrews-MacBook-Pro.local>

On Thu, Jul 14, 2016 at 12:15 AM, Andrew Hyatt <ahyatt@gmail.com> wrote:
>> It appears that the OP was indeed about face extension across (hard) line breaks
>> into indented text on the next line.
>>
>> That was what my original response was to: If it hurts, don't do it; and let's
>> not assume that whitespace should not show the face attributes of the adjacent
>> text just because it represents indentation.
>
> Now we are almost 5 years into the future, and this bug hasn't been
> updated.  Drew's response didn't get agreement or disagreement, so would
> anyone object if we considered this not a bug, as he suggests?
>
>
>

Hmm, seems somewhat related to
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23574 (that one is about
underline from the end of line to the edge of screen, this one is
about underline from beginning of next line). Perhaps the new
defcustom discussed there
(http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23574#67) should cover
this too?





  reply	other threads:[~2016-07-14 11:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-12 20:49 bug#4710: 23.1.50; Bad display of underlines crossing line boundaries Lennart Borgman
2011-09-18  8:53 ` Lars Magne Ingebrigtsen
2011-09-18  9:12   ` Deniz Dogan
2011-09-18  9:20     ` Lars Magne Ingebrigtsen
2011-09-18  9:42       ` Eli Zaretskii
2011-09-18  9:43         ` Lars Magne Ingebrigtsen
2011-09-19 20:03           ` Stefan Monnier
2011-09-19 21:20             ` Drew Adams
2011-09-20  1:38               ` Stefan Monnier
2011-09-20  2:21                 ` Drew Adams
2011-09-20  2:29                   ` Stefan Monnier
2011-09-20 14:05                     ` Drew Adams
2016-07-14  4:15                       ` Andrew Hyatt
2016-07-14 11:45                         ` Noam Postavsky [this message]
2016-07-14 15:15                           ` Eli Zaretskii
2016-07-14 15:10                         ` Eli Zaretskii
2011-09-20  9:41                 ` Lars Magne Ingebrigtsen
2011-09-20 14:04                   ` Drew Adams
2011-09-20 21:46                     ` Stefan Monnier
2011-09-21 18:36                       ` Lars Magne Ingebrigtsen
2011-09-21 20:27                         ` Lennart Borgman
2011-09-22  1:18                         ` Stefan Monnier

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-_Jxs8LNGcicDraXLYt+HMn3jqSO8zZivtPi_8f03z=cg@mail.gmail.com' \
    --to=npostavs@users.sourceforge.net \
    --cc=4710@debbugs.gnu.org \
    --cc=ahyatt@gmail.com \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    /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).