unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 17623@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#17623: 24.4.50; incorrect example for `apply-partially' in (elisp) `Calling Functions'
Date: Tue, 26 Oct 2021 22:24:38 +0200	[thread overview]
Message-ID: <CADwFkmkgQFhYudVNy1D1vDo4i=rQABWPXnv4moGdACAca=c2kQ@mail.gmail.com> (raw)
In-Reply-To: <87wnm0i1cc.fsf@web.de>

Michael Heerdegen <michael_heerdegen@web.de> writes:

> When reading again, I wondered if we should convert that whole manual
> page to use function quoting.  E.g.
>
>   (apply-partially '+ 1) ~> (apply-partially #'+ 1)
>
> The same problem exists for a few other pages.  Should I make a separate
> report about this?

I don't have a strong opinion either way.

I think what could be better documented are the benefits of quoting with
function (or #').  AFAICT, it is not really explained on (info "(elisp)
Anonymous Functions"), it is more hinted at.





  reply	other threads:[~2021-10-26 20:24 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
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 [this message]
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

  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='CADwFkmkgQFhYudVNy1D1vDo4i=rQABWPXnv4moGdACAca=c2kQ@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=17623@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    --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).