From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: matthewktromp@gmail.com, 67470@debbugs.gnu.org
Subject: bug#67470: 29.1; move-end-of-line behaves badly with eglot type annotations
Date: Mon, 27 Nov 2023 13:38:56 +0000 [thread overview]
Message-ID: <CALDnm52cGyO3knk6Jyqh8dJVsNyid1fPm9P2sYDXuvGcuN2Pcw@mail.gmail.com> (raw)
In-Reply-To: <83v89n8he0.fsf@gnu.org>
On Mon, Nov 27, 2023 at 1:18 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: João Távora <joaotavora@gmail.com>
> > Date: Mon, 27 Nov 2023 13:02:36 +0000
> > Cc: matthewktromp@gmail.com, 67470@debbugs.gnu.org
> >
> > I have reproduced this. I can even add the following curious example
> >
> > some code aaaaaaaaaa
> > here are|some more lines which do not have annotations
> >
> > Press C-p, get
> >
> >
> > some cod| aaaaaaaaaa
> > here are some more lines which do not have annotations
> >
> > Which looks like just what you would get if you had pressed C-e
> > in the first line. Now type C-n.
> >
> > some code aaaaaaaaaa
> > here are|some more lines which do not have annotations
> >
> > Which is exactly what you expect. So, the manner in which
> > one arrives at the end of the line matters.
> >
> > > João, how are those annotations shown?
> >
> > With 'before-string' and 'after-string' properties, as you
> > guessed.
>
> I'd appreciate an example I could play with that doesn't need Eglot.
> I'm not sure we can fix this, but I'd like to understand better what
> gets in the way before I decide.
>
> Thanks.
You can try in the scratch buffer with your own overlay at the
end of the line with a before-string property that has the 'cursor'
property set to 1 at the first character.
João
next prev parent reply other threads:[~2023-11-27 13:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-26 23:37 bug#67470: 29.1; move-end-of-line behaves badly with eglot type annotations matthewktromp
2023-11-27 12:34 ` Eli Zaretskii
2023-11-27 13:02 ` João Távora
2023-11-27 13:17 ` Eli Zaretskii
2023-11-27 13:38 ` João Távora [this message]
2023-11-27 13:42 ` João Távora
2023-11-27 14:03 ` 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=CALDnm52cGyO3knk6Jyqh8dJVsNyid1fPm9P2sYDXuvGcuN2Pcw@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=67470@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=matthewktromp@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.
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.