GNU bug report logs - #15455
24.3.50; wrong defcustom :type for `confirm-kill-emacs'

Previous Next

Package: emacs;

Reported by: Drew Adams <drew.adams <at> oracle.com>

Date: Tue, 24 Sep 2013 15:15:02 UTC

Severity: normal

Found in version 24.3.50

Fixed in version 24.4

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 15455 in the body.
You can then email your comments to 15455 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#15455; Package emacs. (Tue, 24 Sep 2013 15:15:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Drew Adams <drew.adams <at> oracle.com>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Tue, 24 Sep 2013 15:15:03 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.3.50; wrong defcustom :type for `confirm-kill-emacs'
Date: Tue, 24 Sep 2013 08:13:39 -0700 (PDT)
The Value Menu in Customize wrongly give the user no way to specify an
arbitrary predicate, and wrongly gives the impression that the option
value must be one of the two predicates presented (or nil).

The :type spec should provide a third possibility for the menu: an
arbitrary function (which is used as a predicate).

That menu item's :tag should make clear that the function is used as
a predicate: nil means..., non-nil means....

In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
 of 2013-09-20 on LEG570
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --enable-checking 'CFLAGS=-O0 -g3' CPPFLAGS=-DGLYPH_DEBUG=1'




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#15455; Package emacs. (Tue, 24 Sep 2013 15:25:02 GMT) Full text and rfc822 format available.

Message #8 received at 15455 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: 15455 <at> debbugs.gnu.org
Subject: RE: bug#15455: 24.3.50; wrong defcustom :type for `confirm-kill-emacs'
Date: Tue, 24 Sep 2013 08:24:12 -0700 (PDT)
Also, the doc should not just say that the predicate "should be a
predicate function such as `yes-or-no-p'. That is confusing and not
very meaningful.  What does it mean to be a predicate "such as
`yes-or-no-p'?

It should say that it is a function that is used as a predicate.
It should say what true and false return values mean (what they do).
And it should say that the function must accept at least one argument.




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#15455; Package emacs. (Mon, 10 Feb 2014 04:24:02 GMT) Full text and rfc822 format available.

Message #11 received at 15455 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 15455 <at> debbugs.gnu.org
Subject: Re: bug#15455: 24.3.50; wrong defcustom :type for `confirm-kill-emacs'
Date: Sun, 09 Feb 2014 20:21:54 -0800
Drew Adams <drew.adams <at> oracle.com> writes:

> Also, the doc should not just say that the predicate "should be a
> predicate function such as `yes-or-no-p'. That is confusing and not
> very meaningful.  What does it mean to be a predicate "such as
> `yes-or-no-p'?

I think examples like that can be helpful, especially with variables
like `confirm-kill-emacs' that non-experienced Emacs users happen upon.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#15455; Package emacs. (Mon, 10 Feb 2014 04:29:01 GMT) Full text and rfc822 format available.

Message #14 received at 15455 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 15455 <at> debbugs.gnu.org
Subject: Re: bug#15455: 24.3.50; wrong defcustom :type for `confirm-kill-emacs'
Date: Sun, 09 Feb 2014 20:26:36 -0800
Drew Adams <drew.adams <at> oracle.com> writes:

> The Value Menu in Customize wrongly give the user no way to specify an
> arbitrary predicate, and wrongly gives the impression that the option
> value must be one of the two predicates presented (or nil).
>
> The :type spec should provide a third possibility for the menu: an
> arbitrary function (which is used as a predicate).

Fixed on trunk.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/




bug marked as fixed in version 24.4, send any further explanations to 15455 <at> debbugs.gnu.org and Drew Adams <drew.adams <at> oracle.com> Request was from Lars Ingebrigtsen <larsi <at> gnus.org> to control <at> debbugs.gnu.org. (Mon, 10 Feb 2014 04:29:02 GMT) Full text and rfc822 format available.

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#15455; Package emacs. (Mon, 10 Feb 2014 06:01:02 GMT) Full text and rfc822 format available.

Message #19 received at 15455 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 15455 <at> debbugs.gnu.org
Subject: RE: bug#15455: 24.3.50; wrong defcustom :type for `confirm-kill-emacs'
Date: Sun, 9 Feb 2014 22:00:28 -0800 (PST)
> > Also, the doc should not just say that the predicate "should be a
> > predicate function such as `yes-or-no-p'. That is confusing and
> > not very meaningful.  What does it mean to be a predicate "such as
> > `yes-or-no-p'?
> 
> I think examples like that can be helpful, especially with variables
> like `confirm-kill-emacs' that non-experienced Emacs users happen
> upon.

I think what you are suggesting is to correct the language to
say

"If non-nil the value should be a predicate, for example
`yes-or-no-p'."

That would be fine.  The point is that the current language says
that it not only should be a predicate, but a predicate of a
certain kind, namely in some unspecified way similar to
`yes-or-no-p'.  But that is not the case.  The predicate can
check the phase of the moon if you want.




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#15455; Package emacs. (Mon, 10 Feb 2014 06:10:01 GMT) Full text and rfc822 format available.

Message #22 received at 15455 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 15455 <at> debbugs.gnu.org
Subject: Re: bug#15455: 24.3.50; wrong defcustom :type for `confirm-kill-emacs'
Date: Sun, 09 Feb 2014 22:07:50 -0800
Drew Adams <drew.adams <at> oracle.com> writes:

> I think what you are suggesting is to correct the language to
> say
>
> "If non-nil the value should be a predicate, for example
> `yes-or-no-p'."

Yeah, that's better.  Fixed on trunk.
-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Mon, 10 Mar 2014 11:24:12 GMT) Full text and rfc822 format available.

This bug report was last modified 10 years and 61 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.