GNU bug report logs - #9300
24.0.50; `bounds-of-thing-at-point' does not return nil when just after THING

Previous Next

Full log

View this message in rfc822 format

From: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
To: 9300 <at> debbugs.gnu.org
Subject: bug#9300: 24.0.50; `bounds-of-thing-at-point' does not return nil when just after THING
Date: Tue, 21 Jun 2016 08:14:22 +0200

On 20.06.2016 22:04, Eli Zaretskii wrote:
>> Date: Mon, 20 Jun 2016 10:50:27 -0700 (PDT)
>> From: Drew Adams <drew.adams <at> oracle.com>
>> Cc: f92capac <at> gmail.com, 9300 <at> debbugs.gnu.org, dgutov <at> yandex.ru
>>
>>> FWIW, I agree with Dmitry: this has been a de-facto behavior long
>>> enough to consider it the correct one. If documentation is confusing
>>> in that it says otherwise, we should fix the documentation.
>> I couldn't disagree more.
>>
>> It is wrong to consider the current behavior "the correct one",
>> regardless of how long it has been in place.  It is wrong because
>> you cannot use it in a general and precise way.  It is just broken.
>> It has been broken for a long time, but it is broken nevertheless.
> That's immaterial.  It is being used in many places, and it's
> obviously useful.

It is useful, but not in the way of the lemma "at-point". At-point means 
at cursor-position.
What is expected when calling "C-x ="  -- probably not info WRT char 
after, but at cursor position.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.