From: "Clément Pit-Claudel" <clement.pitclaudel@live.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31666@debbugs.gnu.org
Subject: bug#31666: Bad interaction between visual-line-mode and wrap-prefix on long lines
Date: Thu, 31 May 2018 19:16:12 -0400 [thread overview]
Message-ID: <99baa6b2-584f-789f-ecf8-d845aedd18ef@live.com> (raw)
In-Reply-To: <83fu27hnko.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 1613 bytes --]
On 2018-05-31 11:06, Eli Zaretskii wrote:
> …
> I'm not sure I understand/agree that the above describes the same
> issue as your example. But let's deal with the example first:
> …
> I don't see why you shouldn't expect that. Visual Line mode breaks
> long lines on whitespace characters, and the 15 spaces with which you
> start each line provide ample opportunity for that.
That's a good point, the behavior that I dislike doesn't even require adaptive-wrap or a wrap-prefix property. Just having a few spaces at the beginning of a line and a very long word is enough.
> ...
> Are you saying that you expected this instead:
>
> xxxxxxxxxxxxxxx AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
> AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
>
> ? That would be Visual Line mode missing an opportunity to break a
> long line on whitespace characters, no?
Yes, I think that's correct. If I understand correctly, the purpose of visual-line-mode is to break between word to avoid having to break inside words. 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
Does this make sense?
Clément.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2018-05-31 23:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 12:27 bug#31666: Bad interaction between visual-line-mode and wrap-prefix on long lines Clément Pit-Claudel
2018-05-31 15:06 ` Eli Zaretskii
2018-05-31 23:16 ` Clément Pit-Claudel [this message]
2018-06-01 0:19 ` Noam Postavsky
2018-06-01 7:02 ` Stephen Berman
2018-06-01 7:32 ` Eli Zaretskii
2018-06-01 8:00 ` Stephen Berman
2018-06-01 8:44 ` Eli Zaretskii
2018-06-01 7:36 ` Eli Zaretskii
2018-06-08 18:04 ` Clément Pit-Claudel
2018-06-08 18:32 ` Eli Zaretskii
2018-06-08 19:24 ` Eli Zaretskii
2018-06-08 19:32 ` Clément Pit-Claudel
2018-06-08 21:19 ` Clément Pit-Claudel
2018-06-09 8:42 ` Eli Zaretskii
2018-06-09 12:45 ` Clément Pit-Claudel
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=99baa6b2-584f-789f-ecf8-d845aedd18ef@live.com \
--to=clement.pitclaudel@live.com \
--cc=31666@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.