The actual patch is maintained in:

https://github.com/nene/esprima/tree/linenr-in-range

Having the esprima source right inside JSDuck source tree is more
convenient for other developers as there's no need to additionally clone
esprima repository in addition to jsduck itself.

Also the esprima.js needs to be modified only rarely.

This got broken by previous commit that added printing of filename.

Except for one case with @since tag where I can't access the context of
input filename.

Only in UNIX.

Because a class can consist of several files, list all the files
separated by spaces.

Using both Gemfile for bundler and a .gemspec for gem doesn't seem to
work quite well together.  Besides I'm not really making much use of
bunder, so I feel I'm better off without this additional complexity.

Though, this means I need to explicitly list the dependencies to be
installed for development, but there are only a few, so it really
shouldn't be much of an issue.

Allows defining a different version as a starting point for generating
@new tags.

Removed the old yellow "Private" sign from classes - they now have an
orange "private" bubble just like members.  All other meta tags now also
show up in class header.

Without this the lookup table will report duplicates that aren't really
there.

First off just a tag-based implementation of Ext4 overrides.

As we no more support JRuby, we can require therubyracer as a dependency.

This reverts commit aba71287.

Problem caused by the addition of --ext4-events option, which caused the
append_ext4_event_options method to no more behave as it did.

As I'm dropping JRuby support, there's no need for extra redirection
layer.

Not needed for day-to-day testing, a drag on performance.

IE7 & 8 will download this kind of URL twice, so better to use a script.

See also: http://stackoverflow.com/questions/4831741/can-i-change-all-my-http-links-to-just

Won't work in Ruby 1.8.

This way it'll play nicely when JSDuck is hosted over HTTPS.

Rewrite #! links into ?print= links.

The stylesheet assumes .x-panel-body div which wasn't present in print
page.

I use it rarely, so no need to waste time on creating that.

We're still defaulting to auto-detection, but this option can be used to
override the auto-detection.

Otherwise we need to pass around the ParallelWrap instance or config
for it, which is annoying.  Parallelization is more of an implementation
detail - passing it explicitly to every class that needs to make use
of it doesn't really fit to the interface of these classes.  We
shouldn't need to change the interface when switching from normal each
loop to parallel each.  So a singleton class it is.