From: Jim Porter <jporterbugs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 71605@debbugs.gnu.org
Subject: bug#71605: 30.0.50; [PATCH] Support variable-width text in 'visual-wrap-prefix-mode'
Date: Thu, 20 Jun 2024 10:36:23 -0700 [thread overview]
Message-ID: <dc004bc2-6927-6c49-debc-486b6fe495ac@gmail.com> (raw)
In-Reply-To: <86a5jgndev.fsf@gnu.org>
On 6/20/2024 2:58 AM, Eli Zaretskii wrote:
> Should be fixed now on the master branch.
Thanks, it all seems to work now.
I think I have a way forward to implement this that should avoid issues,
though it's a bit more complex than I'd initially thought. I think there
are three cases:
"* here is some text":
Text Properties
"* " (display (min-width (2)))
"here is some text" (wrap-prefix (space :align-to 2))
" here is some text":
Text Properties
" " (display "")
" here is some text" (line-prefix (space :align-to 2)
wrap-prefix (space :align-to 2))
"// here is some text" (in c-mode):
Text Properties
"// here is some text" (wrap-prefix "// ")
(The last case is just doing what visual-wrap-prefix-mode currently
does.) I'm pretty sure all these should be unproblematic in the
scenarios Po Lu mentioned. The only case I haven't considered is how
this interacts with 'visual-wrap-extra-indent'. I'll have to think about
that some more.
next prev parent reply other threads:[~2024-06-20 17:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 2:56 bug#71605: 30.0.50; [PATCH] Support variable-width text in 'visual-wrap-prefix-mode' Jim Porter
2024-06-17 11:37 ` Eli Zaretskii
2024-06-17 17:42 ` Jim Porter
2024-06-17 18:20 ` Eli Zaretskii
2024-06-17 18:44 ` Jim Porter
2024-06-18 11:37 ` Eli Zaretskii
2024-06-18 22:17 ` Jim Porter
2024-06-19 11:45 ` Eli Zaretskii
2024-06-19 19:53 ` Jim Porter
2024-06-20 4:58 ` Eli Zaretskii
2024-06-20 5:37 ` Jim Porter
2024-06-20 9:58 ` Eli Zaretskii
2024-06-20 17:36 ` Jim Porter [this message]
2024-06-20 18:08 ` Eli Zaretskii
2024-06-20 19:01 ` Jim Porter
2024-07-28 4:53 ` Jim Porter
2024-08-02 7:27 ` Eli Zaretskii
2024-08-04 19:24 ` Jim Porter
2024-06-17 14:23 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-17 16:13 ` Jim Porter
2024-06-17 18:17 ` Jim Porter
2024-06-17 19:55 ` Eli Zaretskii
2024-06-17 20:08 ` Jim Porter
2024-06-18 3:02 ` Jim Porter
2024-06-18 6:27 ` Jim Porter
2024-06-18 12:53 ` Eli Zaretskii
2024-06-18 12: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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dc004bc2-6927-6c49-debc-486b6fe495ac@gmail.com \
--to=jporterbugs@gmail.com \
--cc=71605@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.