unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Heime via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65064@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#65064: Macro definition using C-h f
Date: Sat, 05 Aug 2023 07:39:04 +0000	[thread overview]
Message-ID: <PaBBKTPlEQry5i2wi7_DXrmUOtsG3ZFzGChl__X65npK4ebFHIw68WF3vN3cjQVWJNaqLV_61YFLO2ny1WJAvj7i38NV0L0FN3KKtF-_fX4=@protonmail.com> (raw)
In-Reply-To: <83leeqt0wg.fsf@gnu.org>


------- Original Message -------
On Saturday, August 5th, 2023 at 7:15 PM, Eli Zaretskii <eliz@gnu.org> wrote:


> tags 65064 notabug
> thanks
> 
> > Date: Sat, 05 Aug 2023 06:42:57 +0000
> > From: Heime via "Bug reports for GNU Emacs,
> > the Swiss army knife of text editors" bug-gnu-emacs@gnu.org
> > 
> > Have done the following macro, but calling `C-h f tak` shows the definition
> > as
> > 
> > (tak &rest ARGS)
> > 
> > rather than
> > 
> > (tak &rest _ARGS)
> > 
> > (defmacro tak (&rest _args)
> > "Performs no action, no matter how many arguments are passed."
> > 
> > nil)
> 
> 
> This is a feature: the leading '_' is an indication that the argument
> is unused, but the argument's name is 'args', without the underscore.
> 
> This is not a bug.

Don't you need to show users that the argument is unused?






  reply	other threads:[~2023-08-05  7:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-05  6:42 bug#65064: Macro definition using C-h f Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-05  7:15 ` Eli Zaretskii
2023-08-05  7:39   ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-08-09 12:53     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-02 16:44   ` Stefan Kangas

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='PaBBKTPlEQry5i2wi7_DXrmUOtsG3ZFzGChl__X65npK4ebFHIw68WF3vN3cjQVWJNaqLV_61YFLO2ny1WJAvj7i38NV0L0FN3KKtF-_fX4=@protonmail.com' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=65064@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=heimeborgia@protonmail.com \
    --cc=monnier@iro.umontreal.ca \
    /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).