unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: pent <pent@aparamon.msk.ru>, 2749@debbugs.gnu.org
Subject: bug#2749: 23.0.91; Visual Line Mode: incorrect line wrapping in corner case
Date: Mon, 18 Feb 2013 13:03:12 +0100	[thread overview]
Message-ID: <87obfhhn9d.fsf@rosalinde.fritz.box> (raw)
In-Reply-To: <E1LlT79-0005aK-Jv@neo.paramonovs>

On Tue, 24 Mar 2009 21:35:02 -0400 Stefan Monnier <monnier@iro.umontreal.ca> wrote:

>> This behavior is expected.  The word wrap algorithm treats lines that
>> are too long to wrap using the ordinary line-wrapping rules, and since
>> overflow-newline-into-fringe is disabled in Visual Line mode, the extra
>> empty line is used to show the non-overflowed newline character.
>
>> After the release, I might look into letting word wrap handle
>> overflow-newline-into-fringe behavior.  I suspect, however, that this
>> may lead to confusing results in some circumstances.
>
> BTW: why is overflow-newline-into-fringe ignored when word-wrap is
> non-nil?  What kind of confusing results are you thinking of?

I would like to use a string of length window-width in a display overlay
together with word-wrap and a non-nil wrap-prefix.  Currently this
results in a following empty line with indentation, which is rather
disconcerting.  But after removing `&& (IT)->line_wrap != WORD_WRAP'
from the definition of IT_OVERFLOW_NEWLINE_INTO_FRINGE and rebuilding
Emacs, the empty indented line is gone and I have just what I want.  I
haven't yet seen anything confusing.  So I too would be very interested
to know if there are known or suspected problems with allowing non-nil
overflow-newline-into-fringe with word-wrap.  If it's not clear there
are any, could we allow it and then see if anyone screams bloody murder?

Steve Berman





  reply	other threads:[~2013-02-18 12:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24 18:04 bug#2749: 23.0.91; Visual Line Mode: incorrect line wrapping in corner case Chong Yidong
2009-03-25  1:35 ` Stefan Monnier
2009-03-22 19:13   ` pent
2013-02-18 12:03     ` Stephen Berman [this message]
2013-05-10 14:01       ` Stephen Berman
2013-05-10 14:59         ` Eli Zaretskii
2013-05-10 15:49           ` Stephen Berman
2013-05-10 17:37             ` Eli Zaretskii
2013-05-10 19:06               ` Stephen Berman
2013-05-10 19:31                 ` Eli Zaretskii
2013-05-18 20:30                   ` Stephen Berman
2013-05-19 15:29                     ` Eli Zaretskii
2013-05-19 16:28                       ` Stephen Berman
2013-05-19 17:38                         ` Eli Zaretskii
2013-05-28 22:26                     ` Stefan Monnier
2013-07-02 15:54                       ` Eli Zaretskii
2013-07-03  9:15                         ` Stefan Monnier
2013-07-03  9:52                         ` Stephen Berman

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=87obfhhn9d.fsf@rosalinde.fritz.box \
    --to=stephen.berman@gmx.net \
    --cc=2749@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=pent@aparamon.msk.ru \
    /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).