From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.bugs Subject: bug#24969: 26.0.50; number-at-point Date: Mon, 21 Nov 2016 06:22:20 -0800 (PST) Message-ID: <7ed070bc-e4a7-468f-98e6-ac3b9660ed08@default> References: <87fumm9uti.fsf@gmx.net> <2b644637-6ade-b00f-aa35-07c390fc92c7@easy-emacs.de> <87twb2jkzs.fsf@users.sourceforge.net> <70732268-f26e-8639-335b-0c58689b2a9d@easy-emacs.de> <4b460e35-7e65-4224-a52b-083f87b24c70@default> <37f0b2e5-f446-a8c4-635a-5cc120cbb66e@easy-emacs.de> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1479738207 31289 195.159.176.226 (21 Nov 2016 14:23:27 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 21 Nov 2016 14:23:27 +0000 (UTC) Cc: Stephen Berman , 24969@debbugs.gnu.org To: Andreas =?UTF-8?Q?R=C3=B6hler?= , Noam Postavsky Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Nov 21 15:23:19 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c8pV8-0006hE-KJ for geb-bug-gnu-emacs@m.gmane.org; Mon, 21 Nov 2016 15:23:18 +0100 Original-Received: from localhost ([::1]:49734 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c8pVC-00049Z-4i for geb-bug-gnu-emacs@m.gmane.org; Mon, 21 Nov 2016 09:23:22 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34889) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c8pUx-00049A-Dr for bug-gnu-emacs@gnu.org; Mon, 21 Nov 2016 09:23:13 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c8pUr-0005Cj-Pt for bug-gnu-emacs@gnu.org; Mon, 21 Nov 2016 09:23:07 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:49648) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c8pUr-0005Cf-Mr for bug-gnu-emacs@gnu.org; Mon, 21 Nov 2016 09:23:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1c8pUr-0003Ig-HW for bug-gnu-emacs@gnu.org; Mon, 21 Nov 2016 09:23:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Drew Adams Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 21 Nov 2016 14:23:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 24969 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: unreproducible Original-Received: via spool by 24969-submit@debbugs.gnu.org id=B24969.147973815312652 (code B ref 24969); Mon, 21 Nov 2016 14:23:01 +0000 Original-Received: (at 24969) by debbugs.gnu.org; 21 Nov 2016 14:22:33 +0000 Original-Received: from localhost ([127.0.0.1]:36814 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c8pUP-0003I0-1k for submit@debbugs.gnu.org; Mon, 21 Nov 2016 09:22:33 -0500 Original-Received: from userp1040.oracle.com ([156.151.31.81]:20894) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c8pUN-0003Hn-1r for 24969@debbugs.gnu.org; Mon, 21 Nov 2016 09:22:31 -0500 Original-Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id uALEMM63005457 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 21 Nov 2016 14:22:23 GMT Original-Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by aserv0021.oracle.com (8.13.8/8.14.4) with ESMTP id uALEMM5k001905 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 21 Nov 2016 14:22:22 GMT Original-Received: from abhmp0009.oracle.com (abhmp0009.oracle.com [141.146.116.15]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id uALEML3j005579; Mon, 21 Nov 2016 14:22:21 GMT In-Reply-To: <37f0b2e5-f446-a8c4-635a-5cc120cbb66e@easy-emacs.de> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9.1 (1003210) [OL 12.0.6753.5000 (x86)] X-Source-IP: aserv0021.oracle.com [141.146.126.233] 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:125943 Archived-At: > > But the question is, "What constitutes a numeral?" in the given > > context. Whatever the context, I would expect some kind of > > well-defined delimiting. In Lisp I would expect what the Lisp > > reader would pick up as a number - nothing more. >=20 > The perspective of the lisp-programmer and the user of an editor may > be different here. Too vague. > The implementation at progress should pick any valid hex- octal- or > decimal integer at point. I disagree. Users should control whether they want a decimal, octal, or hex number at point - or any kind of number. Those are different things. In my code I define hex and decimal number at point functions. When code wants to get only a decimal number it does not want to pick up `FACE'. When code wants an octal number it does not want `987'. And nothing prevents a given context from defining a "number" category. That's we had, for Lisp numbers. Other modes are free to define a number syntax such that the (previous) implementation of `number-at-point' - or any local, mode/context-specific implementation, is in charge. > In a related case even characters are raised here, returning > a "b" for an "a", an "y" for an "x" etc. Far too loose and useless. Thingatpt lets you define any number of specific kinds of things. A predefined catch-all that does lots of things that are not clear is not helpful. > > In Lisp I would expect what the Lisp reader would pick up > > as a number - nothing more. And that would exclude picking > > up `2' within `foo-2'. >=20 > Not, when for example filenames inside shell-scripts etc. are > edited. What part of Lisp reader was not clear? The (previous) implementation uses what the current mode considers a number. It is based on the Lisp reader, but users (or Emacs) can define other number readings.