GNU bug report logs - #72597
30.0.60; Eglot: MarkedString with embedded Carriage Return

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Troy Brown <brownts <at> troybrown.dev>
Cc: 72597 <at> debbugs.gnu.org, felician.nemeth <at> gmail.com, joaotavora <at> gmail.com
Subject: bug#72597: 30.0.60; Eglot: MarkedString with embedded Carriage Return
Date: Wed, 14 Aug 2024 07:37:01 +0300

> From: Troy Brown <brownts <at> troybrown.dev>
> Date: Tue, 13 Aug 2024 17:35:57 -0400
> Cc: Felician Nemeth <felician.nemeth <at> gmail.com>, Eli Zaretskii <eliz <at> gnu.org>, 72597 <at> debbugs.gnu.org
> 
> On Tue, Aug 13, 2024 at 2:45 PM João Távora <joaotavora <at> gmail.com> wrote:
> >
> > On Tue, Aug 13, 2024 at 7:32 PM Felician Nemeth
> > <felician.nemeth <at> gmail.com> wrote:
> >
> > > The way I understand it, Eglot calls gfm-view-mode to format this text.
> > > So even if the observed behavior is not in line with the LSP
> > > specification, it is the fault of gfm-view-mode and not directly
> > > Eglot's.
> > >
> > > gfm-view-mode is part of the markdown-mode package, which is NonGNU
> > > ELPA.
> >
> > Very correct.  Worth noting, though, that markdown-mode is an _optional_
> > dependency of Eglot. It doesn't need it (but it will use it if it finds it).
> >
> 
> I don't think it's gfm-view-mode's fault.  I can get the same
> problematic behavior with MarkupContent of "plaintext" (which uses
> text-mode), as follows:
> 
> (eglot--format-markup '(:value "foo\rbar" :kind "plaintext"))

Can you please answer my question whether this is standard-complying
behavior according to LSP protocol?  IOW, what is the source of the
assumption that CR characters will be interpreted as newlines in these
cases?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.