From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Gildea <stepheng+emacs@gildea.com>
Cc: emacs-devel@gnu.org
Subject: Re: a property "definition-type" would help find macro-defined tests
Date: Wed, 08 Jan 2025 14:31:36 +0200 [thread overview]
Message-ID: <86bjwh4hcn.fsf@gnu.org> (raw)
In-Reply-To: <234754.1736288018@pental.sg.gildea.net> (message from Stephen Gildea on Tue, 07 Jan 2025 14:13:38 -0800)
> From: Stephen Gildea <stepheng+emacs@gildea.com>
> Date: Tue, 07 Jan 2025 14:13:38 -0800
>
> In the two weeks since posting the proposal for a new property
> "definition-type" (find-function-search-for-symbol would use
> it instead of the passed-in type to find a definition), I have
> received only one response, an enthusiastic "yes, please!"
>
> So unless I hear any objections now, I will go ahead and add this feature.
>
> In addition to the small code and doc-string changes to
> find-function-search-for-symbol, I will expand the Emacs Lisp
> manual's documentation of definition-name in node "Standard
> Properties" to include definition-type. I will also mention
> definition-type, with cross reference, in "defining functions
> dynamically" and, in the ERT manual, in "How to Write Tests".
Please post the full patch before you install it. Your original
message only shows a very small part of the tip of this particular
iceberg, which makes it hard to provide useful feedback.
Thanks.
next prev parent reply other threads:[~2025-01-08 12:31 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-21 16:53 a property "definition-type" would help find macro-defined tests Stephen Gildea
2024-12-22 17:12 ` Richard Lawrence
2025-01-07 22:13 ` Stephen Gildea
2025-01-08 12:31 ` Eli Zaretskii [this message]
2025-01-08 17:44 ` Stephen Gildea
2025-01-09 6:57 ` Eli Zaretskii
2025-01-10 4:47 ` Stephen Gildea
2025-01-10 7:08 ` Eli Zaretskii
2025-01-11 19:43 ` Stephen Gildea
2025-01-12 5:32 ` Eli Zaretskii
2025-01-12 17:06 ` Stephen Gildea
2025-01-12 18:38 ` Eli Zaretskii
2025-01-13 4:44 ` Stephen Gildea
2025-01-13 9:03 ` Eshel Yaron
2025-01-13 21:34 ` Stephen Gildea
2025-01-14 7:21 ` Eshel Yaron
2025-01-15 3:14 ` Stephen Gildea
2025-01-15 7:30 ` Eshel Yaron
2025-01-15 21:17 ` Stephen Gildea
2025-01-16 6:20 ` Eli Zaretskii
2025-01-16 14:47 ` Stephen Gildea
2025-01-16 23:45 ` Stephen Gildea
2025-01-17 7:17 ` Eli Zaretskii
2025-01-22 5:27 ` Stephen Gildea
2025-01-22 14:18 ` Eli Zaretskii
2025-01-23 3:16 ` Stephen Gildea
2025-01-23 8:05 ` Eli Zaretskii
2025-01-23 17:14 ` Stephen Gildea
2025-01-23 17:44 ` Eli Zaretskii
2025-01-23 21:52 ` Stephen Gildea
2025-01-15 14:34 ` Eli Zaretskii
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=86bjwh4hcn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stepheng+emacs@gildea.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).