From: "João Távora" <joaotavora@gmail.com>
To: Daniel Pettersson <daniel@dpettersson.net>
Cc: 72597@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
Troy Brown <brownts@troybrown.dev>,
felician.nemeth@gmail.com
Subject: bug#72597: 30.0.60; Eglot: MarkedString with embedded Carriage Return
Date: Thu, 5 Sep 2024 22:58:01 +0100 [thread overview]
Message-ID: <CALDnm51M1es+ApV+FYEcxvgRZ_j7q67cGXFsqBNYnZqReqPQpw@mail.gmail.com> (raw)
In-Reply-To: <m2ikv9zt0n.fsf@dpettersson.net>
On Thu, Sep 5, 2024 at 10:32 PM Daniel Pettersson
<daniel@dpettersson.net> wrote:
> I might be missing something, but jsonrpc should not in my mind
> convert/format/encode any json data. Any assumptions on line endings
> can only be made on header and content separators, not on the json
> payload itself.
That's also a reasonable position, I guess. The line ending
convention is somewhat of a grey zone. jsonrpc.el produces
Elisp strings from JSON strings. It could apply Emasc's
line-ending conventions. Or maybe not, maybe you're right
and Eglot the jsonrpc.el client should do it. Or really this
quirky server should just use \n like everyone else.
João
next prev parent reply other threads:[~2024-09-05 21:58 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
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 [this message]
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=CALDnm51M1es+ApV+FYEcxvgRZ_j7q67cGXFsqBNYnZqReqPQpw@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=72597@debbugs.gnu.org \
--cc=brownts@troybrown.dev \
--cc=daniel@dpettersson.net \
--cc=eliz@gnu.org \
--cc=felician.nemeth@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).