|
From: | Dmitry Gutov |
Subject: | bug#9300: 24.0.50; `bounds-of-thing-at-point' does not return nil when just after THING |
Date: | Tue, 23 Feb 2016 03:01:12 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:44.0) Gecko/20100101 Thunderbird/44.0 |
I'm not sure it should be fixed.Your reasoning seems valid, however by now this behavior is ingrained into my expectations of how thing-at-point should behave.
This would be a breaking change. For instance, it will make (bounds-of-thing-at-point 'symbol) unsuitable for use in a completion-at-point-functions element, to compute the first two values of the returned list, because during completion you're most often "after" the symbol. And I do use it for that purpose in one third-party package.
emacs-eclim also uses it in eclim-java-show-documentation-for-current-element. At the very least, this will change the existing behavior.
[Prev in Thread] | Current Thread | [Next in Thread] |