bedmap produces incorrect results

[sjneph]

There is a current scenario where bedmap will produce incorrect results.

foo1.bed:
chr1 1 200 a 1
chr1 10 20 b 3
chr1 50 150 c 4

foo2.bed:
chr1 1 200 a 1

Without --faster, bedmap should always produce correct results even with nested elements. The current output from:
bedmap --count --bp-ovr 11 foo1.bed foo2.bed

is:
1
0
0

when it should be:
1
0
1

Row two of the reference cannot have qualifying overlaps as its length is 10, and I used --bp-ovr 11. If --bp-ovr is 10 or less, the output is correct. If the file order is reversed, the output is correct. This needs to be fixed asap.

[sjneph]

Fixed in commit 2cda151