From: Philipp Stephani <p.stephani2@gmail.com>
To: npostavs@users.sourceforge.net
Cc: 23486@debbugs.gnu.org
Subject: bug#23486: 25.0.93; Modules: features missing from make_function
Date: Sun, 26 Mar 2017 20:40:00 +0000 [thread overview]
Message-ID: <CAArVCkRqv9oN__MadfpbWg-PDt5DbhBG7R48ZhnTLH7Eq_Mmkw@mail.gmail.com> (raw)
In-Reply-To: <877f3b4wl3.fsf@users.sourceforge.net>
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
<npostavs@users.sourceforge.net> schrieb am So., 26. März 2017 um 22:21 Uhr:
> Philipp Stephani <p.stephani2@gmail.com> writes:
>
> >
> >> I think adding "(fn ARG1 ARG2...)" to the docstring would solve
> (1)-(3).
> >
> > That doesn't work, because Emacs ignores this syntax when the
> > arguments are provided explicitly, and since a module function is just
> > a (lambda (&rest args) ...) under the hood, the arglist is always just
> > (&rest args).
>
> I don't know what you mean here.
>
> (defun foo (&rest args)
> "Do foo.
>
> \(fn ARG1 ARG2)")
>
> <f1> f foo RET gives
>
> foo is a Lisp function.
>
> (foo ARG1 ARG2)
>
> Do foo.
>
OK, that one works, but others don't (e.g. help-function-arglist). The
argument names should be transparent, without having to use such tricks.
[-- Attachment #2: Type: text/html, Size: 1773 bytes --]
next prev parent reply other threads:[~2017-03-26 20:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 16:37 bug#23486: 25.0.93; Modules: features missing from make_function Philipp Stephani
2016-09-11 14:13 ` Philipp Stephani
2016-09-11 14:57 ` npostavs
2017-03-26 20:02 ` Philipp Stephani
2017-03-26 20:22 ` npostavs
2017-03-26 20:40 ` Philipp Stephani [this message]
2017-03-27 3:57 ` npostavs
2017-07-04 18:20 ` Philipp Stephani
2017-07-05 3:40 ` npostavs
2020-09-05 13:59 ` Lars Ingebrigtsen
2020-09-13 9:44 ` Philipp Stephani
2020-09-13 13:20 ` Lars Ingebrigtsen
2020-09-13 18:50 ` Philipp Stephani
2020-12-07 16:42 ` Lars Ingebrigtsen
2020-12-12 14:31 ` Philipp Stephani
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=CAArVCkRqv9oN__MadfpbWg-PDt5DbhBG7R48ZhnTLH7Eq_Mmkw@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=23486@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
/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).