GNU bug report logs - #23975
25.0.94: defcustom error message is wrong when :type field has a :match attribute

Previous Next

Package: emacs;

Reported by: rswgnu <at> gmail.com

Date: Wed, 13 Jul 2016 20:05:02 UTC

Severity: minor

Tags: fixed

Found in version 25.0.94

Fixed in version 28.1

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

Bug is archived. No further changes may be made.

Full log


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

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Mauro Aranda <maurooaranda <at> gmail.com>
Cc: rswgnu <at> gmail.com, 23975 <at> debbugs.gnu.org, Robert Weiner <rsw <at> gnu.org>
Subject: Re: 25.0.94: defcustom error message is wrong when :type field has
 a :match attribute
Date: Fri, 04 Sep 2020 14:12:44 +0200
Mauro Aranda <maurooaranda <at> gmail.com> writes:

> I wonder if we could just document the :type-error property.  So
> anybody that uses a custom :match function with additional checks can
> put there the information they like to show the user when something goes
> wrong.  So the defcustom posted would be something like:
>
> (defcustom bounded-num 999
>   "Positive, bounded number"
>   :type '(integer :match (lambda (widget value) (and (integerp value)
>                                                                                   (> value 0)
>                                                                                   (< value 1000)))
>                         :type-error "Value should be an integer between 0 and 1000"))
>
> That's easy, and would solve the main problem here.  WDYT?

I think that's a very good idea.

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




This bug report was last modified 4 years and 338 days ago.

Previous Next


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