* bug#32016: 27.0; (elisp) `Imenu'
[not found] ` <<83d0vzjsll.fsf@gnu.org>
@ 2018-07-07 14:34 ` Drew Adams
0 siblings, 0 replies; 3+ messages in thread
From: Drew Adams @ 2018-07-07 14:34 UTC (permalink / raw)
To: Eli Zaretskii, Drew Adams; +Cc: 32016-done
> > The description of `imenu-generic-expression' is incomplete. It does
> > not specify the case where argument REGEXP is a function...
>
> Thanks, I fixed the doc string.
Thanks.
> > But this bug report is about the missing description of the
> > REGEXP-as-function case.
>
> What is this about? A left-over of editing some other message?
No; it refers to the introductory sentences (quoted above)
and the description of the bug, which is about the doc not
specifying the case where REGEXP is a function.
It appears after an aside mention that the sentence about
the unclear sentence about "find another element". I didn't
want the bug about missing spec of REGEXP as a function to
be side-tracked by the parenthetical mention of some unclear
text that is not related to that.
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#32016: 27.0; (elisp) `Imenu'
@ 2018-06-30 6:42 Drew Adams
2018-07-07 9:35 ` Eli Zaretskii
0 siblings, 1 reply; 3+ messages in thread
From: Drew Adams @ 2018-06-30 6:42 UTC (permalink / raw)
To: 32016
The description of `imenu-generic-expression' is incomplete. It does
not specify the case where argument REGEXP is a function.
The doc string describes this use case this way:
REGEXP may also be a function, called without arguments. It is expected
to search backwards. It must return true and set 'match-data' if it
finds another element.
Unfortunately, the last sentence there is unclear. The function does
not "find another element". It finds a definition construct in the
buffer, and it sets match data for it. It does not construct or "find"
an element of the list that is the variable value.
But this bug report is about the missing description of the
REGEXP-as-function case.
In GNU Emacs 27.0.50 (build 3, x86_64-w64-mingw32)
of 2018-03-21
Repository revision: e70d0c9e66d7a8609450b2889869d16aeb0363b5
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --without-dbus --host=x86_64-w64-mingw32
--without-compress-install -C 'CFLAGS=-O2 -static -g3''
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#32016: 27.0; (elisp) `Imenu'
2018-06-30 6:42 Drew Adams
@ 2018-07-07 9:35 ` Eli Zaretskii
0 siblings, 0 replies; 3+ messages in thread
From: Eli Zaretskii @ 2018-07-07 9:35 UTC (permalink / raw)
To: Drew Adams; +Cc: 32016-done
> Date: Fri, 29 Jun 2018 23:42:02 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
>
> The description of `imenu-generic-expression' is incomplete. It does
> not specify the case where argument REGEXP is a function.
>
> The doc string describes this use case this way:
>
> REGEXP may also be a function, called without arguments. It is expected
> to search backwards. It must return true and set 'match-data' if it
> finds another element.
>
> Unfortunately, the last sentence there is unclear. The function does
> not "find another element". It finds a definition construct in the
> buffer, and it sets match data for it. It does not construct or "find"
> an element of the list that is the variable value.
Thanks, I fixed the doc string.
> But this bug report is about the missing description of the
> REGEXP-as-function case.
What is this about? A left-over of editing some other message?
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-07-07 14:34 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <<4f6216dc-d39a-42a1-a21b-c6ea8650e6a4@default>
[not found] ` <<83d0vzjsll.fsf@gnu.org>
2018-07-07 14:34 ` bug#32016: 27.0; (elisp) `Imenu' Drew Adams
2018-06-30 6:42 Drew Adams
2018-07-07 9:35 ` Eli Zaretskii
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).