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: Fri, 8 Jun 2018 14:04:16 -0400 [thread overview]
Message-ID: <86045cc6-5fc8-76c0-3d18-d6e1852df401@live.com> (raw)
In-Reply-To: <8336y7gdpo.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 1477 bytes --]
On 2018-06-01 03:36, Eli Zaretskii wrote:
> What about this case:
>
> Input
> 123456789
> xxxxxxx aaaaaaaaaaaaa
>
> ? Would you rather see this:
>
> 123456789
> xxxxxxx
> aaaaaaaaa
> aaaa
>
> or this:
>
> 123456789
> xxxxxxx a
> aaaaaaaaa
> aaa
>
> ?
I think I'd be fine with both, with a preference for the second one, especially if it's cheaper to compute that way.
> See also the fundamental problem with what you'd like Emacs to do,
which I described in another message.
Yes, this is a good point, and I don't have a great idea to overcome it.
That does suggest a more restricted improvement, though. The specific case in which I notice this issue is org-mode:
**** http://...very-long-string...
- Item 1
- http://…very-long-string…
I never want a break after leading '*' characters or bullets, or at the beginning of a line. In other words, changing this (| is the left margin):
|asdasd http://
|*** xyz http://…
to this:
|asdasd
|http://…
|*** xyz
| http://…
is OK, but changing this:
| http://…
|*** http://…
to this:
|
|http://…
|***
| http://…
is confusing.
How hard would it be to introduce a no-break text property? Then I could wire org-mode to put no-break properties on leading spaces and on spaces following '*' markers and everything would be good.
Clément.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2018-06-08 18:04 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
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 [this message]
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=86045cc6-5fc8-76c0-3d18-d6e1852df401@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.