From: Dmitry Gutov <dgutov@yandex.ru>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,
Lars Ingebrigtsen <larsi@gnus.org>,
45032@debbugs.gnu.org, Henry Minsky <henry.minsky@gmail.com>
Subject: bug#45032: 26.3; json-pretty-print of JSON with dict containing 't' as a key causes error
Date: Sat, 12 Dec 2020 23:25:38 +0200 [thread overview]
Message-ID: <56638b63-79a6-a543-4a43-5ee32a30d57e@yandex.ru> (raw)
In-Reply-To: <CAArVCkTdhaUoLUMJsPLS3hj0y98Hv33yuQqzMQGz-9Oo0_YtrQ@mail.gmail.com>
On 12.12.2020 16:28, Philipp Stephani wrote:
>> So this difference in keywords serialization was by design?
>>
>> ELISP> (json-serialize '(:a 1 :b 2))
>> "{\"a\":1,\"b\":2}"
>> ELISP> (json-serialize '((:a . 1) (:b . 2)))
>> "{\":a\":1,\":b\":2}"
> I can't answer that. When I wrote json.c, I had it only support
> hashtables, and list support is a later addition.
Perhaps we could agree that there _are_ some things that can be fixed in
json.c's behavior, then?
And use json.el's behavior in those situations as example.
next prev parent reply other threads:[~2020-12-12 21:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 21:19 bug#45032: 26.3; json-pretty-print of JSON with dict containing 't' as a key causes error Henry Minsky
2020-12-04 10:15 ` Lars Ingebrigtsen
2020-12-05 16:17 ` Basil L. Contovounesios
2020-12-05 19:35 ` Philipp Stephani
2020-12-05 22:13 ` Basil L. Contovounesios
2020-12-06 13:37 ` Lars Ingebrigtsen
2020-12-06 17:02 ` Philipp Stephani
2020-12-06 17:06 ` Lars Ingebrigtsen
2020-12-06 17:16 ` Philipp Stephani
2020-12-07 13:39 ` Lars Ingebrigtsen
[not found] ` <CAJo0r8gbrVk2wZatYS6_G7+7+tF_7VHO9KffrEMWanOK5BjuUg@mail.gmail.com>
2020-12-08 13:26 ` Lars Ingebrigtsen
2020-12-06 19:26 ` Dmitry Gutov
2020-12-12 14:28 ` Philipp Stephani
2020-12-12 21:25 ` Dmitry Gutov [this message]
2020-12-13 13:19 ` Philipp Stephani
2020-12-13 18:58 ` Dmitry Gutov
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=56638b63-79a6-a543-4a43-5ee32a30d57e@yandex.ru \
--to=dgutov@yandex.ru \
--cc=45032@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=henry.minsky@gmail.com \
--cc=larsi@gnus.org \
--cc=p.stephani2@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).