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: Tue, 18 Jun 2024 15:17:29 -0700 [thread overview]
Message-ID: <a378b46a-e53a-d7b4-c3c0-e2db1022bc55@gmail.com> (raw)
In-Reply-To: <86h6dqqy63.fsf@gnu.org>
On 6/18/2024 4:37 AM, Eli Zaretskii wrote:
> I don't think I understand how would this do the job. Surely, the
> indentation space should be visible?
I mean the second-line "* " prefix would be visible but transparent.
>> A face transparency attribute might do the trick, and be useful for
>> other things too:
>
> It isn't universally supported, AFAIK.
I think it would be feasible to support an opacity level of 1.0 and 0.0.
opacity=0.0 could just allocate the space for the text but not actually
draw the glyphs. (Whether we want to go this route is another question.)
>> Or maybe :align-to could take a string value, which would mean "use the
>> pixel-width of this string as the value".
>
> How is that different from using a column (as opposed to pixel) value
> for :align-to?
A column wouldn't work, since for a variable-pitch font, N columns is
just N * <canonical character width>. If the actual characters you're
trying to align to are narrower than the canonical width, they won't
line up correctly.
Po Lu also raised the issue that in some cases, different frames can be
displaying the same buffer using different fonts. Conceptually, I'm
really trying to tell the display engine, "Put a space here exactly as
wide as <some text> using whatever font you end up using." At the buffer
level, I can't provide a numeric width here that works everywhere, since
it might really be multiple numbers, one for each frame.
Providing a number in pixels is also challenging because then I need to
be able to determine when to recompute that number.
>>>> If I set that correctly, then the pixel-size should adjust as the
>>>> text scales. It wouldn't handle the case where the actual font
>>>> changes though.
>>>
>>> Why not?
>>
>> I was planning to set :relative-width to <first_line_prefix_width> /
>> <width_of_one_space>. If the font changes, the result of that
>> calculation can change.
>
> The idea is to set it to the multiple of the character's width, which
> will then scale with the font.
Imagine two fonts A and B, where the only difference is that the space
character in B is twice as wide. So:
<asterisk_width> = 15
<space_width_A> = 10
<space_width_B> = 20
<first_line_prefix_width_A> = 15 + 10 = 25
<first_line_prefix_width_B> = 15 + 20 = 35
If I compute :relative-width for font A, the result is 25/10 = 2.5. Then,
2.5 * <space_width_A> = 25 = <first_line_prefix_width_A> (good)
2.5 * <space_width_B> = 50 != <first_line_prefix_width_B> (bad!)
So we'd need a way of keeping the width in-sync with any font changes.
next prev parent reply other threads:[~2024-06-18 22: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 [this message]
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
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=a378b46a-e53a-d7b4-c3c0-e2db1022bc55@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.