From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Simen =?iso-8859-1?q?Heggest=F8yl?= Newsgroups: gmane.emacs.devel Subject: Re: JSON mode Date: Thu, 12 Nov 2015 21:01:00 +0100 Message-ID: <1447358460.13316.0@smtp.gmail.com> References: <1445164032.6127.0@smtp.gmail.com> <562390EC.5080709@yandex.ru> <56321AA6.6010908@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=-MbOvrZEpWKIDDtgXrU1F" X-Trace: ger.gmane.org 1447358569 24028 80.91.229.3 (12 Nov 2015 20:02:49 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 12 Nov 2015 20:02:49 +0000 (UTC) Cc: Josh Johnston , Artur Malabarba , emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 12 21:02:41 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Zwy4t-0007I6-J1 for ged-emacs-devel@m.gmane.org; Thu, 12 Nov 2015 21:02:39 +0100 Original-Received: from localhost ([::1]:49552 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zwy4t-0004UJ-0h for ged-emacs-devel@m.gmane.org; Thu, 12 Nov 2015 15:02:39 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47693) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zwy3S-00024e-UG for emacs-devel@gnu.org; Thu, 12 Nov 2015 15:01:11 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zwy3M-0004Qp-6j for emacs-devel@gnu.org; Thu, 12 Nov 2015 15:01:10 -0500 Original-Received: from mail-lf0-x229.google.com ([2a00:1450:4010:c07::229]:35197) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zwy3M-0004Qi-0j for emacs-devel@gnu.org; Thu, 12 Nov 2015 15:01:04 -0500 Original-Received: by lfdo63 with SMTP id o63so40599966lfd.2 for ; Thu, 12 Nov 2015 12:01:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:subject:to:cc:message-id:in-reply-to:references :mime-version:content-type; bh=ozKPWv2deS2C3vK13rSShlb5MY22Xsv+ReuU7n3G0wE=; b=THES0sqqBLKbxjHvVSVvvu3wl4bInxUg5H9ixkuYkzoDI37VwEXlJoUKqZQyKhbsh0 TuqGva3N8Pie9ViW+w3Gqwt175on3m3M20ntZVL/fT9inyvXWVnznkSguY3tmeylzLKC GAaCDly1MgfNPcMWZRB6fhAf/cxMRihbN4l0vrgdhE9W+nWxuwxiz4l7gE7k4bSa0rjT d+wHS6hgIYtb0egBoxC+riHr90X4Hg8GXUlTfR4u5ByYWEzaBhq2XrYqN7cegbvCPr4U aHtRrIYoF0GBKk/iPvQYNf45lxFEALpms4yIwBfifTWwwvkBNzOfcwndko67HY5ciTDX yisg== X-Received: by 10.25.159.193 with SMTP id i184mr8105126lfe.63.1447358462993; Thu, 12 Nov 2015 12:01:02 -0800 (PST) Original-Received: from [192.168.100.7] (cm-84.210.143.4.getinternet.no. [84.210.143.4]) by smtp.gmail.com with ESMTPSA id so5sm2517921lbb.43.2015.11.12.12.01.01 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Nov 2015 12:01:02 -0800 (PST) In-Reply-To: <56321AA6.6010908@yandex.ru> X-Mailer: geary/0.10.0 X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c07::229 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:194280 Archived-At: --=-MbOvrZEpWKIDDtgXrU1F Content-Type: text/plain; charset=utf-8; format=flowed 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 --=-MbOvrZEpWKIDDtgXrU1F Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hello again!

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

The latest ver= sion can be found at:
http://folk.uio.no/simenheg/json-mode.el. It requires at leas= t 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 belo= w.

Putting it into ELPA:

= + Updates may reach the users faster.

- json-mode.= el will need to support different versions of json.el
  (whi= ch 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, t= hough that may be because I
  work in a web development envi= ronment. My feeling of this is
  strengthened by the fact th= at Josh's JSON mode has been downloaded
  from MELPA over 40= ,000 times.

- The mode is very young, and currentl= y only used by me. Maybe it's
  too early to include it in E= macs, and it should be given a chance to
  ripen at ELPA fir= st.

What do you think?

--= Simen
= --=-MbOvrZEpWKIDDtgXrU1F--