unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: tomas@tuxteam.de
To: Platon Pronko <platon7pronko@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Moving point around empty overlays with 'after-text
Date: Mon, 10 Apr 2023 07:35:49 +0200	[thread overview]
Message-ID: <ZDOgNUd3EVWiKhiM@tuxteam.de> (raw)
In-Reply-To: <c927666a-a52e-c902-3525-cf82f5398fe6@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1537 bytes --]

On Mon, Apr 10, 2023 at 09:52:54AM +0800, Platon Pronko wrote:
> On 2023-04-09 22:49, tomas@tuxteam.de wrote:

[...]

> > What I don't understand is why the overlay doesn't cover the
> > whole argument value instead of sticking before it. Perhaps
> > this would ease some of the problems?
> > 
> > Cheers
> 
> Why should it?
> 
> (maybe there's a confusion because of the words - what is being used here is technically a zero-width overlay, so it's not "overlaying" anything, it's probably better to call it "inlay")

I did understand that it is a zero-width overlay, so the
description wasn't confusing to me.

> Anyway, even if you make this overlay to cover something it won't solve the problem - it still won't be possible to navigate the cursor to be before or after the hint.

For non-zero width overlays, it is quite easy to have
point to each side of the overlay's "border": it depends
on which side you are coming from. For me, at least, it
is intuitive.

Quite possibly I'm not understanding what you are trying
to achieve. The mental model I got from your description
is that the overlay describes some property of the arg
value in question (the name given to the corresponding
formal argument elsewhere in the function declaration
viz. definition). That's why I'd expect the overlay to
cover /all/ of the arg value (and let it grow and shrink
automatically as the latter is edited by the user).

But, as said, perhaps I'm lost in the woods.If yes, then
sorry for that :)

Cheers
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2023-04-10  5:35 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 [this message]
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

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=ZDOgNUd3EVWiKhiM@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=help-gnu-emacs@gnu.org \
    --cc=platon7pronko@gmail.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.
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).