From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Artur Malabarba Newsgroups: gmane.emacs.devel Subject: Re: JSON mode Date: Sun, 18 Oct 2015 13:22:44 +0100 Message-ID: References: <1445164032.6127.0@smtp.gmail.com> Reply-To: bruce.connor.am@gmail.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a114121140089be0522601632 X-Trace: ger.gmane.org 1445170979 14413 80.91.229.3 (18 Oct 2015 12:22:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 18 Oct 2015 12:22:59 +0000 (UTC) Cc: emacs-devel To: =?UTF-8?Q?Simen_Heggest=C3=B8yl?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Oct 18 14:22:54 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 1ZnmzE-0001qY-2l for ged-emacs-devel@m.gmane.org; Sun, 18 Oct 2015 14:22:52 +0200 Original-Received: from localhost ([::1]:33560 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZnmzD-0002aj-BQ for ged-emacs-devel@m.gmane.org; Sun, 18 Oct 2015 08:22:51 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46866) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Znmz8-0002aH-Vm for emacs-devel@gnu.org; Sun, 18 Oct 2015 08:22:48 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Znmz7-0005j3-Sy for emacs-devel@gnu.org; Sun, 18 Oct 2015 08:22:46 -0400 Original-Received: from mail-lf0-x244.google.com ([2a00:1450:4010:c07::244]:36525) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Znmz7-0005iy-Lz for emacs-devel@gnu.org; Sun, 18 Oct 2015 08:22:45 -0400 Original-Received: by lffz202 with SMTP id z202so9233890lff.3 for ; Sun, 18 Oct 2015 05:22:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=tppRVGeq8nmc5zquw3eFkImTg5kfuZfPEZW+oSxEisc=; b=tIXXEiqMcr/2wMOCEqkEcqdUE+cklSWIPZN7vmOU4qkPnE/ncTVsnDS8wUUaqKA8rm 2WJsoMtcA3hIyoNPNEJv37iaWzWVDu67euh1AsGUGAvc67WR6WRrNV0IoSs466DfrLPy MNtNCpMIMKyr+ZOIsC4QKy2UNDNU8h+1XHPHbglT3lwXmKfrTsxhKsLVmezQMHNZaJwZ +IuEpDb8MPGbju1NEDquhmxIHu10X6wNwg6AVhoHyudsr8N89q7yzlV20F91WkiqTxS+ ukDe7jAc/eSoezRjvph7lGcoMnSPalYUz488+T6YdmIbblUX/kQANqOaF480/lux2z70 Br1w== X-Received: by 10.25.91.4 with SMTP id p4mr7782106lfb.95.1445170964890; Sun, 18 Oct 2015 05:22:44 -0700 (PDT) Original-Received: by 10.25.22.197 with HTTP; Sun, 18 Oct 2015 05:22:44 -0700 (PDT) Original-Received: by 10.25.22.197 with HTTP; Sun, 18 Oct 2015 05:22:44 -0700 (PDT) In-Reply-To: <1445164032.6127.0@smtp.gmail.com> X-Google-Sender-Auth: RQJOAitHtZyyteYyxgr_VCmhuNY X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c07::244 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:191938 Archived-At: --001a114121140089be0522601632 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Sounds reasonable to me. On 18 Oct 2015 11:27 am, "Simen Heggest=C3=B8yl" wrote= : > > Hi! > > With the newly introduced json-sexp-mode, I was reminded of a JSON > editing mode that I started toying with some time ago, and have been > using privately. > > It arose from my frustration of Emacs having JavaScript mode as the > JSON editing mode, making it more difficult than necessary to have > separate settings for editing JavaScript and JSON. > > The code can be found at: http://folk.uio.no/simenheg/json-mode.el. > > Compared to using the built-in JavaScript mode, the dedicated JSON > mode offers the following advantages: > > - A separate mode hook and namespace, providing for instance > `json-mode-indent-offset'. > > - SMIE based movement and indentation. > > - Key bindings and a menu entry for prettifying JSON data. > > - Separate highlighting of JSON keywords, object names and values. > > If you agree with me that Emacs should have a dedicated mode for > editing JSON, I'll be happy to help integrating it (be it this mode, > or another one, if it proves insufficient). > > -- Simen --001a114121140089be0522601632 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Sounds reasonable to me.

On 18 Oct 2015 11:27 am, "Simen Heggest=C3=B8yl" &= lt;simenheg@gmail.com> wrote:<= br> >
> Hi!
>
> With the newly introduced json-sexp-mode, I was reminded of a JSON
> editing mode that I started toying with some time ago, and have been > using privately.
>
> It arose from my frustration of Emacs having JavaScript mode as the > JSON editing mode, making it more difficult than necessary to have
> separate settings for editing JavaScript and JSON.
>
> The code can be found at: http://folk.uio.no/simenheg/json-mode.el.
>
> Compared to using the built-in JavaScript mode, the dedicated JSON
> mode offers the following advantages:
>
> =C2=A0- A separate mode hook and namespace, providing for instance
> =C2=A0 =C2=A0`json-mode-indent-offset'.
>
> =C2=A0- SMIE based movement and indentation.
>
> =C2=A0- Key bindings and a menu entry for prettifying JSON data.
>
> =C2=A0- Separate highlighting of JSON keywords, object names and value= s.
>
> If you agree with me that Emacs should have a dedicated mode for
> editing JSON, I'll be happy to help integrating it (be it this mod= e,
> or another one, if it proves insufficient).
>
> -- Simen

--001a114121140089be0522601632--