From: Platon Pronko <platon7pronko@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs@gnu.org
Subject: Re: Moving point around empty overlays with 'after-text
Date: Mon, 10 Apr 2023 13:26:13 +0800 [thread overview]
Message-ID: <933824d7-e9b6-fc17-3f67-87ad94bbebd1@gmail.com> (raw)
In-Reply-To: <83mt3gl49z.fsf@gnu.org>
On 2023-04-10 13:01, Eli Zaretskii wrote:
>> But inlay hints seem to be a common functionality for any modern IDE nowdays, so it might make sense to support them natively, without making major-mode developers resort >> to horrible hacks like described before.
> Well, maybe "someone" should reconsider whether using overlays for
> that is a good idea, then?
I agree, using overlays as they are currently implemented is definitely not optimal. Are there some better alternatives?
> Why not help-echo, for example?
This will show the help only for the current symbol, while the way inline hints are used is to show annotations for many symbols on the screen (for example, you have 20 different variable definitions, and IDE shows you inline type hints for each of them).
prev parent reply other threads:[~2023-04-10 5:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-08 5:46 Moving point around empty overlays with 'after-text Ash
2023-04-08 10:06 ` Eli Zaretskii
2023-04-08 10:14 ` Platon Pronko
2023-04-08 10:10 ` Platon Pronko
2023-04-08 23:06 ` Ash
2023-04-09 12:15 ` Platon Pronko
2023-04-09 14:49 ` tomas
2023-04-10 1:52 ` Platon Pronko
2023-04-10 4:56 ` Eli Zaretskii
2023-04-10 5:22 ` Platon Pronko
2023-04-10 9:56 ` Yuri Khan
2023-04-11 8:49 ` Platon Pronko
2023-04-11 9:41 ` Yuri Khan
2023-04-10 5:35 ` tomas
2023-04-10 5:48 ` Platon Pronko
2023-04-09 20:44 ` Ash
2023-04-10 2:00 ` Platon Pronko
2023-04-10 3:21 ` Ash
2023-04-10 3:31 ` Platon Pronko
2023-04-11 0:22 ` Ash
2023-04-10 5:09 ` Eli Zaretskii
2023-04-10 5:37 ` Platon Pronko
2023-04-10 8:03 ` Eli Zaretskii
2023-04-10 9:05 ` Platon Pronko
2023-04-10 5:01 ` Eli Zaretskii
2023-04-10 5:26 ` Platon Pronko [this message]
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=933824d7-e9b6-fc17-3f67-87ad94bbebd1@gmail.com \
--to=platon7pronko@gmail.com \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).