From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 33428-done@debbugs.gnu.org
Subject: bug#33428: 27.0.50; edebug-print-{length,level} customization types
Date: Mon, 19 Nov 2018 23:16:59 +0100 [thread overview]
Message-ID: <874lccd86c.fsf@rub.de> (raw)
In-Reply-To: <878t1od892.fsf@rub.de> (Stephen Berman's message of "Mon, 19 Nov 2018 23:15:21 +0100")
On Mon, 19 Nov 2018 23:15:21 +0100 Stephen Berman <stephen.berman@gmx.net> wrote:
> On Mon, 19 Nov 2018 20:37:05 +0200 Eli Zaretskii <eliz@gnu.org> wrote:
>
>>> From: Stephen Berman <stephen.berman@gmx.net>
>>> Date: Mon, 19 Nov 2018 11:32:51 +0100
>>>
>>> The doc strings of edebug-print-length and edebug-print-level imply that
>>> nil is a valid value and indeed it is. Yet trying to set the value to
>>> nil via `M-x customize-option' fails with the error "This field should
>>> contain an integer", because nil does not fit the customization type
>>> :integer used in the definitions of these user options. It's been like
>>> this since they were changed from defvars to defcustoms more than 20
>>> years ago (though "If non-nil" was added to the doc strings only a
>>> little less than 10 years ago), so should the fix (below) go into
>>> master, or is it on the order of a documentation fix and suitable for
>>> the release branch?
>>
>> It's fine with me to put this on the release branch.
>>
>> Thanks.
>
> Done in commit d667318a7f.
>
> Steve Berman
Oops, and closing the bug.
prev parent reply other threads:[~2018-11-19 22:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 10:32 bug#33428: 27.0.50; edebug-print-{length,level} customization types Stephen Berman
2018-11-19 18:37 ` Eli Zaretskii
2018-11-19 22:15 ` Stephen Berman
2018-11-19 22:16 ` Stephen Berman [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874lccd86c.fsf@rub.de \
--to=stephen.berman@gmx.net \
--cc=33428-done@debbugs.gnu.org \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.