bug#52593: 28.0.90; (thing-at-point thing) has so much overhead since commit 7db376e560448e61485ba054def8c82b21f33d6a

[Kang Niu <isgniuk@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 921 bytes --]

There are no fields in the buffer. (field-beginning) (field-end) return the
same value as (point-min) (point-max).

Lars Ingebrigtsen <larsi@gnus.org> 于2021年12月19日周日 21:35写道：

> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> The overhead disappears only if I comment out (narrow-to-region
> >> (field-beginning) (field-end)) in
> >> thing-at-point.
>
> Are there fields in the buffer you're using this in?  I.e., does
> (field-beginning) (field-end) return anything other than
> point-min/point-max?
>
> > Perhaps thing-at-point should acquire a new optional argument saying
> > "don't pay attention to fields"?
>
> If the buffer has fields, then I think thing-at-point should pay
> attention to them -- it's for stuff like this Emacs has fields in the
> first place.
>
> --
> (domestic pets only, the antidote for overdose, milk.)
>    bloggy blog: http://lars.ingebrigtsen.no
>

[-- Attachment #2: Type: text/html, Size: 1413 bytes --]