unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Simen Heggestøyl" <simenheg@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Josh Johnston <josh@x-team.com>,
	Artur Malabarba <bruce.connor.am@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: JSON mode
Date: Thu, 12 Nov 2015 21:01:00 +0100	[thread overview]
Message-ID: <1447358460.13316.0@smtp.gmail.com> (raw)
In-Reply-To: <56321AA6.6010908@yandex.ru>

[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]

Hello again!

With #21616 and #21798 installed, json.el is now instrumented to make
the new json-mode.el able to reach feature parity with Josh's.

The latest version can be found at:
http://folk.uio.no/simenheg/json-mode.el. It requires at least version
1e363a8e of Emacs to fully work.

Now the question on where to put the new json-mode.el remains.

I've tried to summarize what I perceive as the pros (+) and cons (-)
of putting it into ELPA vs. bundling it with Emacs below.

Putting it into ELPA:

+ Updates may reach the users faster.

- json-mode.el will need to support different versions of json.el
  (which is bundled with Emacs).

Bundling it with Emacs:

+ Somehow I feel that a modern text editor should come with support
  for editing JSON data out of the box, though that may be because I
  work in a web development environment. My feeling of this is
  strengthened by the fact that Josh's JSON mode has been downloaded
  from MELPA over 40,000 times.

- The mode is very young, and currently only used by me. Maybe it's
  too early to include it in Emacs, and it should be given a chance to
  ripen at ELPA first.

What do you think?

-- Simen

[-- Attachment #2: Type: text/html, Size: 1660 bytes --]

  reply	other threads:[~2015-11-12 20:01 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 [this message]
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
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=1447358460.13316.0@smtp.gmail.com \
    --to=simenheg@gmail.com \
    --cc=bruce.connor.am@gmail.com \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=josh@x-team.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).