From: Robert Pluim <rpluim@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: help-gnu-emacs@gnu.org
Subject: Re: osm requires json-parse-string
Date: Thu, 17 Mar 2022 11:38:09 +0100 [thread overview]
Message-ID: <875yocc19q.fsf@gmail.com> (raw)
In-Reply-To: <871qz0evxe.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Thu, 17 Mar 2022 10:05:17 +0000")
>>>>> On Thu, 17 Mar 2022 10:05:17 +0000, Eric S Fraga <e.fraga@ucl.ac.uk> said:
Eric> Ignore noise: it seems I need to actually build Emacs with json support.
But osm should be fixed to fall back to using json-read-from-string in
that case.
Robert
--
next prev parent reply other threads:[~2022-03-17 10:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 10:00 osm requires json-parse-string Eric S Fraga
2022-03-17 10:05 ` Eric S Fraga
2022-03-17 10:38 ` Robert Pluim [this message]
2022-03-17 10:08 ` Thibaut Verron
2022-03-17 10:26 ` Eric S Fraga
2022-03-17 10:40 ` Joost
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=875yocc19q.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--cc=help-gnu-emacs@gnu.org \
/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.
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).