From: Josh Johnston <josh@x-team.com>
To: "Clément Pit--Claudel" <clement.pit@gmail.com>
Cc: "Simen Heggestøyl" <simenheg@gmail.com>, emacs-devel@gnu.org
Subject: Re: JSON mode
Date: Tue, 13 Dec 2016 10:05:56 +1100 [thread overview]
Message-ID: <CAF9DJzT7C8uNKZgYwWXeZGktJ0v0Ki4YPx2wKv6sjzxhCsB1Lw@mail.gmail.com> (raw)
In-Reply-To: <2b5701cf-0636-baa7-2eec-a494aa9b9af6@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1972 bytes --]
Thanks Simen!
On Tue, Dec 13, 2016 at 9:27 AM, Clément Pit--Claudel <clement.pit@gmail.com
> wrote:
> Thanks for clarifying! This makes a lot of sense.
>
> Cheers,
> Clément.
>
> On 2016-12-12 15:38, Simen Heggestøyl wrote:
> > Hi Clément.
> >
> > More than a year ago I contacted the author of the original JSON mode,
> > Josh Johnston, to see if we could get JSON mode included in Emacs. At
> > the same time it seemed like a good idea to remove its basis on JS mode,
> > since various issues come from it [1, 2]. We would also need to either
> > get its two MELPA dependencies into GNU ELPA or replace them.
> >
> > I had already written a JSON mode that I had been using privately for a
> > while that didn't depend on JS mode, and that didn't depend on any MELPA
> > packages (it uses json.el bundled with Emacs for the same
> > functionality). I suggested we merge our two modes before moving it into
> > Emacs or GNU ELPA. Josh then pointed out that everything from the old
> > mode was already implemented in the new one. So while the new JSON
> > mode's code isn't directly based on the old JSON mode's, it carries on
> > its name, its functionality, and the same default keybindings.
> >
> > Lastly we agreed to try and make the transition to the new mode as
> > smooth as possible for the users. I've released the new mode with a
> > lower version number than Josh's, so Josh's mode will still be installed
> > for those who have configured MELPA. By doing so I was hoping to get
> > more testing, and finding out whether the new approach is really
> > better. If it turns out that it's not, we'll just retract it. If it
> > turns out that it is, we'll increase the version number higher than the
> > old mode (for instance 2.0).
> >
> > -- Simen
> >
> > [1] https://github.com/joshwnj/json-mode/issues/32
> > [2] https://github.com/joshwnj/json-mode/issues/34
> >
> >
>
>
--
X-Team (http://x-team.com)
[-- Attachment #2: Type: text/html, Size: 2892 bytes --]
next prev parent reply other threads:[~2016-12-12 23:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-18 10:27 JSON mode Simen Heggestøyl
2015-10-18 12:22 ` Artur Malabarba
2015-10-18 12:30 ` Dmitry Gutov
2015-10-18 14:08 ` Simen Heggestøyl
2015-10-18 15:32 ` Dmitry Gutov
2015-10-29 3:47 ` Josh Johnston
2015-10-29 13:09 ` Dmitry Gutov
2015-11-12 20:01 ` Simen Heggestøyl
2015-11-12 22:05 ` John Wiegley
2015-11-12 23:24 ` Dmitry Gutov
2015-11-13 0:54 ` Artur Malabarba
2015-11-14 10:40 ` Stephen Leake
2015-11-14 11:14 ` Simen Heggestøyl
2016-12-11 14:58 ` Simen Heggestøyl
2016-12-12 6:08 ` John Wiegley
2016-12-12 13:39 ` Clément Pit--Claudel
2016-12-12 20:38 ` Simen Heggestøyl
2016-12-12 22:27 ` Clément Pit--Claudel
2016-12-12 23:05 ` Josh Johnston [this message]
2016-12-13 10:14 ` Nicolas Petton
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=CAF9DJzT7C8uNKZgYwWXeZGktJ0v0Ki4YPx2wKv6sjzxhCsB1Lw@mail.gmail.com \
--to=josh@x-team.com \
--cc=clement.pit@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=simenheg@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).