From: Felician Nemeth <felician.nemeth@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 72597@debbugs.gnu.org, Troy Brown <brownts@troybrown.dev>,
joaotavora@gmail.com
Subject: bug#72597: 30.0.60; Eglot: MarkedString with embedded Carriage Return
Date: Tue, 13 Aug 2024 20:32:04 +0200 [thread overview]
Message-ID: <87v804mfyz.fsf@betli.tmit.bme.hu> (raw)
In-Reply-To: <86h6bohdsd.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 13 Aug 2024 14:18:10 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Cc: João Távora <joaotavora@gmail.com>
>> From: Troy Brown <brownts@troybrown.dev>
>> Date: Mon, 12 Aug 2024 21:16:40 -0400
>>
>> With the LSP language server I'm using, it's possible the language
>> server will return a textDocument/hover response MarkedString
>> containing "\r" (i.e., carriage return) for the line terminator when
>> the content contains multiple lines. An example of a typical response
>> is as follows:
>>
>> [jsonrpc] e[19:19:44.606] <-- textDocument/hover[38]
>> {"jsonrpc":"2.0","id":38,"result":{"contents":[{"language":"gpr","value":"type
>> Library_Kinds is (\"relocatable\", \"static\",
>> \"static-pic\");\rLibrary_Kind : Library_Kinds :=
>> \"static\";"},"gtkada_shared.gpr:37:04"]}}
>
> Does this behavior comply to the LSP standards?
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.
next prev parent reply other threads:[~2024-08-13 18:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 1:16 bug#72597: 30.0.60; Eglot: MarkedString with embedded Carriage Return Troy Brown
2024-08-13 11:18 ` Eli Zaretskii
2024-08-13 18:32 ` Felician Nemeth [this message]
2024-08-13 18:45 ` João Távora
2024-08-13 21:35 ` Troy Brown
2024-08-14 4:37 ` Eli Zaretskii
2024-08-14 5:54 ` Felician Nemeth
2024-08-14 6:37 ` Eli Zaretskii
2024-08-14 11:41 ` Troy Brown
2024-08-31 7:55 ` Eli Zaretskii
2024-09-01 20:49 ` Troy Brown
2024-09-02 11:24 ` Eli Zaretskii
2024-09-02 12:31 ` João Távora
2024-09-05 21:32 ` Daniel Pettersson
2024-09-05 21:58 ` João Távora
2024-09-06 5:44 ` Eli Zaretskii
2024-09-06 16:00 ` Daniel Pettersson
2024-09-06 19:31 ` João Távora
2024-09-09 0:31 ` Troy Brown
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=87v804mfyz.fsf@betli.tmit.bme.hu \
--to=felician.nemeth@gmail.com \
--cc=72597@debbugs.gnu.org \
--cc=brownts@troybrown.dev \
--cc=eliz@gnu.org \
--cc=joaotavora@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).