|
From: | Andreas Röhler |
Subject: | bug#21391: 24.5; `thing-at-point' should return a string |
Date: | Tue, 8 Nov 2016 09:22:24 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Icedove/45.4.0 |
On 07.11.2016 21:02, Eli Zaretskii wrote:
Cc: tino.calancha@gmail.com, 21391@debbugs.gnu.org From: Dmitry Gutov <dgutov@yandex.ru> Date: Mon, 7 Nov 2016 21:51:23 +0200It's pretty clearly a bug: most other "things" behave otherwise (list, sexp, symbol). I'd very much rather we didn't retain conceptual problems like that just for the sake of compatibility.Not sure which behavior you have in mind. The removal of properties? Or something else?Returning something other than a string or nil from thing-at-point.Didn't the function behave that way for quite some time? If so, how come it's suddenly a problem?
Assume a lot of bugs open like #21391.These library, which is excellent in base, needs a cleanup, resp. reconsideration.
[Prev in Thread] | Current Thread | [Next in Thread] |