unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Jackson Hamilton <jackson@jacksonrayhamilton.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Requesting review before pushing patch to ELPA
Date: Wed, 04 Feb 2015 16:58:57 -0500	[thread overview]
Message-ID: <jwvmw4tfiu3.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAGiE8AwhZPVsA9Ok4bDgsdVHkzit-Pyq5VqZUegphNhse6jN0w@mail.gmail.com> (Jackson Hamilton's message of "Wed, 4 Feb 2015 11:46:31 -0800")

> js2-mode is included in the repo for development and CI purposes.  I want to
> test in a clean environment (emacs -Q) and also on Travis CI.  Having that
> file available lets me easily add it to the load path.  I do exclude it in
> .elpaignore, because I expect that when context-coloring is installed, the
> package manager will handle the dependency instead.

Ah, right, that makes sense.

> Yes, it is a truer statement that (in its current state) context-coloring
> works fine for some modes, but requires those files for non-js2-mode
> JavaScript modes.

> esprima.js is sourced from here:
> https://github.com/jquery/esprima/blob/1114c32c4e0ffaf47864967a835fdc0a37909f14/esprima.js
> escope.js is sourced from here:
> https://github.com/estools/escope/blob/b191ec36b744f65df094c614510ca6125284a958/escope.js
> extraverse.js is sourced from here:
> https://github.com/estools/estraverse/blob/c280df4aa75d7846328aa436ee5acd04afafc543/estraverse.js

As long as we only redistribute these files without modifying them at
all, I think it's fine to have them as-is in elpa.git.

If I were you, I'd probably prefer to split them into a separate
"javascript support for context-coloring" package, but luckily I'm not
you, so feel free to do as you wish in this regard.


        Stefan



  parent reply	other threads:[~2015-02-04 21:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02  7:49 Requesting review before pushing patch to ELPA Jackson Hamilton
2015-02-02 17:58 ` Stefan Monnier
2015-02-03  5:57   ` Jackson Hamilton
2015-02-03 12:13     ` Artur Malabarba
2015-02-04  9:24       ` Jackson Hamilton
2015-02-04 11:15         ` Artur Malabarba
2015-02-04 11:16           ` Artur Malabarba
2015-02-03 17:51     ` Stefan Monnier
2015-02-04  9:32       ` Jackson Hamilton
2015-02-04 15:14         ` Stefan Monnier
2015-02-04 19:46           ` Jackson Hamilton
2015-02-04 19:48             ` Dmitry Gutov
2015-02-04 21:58             ` Stefan Monnier [this message]
2015-02-05  8:05               ` Jackson Hamilton
2015-02-05 14:10                 ` Stefan Monnier
2015-02-05 18:17                   ` Jackson Hamilton
2015-02-05 18:39                     ` Matthew Carter
2015-02-05 18:48                     ` Jackson Hamilton
2015-02-05 20:22                     ` Stefan Monnier
2015-02-04 15:13 ` Stefan Monnier

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=jwvmw4tfiu3.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=jackson@jacksonrayhamilton.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).