From: Michael Heerdegen <michael_heerdegen@web.de>
To: martin rudalics <rudalics@gmx.at>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: No docstring slot for pcase--make-docstring
Date: Wed, 06 Mar 2019 14:36:30 +0100 [thread overview]
Message-ID: <87r2bk2kgx.fsf@web.de> (raw)
In-Reply-To: <5C7F9547.6070306@gmx.at> (martin rudalics's message of "Wed, 06 Mar 2019 10:39:19 +0100")
martin rudalics <rudalics@gmx.at> writes:
> When building master I currently see
>
> Finding pointers to doc strings...
> No docstring slot for pcase--make-docstring
> Finding pointers to doc strings...done
>
> Is this something I should care about?
Stefan (CC'd) had added autoload cookies to achieve that C-h f pcase
looks sane when pcase.el had not yet been loaded. pcase--make-docstring
is now autoloaded, but it's an internal helper and don't has, and
probably don't needs, a docstring. Yet Emacs complains because it's
autoloaded.
Is something like
(put 'pcase 'function-documentation
'(progn (require 'pcase) (pcase--make-docstring)))
an alternative to autoloading `pcase--make-docstring'?
Michael.
next prev parent reply other threads:[~2019-03-06 13:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 9:39 No docstring slot for pcase--make-docstring martin rudalics
2019-03-06 13:36 ` Michael Heerdegen [this message]
2019-03-08 6:23 ` Stefan Monnier
2019-03-08 22:28 ` Stefan Monnier
2019-03-09 9:08 ` martin rudalics
2019-03-09 9:12 ` martin rudalics
2019-03-09 9:46 ` martin rudalics
2019-03-09 10:48 ` Eli Zaretskii
2019-03-09 13:15 ` martin rudalics
2019-03-09 15:10 ` Stefan Monnier
2019-03-10 8:46 ` martin rudalics
2019-03-10 17:22 ` Stefan Monnier
2019-03-11 9:14 ` martin rudalics
2019-03-11 12:01 ` Noam Postavsky
2019-04-23 9:14 ` martin rudalics
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=87r2bk2kgx.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rudalics@gmx.at \
/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).