From: Jim Porter <jporterbugs@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: 71605@debbugs.gnu.org
Subject: bug#71605: 30.0.50; [PATCH] Support variable-width text in 'visual-wrap-prefix-mode'
Date: Mon, 17 Jun 2024 11:17:45 -0700 [thread overview]
Message-ID: <4e596683-665e-8e2c-c201-9ddcb476d195@gmail.com> (raw)
In-Reply-To: <835c7897-d276-b0fe-6d1e-8e6a20cac2bb@gmail.com>
On 6/17/2024 9:13 AM, Jim Porter wrote:
> Note that I haven't removed any of the old logic though; it's all there
> as before, since the space characters are useful for terminals (where
> the pixelwise :width display-spec doesn't do anything for us, if I
> understand correctly).
Evidently I wasn't understanding this correctly, since further testing
and consulting the code shows that the :width display-spec works just
fine on terminals. It does make it harder to get this patch working well
though...
Maybe :align-to could be made to work. It doesn't seem to work at all
for me, even in a minimal test case like calling this on a long line of
text:
(put-text-property (point-min) (point-max) 'wrap-prefix '(space
:align-to 4))
Replacing :align-to with :width works just fine though. It's entirely
possible I'm just doing something wrong, but maybe this is a bug?
(Now what would be great is if :align-to supported a *string* value that
meant "use the pixel-width of this string". Which actually gives me an
idea... what if the wrap-prefix is just the original text like "* " and
we fontify it to be invisible? It's not part of the buffer and you can't
select it anyway, so it doesn't really matter what the text is so long
as it's not visible.)
next prev parent reply other threads:[~2024-06-17 18:17 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
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 [this message]
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=4e596683-665e-8e2c-c201-9ddcb476d195@gmail.com \
--to=jporterbugs@gmail.com \
--cc=71605@debbugs.gnu.org \
--cc=luangruo@yahoo.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 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.