unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 'Lars Magne Ingebrigtsen' <larsi@gnus.org>, 4710@debbugs.gnu.org
Subject: bug#4710: 23.1.50; Bad display of underlines crossing line boundaries
Date: Tue, 20 Sep 2011 07:05:06 -0700	[thread overview]
Message-ID: <67910CA13BCC481CB3F0E99477C8AC97@us.oracle.com> (raw)
In-Reply-To: <jwv62kohruo.fsf-monnier+emacs@gnu.org>

> > Not doing so could give the impression that there is 
> > actually a break (change) in the face attributes when
> > there is not.  If you do that, then perhaps some additional
> > display artifact should convey that -
> > e.g., perhaps a different fringe marker.
> 
> Again, you seem to be confused: I'm specifically talking about "face
> continuations", i.e. ways to express the fact that the face continues
> rather than being broken.  That's the whole point of the two ? in
> my example.  Please make sure there's an actual disagreement before
> jumping on your keyboard ;-)

Great, so you jumped on your keyboard to express your violent agreement. ;-)

At any rate, it looks like your and my proposals for such a
line-wrapping-without-breaking case, while perhaps interesting, do not
correspond to the bug reported.

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.






  reply	other threads:[~2011-09-20 14:05 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 [this message]
2016-07-14  4:15                       ` Andrew Hyatt
2016-07-14 11:45                         ` Noam Postavsky
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=67910CA13BCC481CB3F0E99477C8AC97@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=4710@debbugs.gnu.org \
    --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).