From: Stefan Kangas <stefankangas@gmail.com>
To: Michelangelo Rodriguez <michelangelo.rodriguez@gmail.com>,
emacs-devel@gnu.org
Subject: Re: documentation incorrect for function `define-package'?
Date: Fri, 24 Sep 2021 08:01:14 -0700 [thread overview]
Message-ID: <CADwFkm=CGvD-B2Sp5RwJti5caTpH7uRjMvwP3Qr6JrjuuLMZUw@mail.gmail.com> (raw)
In-Reply-To: <87bl4iukia.fsf@gmail.com>
Michelangelo Rodriguez <michelangelo.rodriguez@gmail.com> writes:
> The documentation for `define-package' function says:
> EXTRA-PROPERTIES is currently unused.
> But, indeed, it's not true.
> In order for a multi-package to correctly work, and in particular to
> `describe-package' to report correctly information on a multi-package,
> it is necessary to specify keywords as :author, :keywords, and so on...
> Neither function documentation nor info manual mention that.
> Infact, if i specify only library headers containing that information,
> describe-package don't report keywords, nor other tags.
This is its current definition:
(defun define-package ( _name-string _version-string
&optional _docstring _requirements
&rest _extra-properties)
"Define a new package.
NAME-STRING is the name of the package, as a string.
VERSION-STRING is the version of the package, as a string.
DOCSTRING is a short description of the package, a string.
REQUIREMENTS is a list of dependencies on other packages.
Each requirement is of the form (OTHER-PACKAGE OTHER-VERSION),
where OTHER-VERSION is a string.
EXTRA-PROPERTIES is currently unused."
;; FIXME: Placeholder! Should we keep it?
(error "Don't call me!"))
On the one hand, this function is clearly not intended for use.
On the other hand, where else do we document the `define-package' list
that goes in "foo-pkg.el"?
Those definitions look like this, but again this is just data (the
"package.el" Commentary section incorrectly says "'PACKAGE-pkg.el' which
consists of a *call* to define-package", my emphasis):
(define-package "which-key" "20210824.11" "Display available
keybindings in popup" '((emacs "24.4")) :commit
"4790a14683a2f3e4f72ade197c78e4c0af1cdd4b" :authors '(("Justin
Burkett" . "justin@burkett.cc")) :maintainer '("Justin Burkett" .
"justin@burkett.cc") :url
"https://github.com/justbur/emacs-which-key")
next prev parent reply other threads:[~2021-09-24 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 14:16 documentation incorrect for function `define-package'? Michelangelo Rodriguez
2021-09-24 15:01 ` Stefan Kangas [this message]
2021-09-25 18:13 ` Michelangelo Rodriguez
2021-09-25 18:51 ` Stefan Kangas
2021-09-25 21:48 ` Michelangelo Rodriguez
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='CADwFkm=CGvD-B2Sp5RwJti5caTpH7uRjMvwP3Qr6JrjuuLMZUw@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=michelangelo.rodriguez@gmail.com \
/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).