From: "T. V. Raman" <raman@users.sf.net>
To: hober0@gmail.com
Cc: emacs-devel@gnu.org
Subject: Re: json.el - JavaScript Object Notation parser / generator for Emacs Lisp
Date: Thu, 14 Feb 2008 06:15:38 -0800 [thread overview]
Message-ID: <18356.19722.474101.644367@gargle.gargle.HOWL> (raw)
In-Reply-To: <m2zlu7mg3n.fsf@gmail.com>
And I use json.el in emacspeak/g-client -- an emacs binding to
the various Google services.
>>>>> "Ted" == Edward O'Connor <hober0@gmail.com> writes:
Ted> RMS wrote, several months ago, about my json.el:
>> If a lot of people start wanting this facility, then it
>> would be good to include it in Emacs. Please let me know
>> if that happens.
Ted>
Ted> I know of several libraries/tools which use json.el,
Ted> including augment.el, a facebook api client, rcov.el,
Ted> and at least one twitter api client. Additionally, I
Ted> know of at least one library, twit.el, whose author
Ted> avoided using json.el solely because it isn't included
Ted> in Emacs.
>> From twit.el's commentary:
Ted>
>> This uses Twitter's XML-based api, not the JSON one
>> because i would like to avoid making the user install
>> third-party libraries to use it.
--
Best Regards,
--raman
Email: raman@users.sf.net
WWW: http://emacspeak.sf.net/raman/
AIM: emacspeak GTalk: tv.raman.tv@gmail.com
PGP: http://emacspeak.sf.net/raman/raman-almaden.asc
Google: tv+raman
IRC: irc://irc.freenode.net/#emacs
next prev parent reply other threads:[~2008-02-14 14:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m21wwvfhbr.fsf@roisin.local>
[not found] ` <E1FM3dc-0006c2-BV@fencepost.gnu.org>
[not found] ` <3b31caf90603220930k1f133151m81ab6986e9aff946@mail.gmail.com>
[not found] ` <E1FMVmY-0006om-Oi@fencepost.gnu.org>
2008-02-11 19:46 ` json.el - JavaScript Object Notation parser / generator for Emacs Lisp Edward O'Connor
2008-02-12 14:22 ` Leo
2008-02-12 20:59 ` Edward O'Connor
2008-02-12 18:39 ` Phil Hagelberg
2008-02-13 0:25 ` Richard Stallman
2008-02-14 14:15 ` T. V. Raman [this message]
2008-02-19 23:49 ` Edward O'Connor
2008-02-21 19:43 ` Michael Olson
2008-02-21 22:28 ` Miles Bader
2008-02-21 23:46 ` Michael Olson
2008-02-22 0:20 ` Phil Hagelberg
2008-02-22 1:08 ` Miles Bader
2008-02-22 22:56 ` Richard Stallman
2008-02-22 23:11 ` javascript.el (was: json.el - JavaScript Object Notation parser / generator for Emacs Lisp) Phil Hagelberg
2008-02-22 23:18 ` javascript.el Lennart Borgman (gmail)
2008-02-23 0:35 ` javascript.el Phil Hagelberg
2008-02-23 0:44 ` javascript.el Lennart Borgman (gmail)
2008-02-23 0:28 ` javascript.el (was: json.el - JavaScript Object Notation parser / generator for Emacs Lisp) Phil Hagelberg
2008-02-23 19:29 ` Richard Stallman
2008-02-26 19:56 ` Phil Hagelberg
2008-02-27 16:07 ` Richard Stallman
2008-02-22 0:30 ` json.el - JavaScript Object Notation parser / generator for Emacs Lisp Miles Bader
2008-02-22 1:25 ` Michael Olson
2008-02-26 6:58 ` Edward O'Connor
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=18356.19722.474101.644367@gargle.gargle.HOWL \
--to=raman@users.sf.net \
--cc=emacs-devel@gnu.org \
--cc=hober0@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).