From: Kevin Carhart <kevin@carhart.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] better line numbers for runtimes
Date: Fri, 27 Jan 2017 14:15:53 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.03.1701271408530.31432@carhart.net> (raw)
In-Reply-To: <20170027095111.eklhad@comcast.net>
Since minified code is a thorn in our side, I bit the bullet and bundled
up de-minification code using esprima and escodegen, in a modular way so
that it can be popped on to the makefile and then popped back off again.
It's 10,000 lines of javascript, but you can think of it as a black box
and just call it. It's just a dev tool and isn't intended as a patch
idea for the real edbrowse.
https://github.com/KevinCarhart/esbrowse/archive/master.zip
prev parent reply other threads:[~2017-01-27 22:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 14:51 [Edbrowse-dev] infinite loop Karl Dahlke
2017-01-27 22:15 ` Kevin Carhart [this message]
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=alpine.LRH.2.03.1701271408530.31432@carhart.net \
--to=kevin@carhart.net \
--cc=Edbrowse-dev@lists.the-brannons.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.
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 NNTP newsgroup(s).