From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: No docstring slot for pcase--make-docstring
Date: Fri, 08 Mar 2019 01:23:35 -0500 [thread overview]
Message-ID: <jwvftrx3ndb.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 87r2bk2kgx.fsf@web.de
>> Finding pointers to doc strings...
>> No docstring slot for pcase--make-docstring
>> Finding pointers to doc strings...done
I wonder why we get this message. AFAICT this message comes from
Snarf-documentation, but since pcase--make-docstring doesn't have
a docstring, it shouldn't appear in etc/DOC and hence shouldn't be
touched by Snarf-documentation.
...Oh, I see that the autoload does have a "dummy" docstring providing
the name of the arguments (tho here there are none, so it's really
silly) and for that reason pcase--make-docstring does appear in etc/DOC.
> (put 'pcase 'function-documentation
> '(progn (require 'pcase) (pcase--make-docstring)))
The warning is definitely harmless here (especially since AFAICT it only
appears when dumping `bootstrap-emacs` and not for the real `emacs`), so
this is not needed. Maybe we should fix the autoload to not have
a docstring, OTOH? Or maybe we shouldn't bother to Snarf-documentation
for bootstrap-emacs?
Stefan
next prev parent reply other threads:[~2019-03-08 6:23 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
2019-03-08 6:23 ` Stefan Monnier [this message]
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=jwvftrx3ndb.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
/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).