all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>,
	"Noam Postavsky" <npostavs@users.sourceforge.net>
Cc: Stephen Berman <stephen.berman@gmx.net>, 24969@debbugs.gnu.org
Subject: bug#24969: 26.0.50; number-at-point
Date: Sun, 20 Nov 2016 13:28:46 -0800 (PST)	[thread overview]
Message-ID: <4b460e35-7e65-4224-a52b-083f87b24c70@default> (raw)
In-Reply-To: <70732268-f26e-8639-335b-0c58689b2a9d@easy-emacs.de>

> > I guess it depends on what a user would expect of a
> > "number-at-point" function.  A priori, I don't see why s?he
> > would expect a non-nil answer if the numeral is embedded in
> > text that does not delimit a numeral (e.g. non whitespace text).
> > But maybe it is OK.
> >
> > Would we expect the same kind of behavior for `sexp-at-point'
> > if a sexp were not surrounded by chars that delimit a sexp?
> >
> > In Lisp, at least, there is no number at point, in `foo-2'.
> > That is, the Lisp parser (reader) would never pick up the
> > `2' as a number here.
> >
> > I'm partial to use of thingatpt for Lisp, but I realize that
> > it is used in other contexts too.
> 
> In use here for edit-purposes.  For example raise all numbers
> in a region - makes it easier sometimes to adapt stuff, which
> doesn't deserve an own template.

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.  And that would
exclude picking up `2' within `foo-2'.

> Have a first implementation with ar-add-numbers in
> https://github.com/andreas-roehler/werkstatt/blob/master/misc/misc-
> utils.el - just re-writing it.

There is no `ar-add-numbers' or `add-numbers' in that file
(having downloaded it just now).  Perhaps you meant
`ar-add-to-number-cummulative'?  That is undefined, without
`ar-bounds-of-number-atpt' (not in the file).

Anyway, my point was made above.





  reply	other threads:[~2016-11-20 21:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-20 12:47 bug#24969: 26.0.50; number-at-point Andreas Röhler
2016-11-20 12:53 ` Stephen Berman
2016-11-20 13:53   ` Andreas Röhler
2016-11-20 14:15     ` npostavs
2016-11-20 16:19       ` Drew Adams
2016-11-20 16:35         ` Noam Postavsky
2016-11-20 16:58           ` Drew Adams
2016-11-20 19:26             ` Andreas Röhler
2016-11-20 21:28               ` Drew Adams [this message]
2016-11-21  6:48                 ` Andreas Röhler
2016-11-21 14:22                   ` Drew Adams
2016-11-21 13:09         ` Tino Calancha
2016-11-21 23:07           ` Drew Adams
2016-11-22  8:45             ` Andreas Röhler
2021-08-10 16:18 ` Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4b460e35-7e65-4224-a52b-083f87b24c70@default \
    --to=drew.adams@oracle.com \
    --cc=24969@debbugs.gnu.org \
    --cc=andreas.roehler@easy-emacs.de \
    --cc=npostavs@users.sourceforge.net \
    --cc=stephen.berman@gmx.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.