[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#72597: 30.0.60; Eglot: MarkedString with embedded Carriage Return
From: |
João Távora |
Subject: |
bug#72597: 30.0.60; Eglot: MarkedString with embedded Carriage Return |
Date: |
Thu, 5 Sep 2024 22:58:01 +0100 |
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
- bug#72597: 30.0.60; Eglot: MarkedString with embedded Carriage Return, Troy Brown, 2024/09/01
- bug#72597: 30.0.60; Eglot: MarkedString with embedded Carriage Return, Eli Zaretskii, 2024/09/02
- bug#72597: 30.0.60; Eglot: MarkedString with embedded Carriage Return, João Távora, 2024/09/02
- bug#72597: 30.0.60; Eglot: MarkedString with embedded Carriage Return, Daniel Pettersson, 2024/09/05
- bug#72597: 30.0.60; Eglot: MarkedString with embedded Carriage Return,
João Távora <=
- bug#72597: 30.0.60; Eglot: MarkedString with embedded Carriage Return, Eli Zaretskii, 2024/09/06
- bug#72597: 30.0.60; Eglot: MarkedString with embedded Carriage Return, Daniel Pettersson, 2024/09/06
- bug#72597: 30.0.60; Eglot: MarkedString with embedded Carriage Return, João Távora, 2024/09/06
- bug#72597: 30.0.60; Eglot: MarkedString with embedded Carriage Return, Troy Brown, 2024/09/08