From: Arun Isaac <arunisaac@systemreboot.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Ricardo Wurmus <rekado@elephly.net>, 27132@debbugs.gnu.org
Subject: bug#27132: [PATCH 6/6] gnu: Add uglify-js.
Date: Sat, 03 Jun 2017 00:30:01 +0530 [thread overview]
Message-ID: <c4ea7f07.AEAAK4j0Od8AAAAAAAAAAAPG5r8AAAACwQwAAAAAAAW9WABZMbW7@mailjet.com> (raw)
In-Reply-To: <878tlb29ul.fsf@gnu.org>
Ludovic Courtès writes:
> Ricardo Wurmus <rekado@elephly.net> skribis:
>
>> * gnu/packages/lisp.scm (uglify-js): New variable.
>
> LGTM! This will definitely be useful for JS packaging like the things
> Arun was looking at. Thank you for doing this!
Yes, I'll use this package (uglify-js) to minify javascript now. But, I
think it would be better to contribute this wrapper script upstream to
the `cl-uglify-js' project. Then, we would be able to remove this
`uglify-js' package and just use `sbcl-cl-uglify-js'.
next prev parent reply other threads:[~2017-06-02 19:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 16:53 bug#27132: [PATCH 0/6] Add uglify-js Ricardo Wurmus
2017-05-29 17:21 ` bug#27132: [PATCH 1/6] gnu: Add sbcl-cl-ppcre-unicode Ricardo Wurmus
2017-05-29 17:21 ` bug#27132: [PATCH 2/6] gnu: Add sbcl-parse-js Ricardo Wurmus
2017-06-01 12:00 ` Ludovic Courtès
2017-05-29 17:21 ` bug#27132: [PATCH 3/6] gnu: Add sbcl-parse-number Ricardo Wurmus
2017-06-01 12:01 ` Ludovic Courtès
2017-05-29 17:21 ` bug#27132: [PATCH 4/6] gnu: Add sbcl-iterate Ricardo Wurmus
2017-06-01 12:01 ` Ludovic Courtès
2017-05-29 17:21 ` bug#27132: [PATCH 5/6] gnu: Add sbcl-cl-uglify-js Ricardo Wurmus
2017-06-01 12:02 ` Ludovic Courtès
2017-05-29 17:21 ` bug#27132: [PATCH 6/6] gnu: Add uglify-js Ricardo Wurmus
2017-06-01 12:03 ` Ludovic Courtès
2017-06-01 21:33 ` Ricardo Wurmus
2017-06-02 19:00 ` Arun Isaac [this message]
2017-06-01 12:00 ` bug#27132: [PATCH 1/6] gnu: Add sbcl-cl-ppcre-unicode Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c4ea7f07.AEAAK4j0Od8AAAAAAAAAAAPG5r8AAAACwQwAAAAAAAW9WABZMbW7@mailjet.com \
--to=arunisaac@systemreboot.net \
--cc=27132@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=rekado@elephly.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.