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

Message #59 received at 9300 <at> debbugs.gnu.org (full text, mbox):

From: Tino Calancha <tino.calancha <at> gmail.com>
To: Dmitry Gutov <dgutov <at> yandex.ru>
Cc: f92capac <at> gmail.com, drew.adams <at> oracle.com, 9300 <at> debbugs.gnu.org,
 Tino Calancha <tino.calancha <at> gmail.com>
Subject: Re: bug#9300: 24.0.50; `bounds-of-thing-at-point' does not return
 nil when just after THING
Date: Mon, 20 Jun 2016 22:11:37 +0900 (JST)

> It's a matter of definition. If we say there is, then there is. We could also 
> add a variable, of course.
Sure, definitions are free.  Maybe the doc string is not clear enough: at 
point or right before than at point would be more precise.


>> * I) and II) agree
>
> Do they?
No they don't, sorry for that.
It should read:
V) and VI) agree but I) and II) disagree.  It seems it depends from the 
point of view and how you ask.  It shouldn't: or always there is a list or 
never.

>> but III) and IV disagree.
>>   I would expect III) and IV) returning the same value.
>
> Agree. But will you be satisfied if they both return "(foo bar)"?
I am sure you know my answer :-)

Regards,
Tino

Previous Next

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