all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65064-done@debbugs.gnu.org, Heime <heimeborgia@protonmail.com>,
	Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#65064: Macro definition using C-h f
Date: Sat, 2 Sep 2023 09:44:37 -0700	[thread overview]
Message-ID: <CADwFkmnQuNJrrz-AYVmSN1=AaguUGXyENZPkQZeCkFaQaHW=3g@mail.gmail.com> (raw)
In-Reply-To: <83leeqt0wg.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 05 Aug 2023 10:15:59 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> 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.

I'm therefore closing this bug report.





      parent reply	other threads:[~2023-09-02 16:44 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
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 [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADwFkmnQuNJrrz-AYVmSN1=AaguUGXyENZPkQZeCkFaQaHW=3g@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=65064-done@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.