all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stephen Berman via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 73863@debbugs.gnu.org
Cc: eliz@gnu.org, romain.ouabdelkader@gmail.com
Subject: bug#73863: 30.0.91; Unexpected cursor movement with flymake-show-diagnostics-at-end-of-line
Date: Fri, 18 Oct 2024 21:25:51 +0200	[thread overview]
Message-ID: <87plnx8b7k.fsf@gmx.net> (raw)
In-Reply-To: <87ttd98bmr.fsf@gmx.net> (Stephen Berman via's message of "Fri, 18 Oct 2024 21:16:44 +0200")

On Fri, 18 Oct 2024 21:16:44 +0200 Stephen Berman via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org> wrote:

> On Fri, 18 Oct 2024 21:31:58 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>
>>> From: Romain Ouabdelkader <romain.ouabdelkader@gmail.com>
>>> Date: Fri, 18 Oct 2024 18:24:31 +0200
>>> Cc: 73863@debbugs.gnu.org
>>>
>>> I can reproduce using pyright, starting with emacs -Q:
>>
>> Thanks, but could you possibly reproduce without any additional
>> external packages, such as pyright?
>
> I can reproduce the problem using the pylsp server (I don't have pyright
> installed).  If this is a problem that occurs only with eglot when
> flymake displays diagnostics at the end of the line, is it even possible
> to avoid using an external LSP server (since IIUC managing such a server
> is what eglot is for and AFAIK no LSP servers are part of Emacs)?

Romain's latest followup, which I saw after posting my followup, answers
the question: eglot is not necessary, just flymake; I can also reproduce
the issue with his emacs-lisp-mode recipe.

Steve Berman





      reply	other threads:[~2024-10-18 19:25 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18 15:09 bug#73863: 30.0.91; Unexpected cursor movement with flymake-show-diagnostics-at-end-of-line Romain Ouabdelkader
2024-10-18 16:08 ` Eli Zaretskii
2024-10-18 16:24   ` Romain Ouabdelkader
2024-10-18 18:31     ` Eli Zaretskii
2024-10-18 19:10       ` Romain Ouabdelkader
2024-10-19 13:15         ` Eli Zaretskii
2024-10-19 13:41           ` Romain Ouabdelkader
2024-10-20  7:25             ` Eli Zaretskii
2024-10-20  9:28               ` João Távora
2024-10-20 11:22                 ` Eli Zaretskii
2024-10-20 11:38                   ` João Távora
2024-10-20 11:49                     ` Eli Zaretskii
2024-10-20 14:42                       ` João Távora
2024-10-20 15:01                         ` Romain Ouabdelkader
2024-10-20 15:49                           ` Eli Zaretskii
2024-10-20 16:23                             ` Eli Zaretskii
2024-10-20 15:31                         ` Eli Zaretskii
2024-10-20 15:39                           ` João Távora
2024-10-20 16:30                             ` Eli Zaretskii
2024-10-20 16:58                               ` João Távora
2024-10-20 17:50                                 ` Eli Zaretskii
2024-10-20 18:05                                   ` João Távora
2024-10-20 18:28                                     ` Eli Zaretskii
2024-10-20 19:18                                       ` João Távora
2024-10-27 10:56                   ` Eli Zaretskii
2024-10-30 23:57                     ` Romain Ouabdelkader
2024-10-18 19:16       ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-18 19:25         ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87plnx8b7k.fsf@gmx.net \
    --to=bug-gnu-emacs@gnu.org \
    --cc=73863@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=romain.ouabdelkader@gmail.com \
    --cc=stephen.berman@gmx.net \
    /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.