From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 17623@debbugs.gnu.org
Subject: bug#17623: 24.4.50; incorrect example for `apply-partially' in (elisp) `Calling Functions'
Date: Sat, 28 Jun 2014 19:55:10 +0300 [thread overview]
Message-ID: <8338ep6kk1.fsf@gnu.org> (raw)
In-Reply-To: <87tx75ni8k.fsf@web.de>
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Date: Sat, 28 Jun 2014 17:53:15 +0200
> Cc: 17623@debbugs.gnu.org
>
> BTW, the second sentence here from (info "(elisp) Calling Functions") is
> confusing too wrt what it says about arguments.
>
> ,----------------------------------------------------------------------
> | The act of fixing some of the function’s arguments is
> | called "partial application" of the function(1). The result is a new
> | function that accepts the rest of arguments and calls the original
> | function with all the arguments combined.
> `----------------------------------------------------------------------
>
> IMHO we should be more clearer about arguments, but then we can keep the
> 1+ example. I think it would be more important to say that
> `apply-partially` is most useful in combination with functionals, as it
> is explained later on that info page. That the result accepts any
> number of arguments is more kind of an implementation detail.
Sorry, I don't understand this critique. Perhaps if you suggested an
alternative wording, it would become clear what is it that confused
you about the current text.
Thanks.
next prev parent reply other threads:[~2014-06-28 16:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 23:53 bug#17623: 24.4.50; incorrect example for `apply-partially' in (elisp) `Calling Functions' Drew Adams
2014-06-27 18:41 ` Michael Heerdegen
2014-06-28 1:36 ` Drew Adams
2014-06-28 15:53 ` Michael Heerdegen
2014-06-28 16:55 ` Eli Zaretskii [this message]
2014-06-28 17:53 ` Michael Heerdegen
2014-06-28 18:45 ` Eli Zaretskii
2014-06-28 19:37 ` Michael Heerdegen
2014-06-29 14:57 ` Eli Zaretskii
2021-10-23 5:24 ` Stefan Kangas
2021-10-23 9:44 ` Michael Heerdegen
2021-10-23 11:05 ` Stefan Kangas
2021-10-23 11:58 ` Michael Heerdegen
2021-10-23 11:39 ` Eli Zaretskii
2021-10-23 12:44 ` Michael Heerdegen
2021-10-23 13:13 ` Eli Zaretskii
2021-10-23 15:29 ` Michael Heerdegen
2021-10-23 17:01 ` Stefan Kangas
2021-10-26 9:26 ` Michael Heerdegen
2021-10-26 20:24 ` Stefan Kangas
2021-10-27 9:18 ` Michael Heerdegen
2021-10-29 4:02 ` Richard Stallman
2021-10-29 10:00 ` Michael Heerdegen
2021-10-23 17:54 ` Eli Zaretskii
2021-10-23 13:14 ` Stefan Kangas
2021-10-23 15:38 ` Michael Heerdegen
2021-10-23 17:57 ` Eli Zaretskii
[not found] ` <<83tx746fgd.fsf@gnu.org>
2014-06-28 19:32 ` Drew Adams
2014-06-29 21:46 ` Stefan Monnier
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=8338ep6kk1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17623@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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.