[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#13824: 24.3.50; :package-version not taking priority over :version
From: |
Stefan Kangas |
Subject: |
bug#13824: 24.3.50; :package-version not taking priority over :version |
Date: |
Thu, 8 Aug 2019 05:59:21 +0200 |
Bastien Guerry <bzg@altern.org> writes:
> The docstring of `defcustom' says:
>
> :package-version
> VALUE should be a list with the form (PACKAGE . VERSION)
> specifying that the variable was first introduced, or its
> default value was changed, in PACKAGE version VERSION. This
> keyword takes priority over :version.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> but `describe-variable-custom-version-info' gives priority to :version
> over :package-version. Which one is correct here?
This is still an issue on current master (and 26.2).
I reproduced this using:
(progn
(defcustom foobar nil
"foo"
:version "27.1"
:package-version '(foo . "1"))
(describe-variable-custom-version-info 'foobar))
Which results in:
"This variable was introduced, or its default value was changed, in
version 27.1 of Emacs.
"
But C-h f defcustom says:
:package-version
VALUE should be a list with the form (PACKAGE . VERSION)
specifying that the variable was first introduced, or its
default value was changed, in PACKAGE version VERSION. This
keyword takes priority over :version.
Thanks,
Stefan Kangas
- bug#13824: 24.3.50; :package-version not taking priority over :version,
Stefan Kangas <=