From: "J.P." <jp@neverwas.me>
To: Lin Jian <jlin.dev@outlook.com>
Cc: 54343@debbugs.gnu.org
Subject: bug#54343: 28.0.91; find-function goes to a wrong place for erc
Date: Sat, 12 Mar 2022 00:27:25 -0800 [thread overview]
Message-ID: <87k0czbmoi.fsf@neverwas.me> (raw)
In-Reply-To: <87wnh0dnyr.fsf@neverwas.me> (J. P.'s message of "Fri, 11 Mar 2022 16:16:44 -0800")
"J.P." <jp@neverwas.me> writes:
> seems to work with emacs -Q. (That rx form is bogus, BTW; it doesn't
> retain the capture groups and probably has other bugs.)
You're probably way ahead of me here, but I thought it prudent to
reemphasize that evaluating that ugly demo expression is useless. If
trying to convince yourself that splicing in a "cl-" prefix may be
promising, please just modify the original `find-function-regexp' value
instead:
""^\\s-*(\\(\\(?:cl-\\)?def\\(ine-skeleton...."
^
FWIW, this one may be slightly less atrocious:
(let ((find-function-regexp
(rx bol
(* (syntax -))
"("
(group
(| (: (? "cl-")
"def"
(group
(| "ine-skeleton"
"ine-generic-mode"
"ine-derived-mode"
(: "ine" (? "-global") "-minor-mode")
"ine-compilation-mode"
"un-cvs-mode"
"foo"
(: (| (not (in "icfgv")) (: "g" (not ?r)))
(+ (group (| word (syntax symbol))))
(? ?*)))))
(: "easy-mmode-define-" (+ (in (?a . ?z) ?-)))
"easy-menu-define"
"menu-bar-make-toggle"
"menu-bar-make-toggle-command"))
(+ (| (syntax -) "\n" (: ";" (* nonl) "\n")))
(? (group (| ?' "(quote "))) "%s"
(group (| (syntax -) eol (in "()"))))))
(find-function 'erc))
next prev parent reply other threads:[~2022-03-12 8:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 19:57 bug#54343: 28.0.91; find-function goes to a wrong place for erc Lin Jian
2022-03-12 0:16 ` J.P.
2022-03-12 1:48 ` Michael Heerdegen
2022-03-12 3:59 ` F. Jason Park
2022-03-12 8:27 ` J.P. [this message]
2022-03-12 17:54 ` Lars Ingebrigtsen
2022-03-13 0:53 ` J.P.
2022-03-13 0:59 ` Lars Ingebrigtsen
2022-03-13 3:09 ` J.P.
2022-03-13 14:10 ` Lars Ingebrigtsen
2022-03-13 20:12 ` J.P.
2022-03-13 20:16 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0czbmoi.fsf@neverwas.me \
--to=jp@neverwas.me \
--cc=54343@debbugs.gnu.org \
--cc=jlin.dev@outlook.com \
/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 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).