unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 46814@debbugs.gnu.org, "Miguel V. S. Frasson" <mvsfrasson@gmail.com>
Subject: bug#46814: 26.3; Visual-line-mode produces fake newline if line begins with space
Date: Sat, 27 Feb 2021 23:14:40 +0100	[thread overview]
Message-ID: <87wnutdupb.fsf@gmail.com> (raw)
In-Reply-To: <835z2dnzba.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 27 Feb 2021 20:24:57 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: "Miguel V. S. Frasson" <mvsfrasson@gmail.com>
>> Date: Sat, 27 Feb 2021 13:30:23 -0300
>> 
>> In visual-line-mode, if after leading whitespace it follows very long
>> text without spaces, it occurs a visual line break after the leading
>> whitespace, creating an false blank line, annoying users because extra
>> blank lines may change the meaning of text.
>> 
>> It would be more sensible in visual-line-mode forbids visual line breaks
>> after leading whitespace, because they always create blank lines.
>
> Patches are welcome to implement this.  Word of warning: the current
> implementation of this is in C, as part of the display engine, and
> it's very complex.

Should this be merged with bug#11759 and bug#31666?  Skimming [1], I get
the impression that this new report describes a similar problem, i.e.
visual-line-mode refusing to break a word preceded by whitespace.
Quoting Clément :

>                If breaking before a word doesn't prevent that word
> from being broken, it would seem better to not break before it.  In
> other words, assuming 9 columns:
>
> Here breaking at ' ' is useful:
> 
>   Input:
>   123456789
>   xxx aaaaaaa
> 
>   Visual-line mode (good)
>   123456789
>   xxx
>   aaaaaaa
> 
> But not here:
> 
>   Input
>   123456789
>   xxx aaaaaaaaaaaaa
> 
>   Visual-line mode (bad):
>   123456789
>   xxx
>   aaaaaaaaa
>   aaaa
> 
>   What I'd expect:
>   123456789
>   xxx aaaaa
>   aaaaaaaa

Apologies if I've missed some subtleties.


[1] bug#31666#11
    <99baa6b2-584f-789f-ecf8-d845aedd18ef@live.com>
    https://lists.gnu.org/archive/html/bug-gnu-emacs/2018-05/msg00894.html





  reply	other threads:[~2021-02-27 22:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-27 16:30 bug#46814: 26.3; Visual-line-mode produces fake newline if line begins with space Miguel V. S. Frasson
2021-02-27 18:24 ` Eli Zaretskii
2021-02-27 22:14   ` Kévin Le Gouguec [this message]
2021-02-28 17:39     ` Eli Zaretskii

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=87wnutdupb.fsf@gmail.com \
    --to=kevin.legouguec@gmail.com \
    --cc=46814@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=mvsfrasson@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).