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 #77 received at 9300 <at> debbugs.gnu.org (full text, mbox):

From: Noam Postavsky <npostavs <at> users.sourceforge.net>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: f92capac <at> gmail.com, Eli Zaretskii <eliz <at> gnu.org>,
 Brief Busters <dgutov <at> yandex.ru>, 9300 <at> debbugs.gnu.org,
 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 19:59:33 -0400

Isn't the safest and simplest solution to rename the current
*-at-point to *-near-point, keep the *-at-point names as obsolete
aliases, and add new *-precisely-at-point functions with the
definitions from the thingatpt+ library? That way, current users of
*-at-point who happen to be relying the on *-near-point functionality
won't break. Only downside I can see is a slightly longer name for the
*-precisely-at-point callers, but that doesn't seem too bad.

What you do think?

Previous Next

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