From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.bugs Subject: bug#9300: 24.0.50; `bounds-of-thing-at-point' does not return nil when just after THING Date: Mon, 20 Jun 2016 17:47:27 -0700 (PDT) Message-ID: References: <67e48e39-f31f-5170-a552-ac33509ffcd6@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1466470158 32200 80.91.229.3 (21 Jun 2016 00:49:18 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 21 Jun 2016 00:49:18 +0000 (UTC) Cc: f92capac@gmail.com, tino.calancha@gmail.com, 9300@debbugs.gnu.org, Brief Busters To: Noam Postavsky Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Jun 21 02:49:04 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bF9sE-0008Tq-0j for geb-bug-gnu-emacs@m.gmane.org; Tue, 21 Jun 2016 02:49:02 +0200 Original-Received: from localhost ([::1]:47290 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bF9sD-0000Gt-5R for geb-bug-gnu-emacs@m.gmane.org; Mon, 20 Jun 2016 20:49:01 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52022) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bF9rJ-0008Ie-UJ for bug-gnu-emacs@gnu.org; Mon, 20 Jun 2016 20:48:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bF9rG-0006VR-KM for bug-gnu-emacs@gnu.org; Mon, 20 Jun 2016 20:48:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:35848) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bF9rG-0006VN-H2 for bug-gnu-emacs@gnu.org; Mon, 20 Jun 2016 20:48:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1bF9rG-0008S9-AI for bug-gnu-emacs@gnu.org; Mon, 20 Jun 2016 20:48:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Drew Adams Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 21 Jun 2016 00:48:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 9300 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 9300-submit@debbugs.gnu.org id=B9300.146647006132462 (code B ref 9300); Tue, 21 Jun 2016 00:48:02 +0000 Original-Received: (at 9300) by debbugs.gnu.org; 21 Jun 2016 00:47:41 +0000 Original-Received: from localhost ([127.0.0.1]:48185 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bF9qv-0008RW-9F for submit@debbugs.gnu.org; Mon, 20 Jun 2016 20:47:41 -0400 Original-Received: from aserp1040.oracle.com ([141.146.126.69]:26718) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bF9qt-0008RJ-Jo for 9300@debbugs.gnu.org; Mon, 20 Jun 2016 20:47:40 -0400 Original-Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u5L0lWYU001505 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 21 Jun 2016 00:47:32 GMT Original-Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by userv0022.oracle.com (8.14.4/8.13.8) with ESMTP id u5L0lVL3000684 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 21 Jun 2016 00:47:32 GMT Original-Received: from abhmp0010.oracle.com (abhmp0010.oracle.com [141.146.116.16]) by aserv0122.oracle.com (8.13.8/8.13.8) with ESMTP id u5L0lTTp005796; Tue, 21 Jun 2016 00:47:30 GMT In-Reply-To: X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9 (901082) [OL 12.0.6744.5000 (x86)] X-Source-IP: userv0022.oracle.com [156.151.31.74] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:119858 Archived-At: > 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. >=20 > What you do think? That's possible (and I appreciate your trying to find a diplomatic way to get this bug fixed), but I don't think that is the best approach. We should aim to have a reasonable name, not just something that doesn't conflict. There is little sense in abandoning the most reasonable name for this, IMO. This is what the library is intended for: returning a thing at point. If the name "*-at-point" is kept (for behavior that is really at point) then the worst that will happen is that some users might complain that they no longer get a thing that is before point but not also at point. And that won't even happen for distributed Emacs code, which should replace any appropriate calls to *-at by *-near (where appropriate means that you really do want to retrieve the thing before point as well as the thing at point). This is a simple off-by-one bug. It really should not require anything to be deprecated. Just because someone might have gotten used to the bugged behavior is not a good reason not to fix this bug. If going the direction you suggest is the best compromise that can be had, I'd suggest using the name *-at-pt instead of *-precisely-at-point. IOW, just change "point" to "pt". That's not the fix I prefer, and it hurts discoverability (matches against "point"), and it doesn't jibe with names such as `find-file-at-point', but I think it's better than something as artificial as *-precisely-at-point. That name just makes one wonder.