On Nov 18, 2013 11:09 PM, "Bram Moolenaar" <Br...@moolenaar.net> wrote:
>
>
> Eddie Monge wrote:
>
> > JSON is a hyper-strict subset of JavaScript-like syntax. It should not
> > be treated as JS. Treating it as JS breaks all sorts of other plugins
> > for minimum gain, if any.
> >
> > https://github.com/b4winckler/macvim/pull/39
>
> OK, but it would be nice to have syntax and indent files for json.
> Which would borrow some parts from Javascript.
> Can't be difficult, someone wants to take this on?
You can just as well borrow parts of YAML. It is also a JSON superset, but with way too less features as the programming language like JavaScript.
>
> Oh, Ingo mentions there is some. Hmm, it's unclear where it came from.
>
>
> --
> I have read and understood the above. X________________
>
> /// Bram Moolenaar -- Br...@Moolenaar.net -- http://www.Moolenaar.net \\\
> /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
> \\\ an exciting new programming language -- http://www.Zimbu.org ///
> \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+u...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
I'm the author of the JSON plugin Ingo mentioned[1]. It's built on Jeroen Ruigrok van der Werven's JSON plugin[2] and he himself recommends this update. Both works are MIT licensed[3].
I'd hereby like to submit the plugin for inclusion in the official runtime and commit myself to its maintenance. Since 9 months ago Ingo approached me about it but I wasn't sure at the moment if the plugin was ready or popular enough. With no marketing on my part the plugin has reached 241 stars on github and we've closed 20 issues[4] as its functionality has grown and been refined.
Thanks,
-Eli Parra
1: https://github.com/elzr/vim-json
2: http://www.vim.org/scripts/script.php?script_id=1945
3: https://github.com/elzr/vim-json/issues/6
4: https://github.com/elzr/vim-json/issues?q=is%3Aissue+is%3Aclosed
Thanks for the tips.
I've updated/added maintainer headers & moved to "hi def link" in the syntax file.
Yes on the Vim license.
I've just emailed Rogerz Zhang about our thread, asking him to chime in.
-Eli
On Saturday, August 23, 2014 9:24:17 PM UTC+8, Bram Moolenaar wrote:
> Eli -
> > I'm the author of the JSON plugin Ingo mentioned[1]. It's built on
>
> > Jeroen Ruigrok van der Werven's JSON plugin[2] and he himself
>
> > recommends this update. Both works are MIT licensed[3].
> The indent file mentions Rogerz Zhang as the maintainer.
>
> Apparently it's from http://github.com/rogerz/vim-json.
>
> I rather have him send it to me.
I've add an MIT license[1] to my original code. I assume it is compatible with VIM license.
@Eli,
I've add a link to your repository[2] since I'm no longer maintaining it. Thanks for your work.
1. https://github.com/rogerz/vim-json/blob/master/LICENSE
2. https://github.com/elzr/vim-json
--
rogerz
Bram, I've changed the header of the indent file on my JSON plugin so it now lists me as the current maintainer and rogerz as the original author (it had already started diverging from Zhang's version).
With this and rogerz's MIT licensing, I think we're ready. :)
thank you for your efforts.
I've noticed this plugin will conceal double quotes by default.
For me, this is unacceptable. I, and I assume many programmers, prefer
to see the actual code I'm editing. All of it.
Sorry to add this discordant note to the thread. It's no big deal to use
the provided g: variable but defaults are important.
Cheers,
--
David