This thing-at-point call was introduced in
3cd52f4993f73b53de8a4f380e2f5a7b75e40437, but I'm unable to find a
scenario where the third element in a sexp is indicative of a
definition.
I've added a test so if this has broken a feature, we can ensure that
the use case here stays fixed.
Coverage remained the same at 45.596% when pulling 37efaa7a19f14a911fb4900bde556e9875135c6a on looking_at_def into ff68dbee6f04ef6dd4b29301c1d42b584ab1da9d on master.
This thing-at-point call was introduced in 3cd52f4993f73b53de8a4f380e2f5a7b75e40437, but I'm unable to find a scenario where the third element in a sexp is indicative of a definition.
I've added a test so if this has broken a feature, we can ensure that the use case here stays fixed.
Fixes #31