bug#21391: 24.5; `thing-at-point' returns error when called with arguments 'number t)

[Drew Adams]

> >>> `thing-at-point' should always return a string.
> >>
> >> Indeed. Which would require some normalization WRT number-at-
> >> point etc.
> >
> > `number-at-point' uses `form-at-point'.  It returns a number (or
> > nil), not a numeral (string).  It satisfies `numberp', not `stringp'.
> >
> > What normalization do you have in mind?
> 
> Still think detecting buffer-substrings according to THING and
> returning them if found at  point --nil otherwise-- is most
> straightforward.

Sorry, but I don't follow you.  Just what are you proposing?

> >>> `list-at-point', `form-at-point', etc. are a different
> >>> story - they can return anything.
> >>
> >> Interesting question. Maybe returns the symbol if found - nil
> >> otherwise?
> >
> > That's what `symbol-at-point' does.
> 
> Unfortunately it does more - it might change the symbol-table.
> Expect a passive, plain report instead.

I don't understand.  Please specify what you are proposing (maybe
in a different bug report, if that is more appropriate).