From: Eli Zaretskii <eliz@gnu.org>
To: "Clément Pit-Claudel" <clement.pitclaudel@live.com>
Cc: 31666@debbugs.gnu.org
Subject: bug#31666: Bad interaction between visual-line-mode and wrap-prefix on long lines
Date: Fri, 08 Jun 2018 21:32:03 +0300 [thread overview]
Message-ID: <83o9glt9i4.fsf@gnu.org> (raw)
In-Reply-To: <86045cc6-5fc8-76c0-3d18-d6e1852df401@live.com> (message from Clément Pit-Claudel on Fri, 8 Jun 2018 14:04:16 -0400)
> Cc: 31666@debbugs.gnu.org
> From: Clément Pit-Claudel <clement.pitclaudel@live.com>
> Date: Fri, 8 Jun 2018 14:04:16 -0400
>
> How hard would it be to introduce a no-break text property?
The problem is not in introduction of the property, the problem is in
implementing property look up where we decide whether to break a line
on a whitespace character. That look up might be costly, especially
if, as usual, we are required to support both text and overlay
properties.
next prev parent reply other threads:[~2018-06-08 18:32 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
2018-06-08 18:32 ` Eli Zaretskii [this message]
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
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=83o9glt9i4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31666@debbugs.gnu.org \
--cc=clement.pitclaudel@live.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).