-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Empty" overlays are ignored #14
Comments
@ShingoFukuyama Ping? :) |
I'm OK with this patch. If you want to add it, please just push or send PR (makes more one-work separate clear and makes easy to revert the whole PR if found issues). |
IIUC there is a small oversight in the proposed patch (thanks @alphapapa!): In |
@sgleizes Thanks, good catch. |
@alphapapa you aren't by any chance interested in maintaining this package? Or any other packages in the orphanage for that matter? |
Hi,
I've noticed that "empty" overlays (i.e. overlays whose beginning and end points are the same) are ignored in functions like
ov-next
andov-prev
. This seems to be becauseov-at
is used, which usesoverlays-at
, which does not return empty overlays. However,overlays-in
does return them.I did some refactoring of
ov-next
andov-prev
which seems to fix it, but they should be tested further. I also usedpcase
to simplify the dispatching. Also, theany
,property
, andproperty-value
functions could be factored out, since they're the same except for which functions they call to get next/previous overlays.Another issue is that
ov-at
only returns one overlay even if there are multiple overlays there. This becomes a small problem when other functions are built on top of it. :) This is a deeper problem, though. Probably, there should be sibling functions to these that return all overlays rather than only one.Please let me know what you think. I can send a PR if you like, but this probably needs a bit more work.
This library is extremely useful, thanks for making it!
The text was updated successfully, but these errors were encountered: