From: D <d.williams@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: prettify-symbols-mode, derived modes, and compose-region
Date: Fri, 5 Mar 2021 01:22:30 +0100 [thread overview]
Message-ID: <587ee071-985b-450a-2df7-0b4bb0f97b48@posteo.net> (raw)
In-Reply-To: <83k0qmzit9.fsf@gnu.org>
> I'm not sure I understand the problem, but can't you use :align-to in
> display properties to solve the alignment issues?
To provide a concrete example, consider the following (closed) issue:
https://github.com/integral-dw/org-superstar-mode/issues/9
The data structure org-superstar-todo-bullet-alist associates a todo
keyword with a character to be displayed. The image shows the alignment
problem. The compose-region solution to this is simply to compose each
character with a wide enough space, so the user simply has to use
"\N{EM SPACE}<character>" instead of ?<character> in the alist.
compose-region will then just superimpose the two and you get a "padded"
character. It is very much possible that :align-to could fix this as
well, judging from the documentation it does sound like it can reproduce
this feature easily. To see how well it works out I would likely have
to implement a display-based version first, though.
On a side note: Are there any quirks I should be aware of when
transitioning to the display property? I doubt there will be any
difference in terms of performance (contrast overlays, which my mode
can't afford use), but is there anything else I should be aware of? I'm
asking in case there have been efforts like mine in the past which I am
not aware of.
next prev parent reply other threads:[~2021-03-05 0:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 21:33 prettify-symbols-mode, derived modes, and compose-region D
2021-03-04 21:54 ` Eli Zaretskii
2021-03-05 0:22 ` D [this message]
2021-03-05 2:30 ` Stefan Monnier
2021-03-05 3:20 ` Stefan Kangas
2021-03-05 7:25 ` Eli Zaretskii
2021-03-05 7:18 ` Eli Zaretskii
2021-03-05 15:14 ` Stefan Monnier
2021-03-05 15:20 ` Eli Zaretskii
2021-03-05 15:51 ` Stefan Monnier
2021-03-05 15:57 ` Lars Ingebrigtsen
2021-03-05 7:08 ` Eli Zaretskii
2021-03-05 14:05 ` Clément Pit-Claudel
2021-03-05 21:24 ` D
2021-03-06 9:15 ` Eli Zaretskii
2021-03-06 10:43 ` D
2021-03-06 10:59 ` 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
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=587ee071-985b-450a-2df7-0b4bb0f97b48@posteo.net \
--to=d.williams@posteo.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 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).