[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#15809: [External] : Re: bug#15809: 24.3.50; wrong defcustom type for
From: |
Stefan Kangas |
Subject: |
bug#15809: [External] : Re: bug#15809: 24.3.50; wrong defcustom type for `suggest-key-bindings' |
Date: |
Fri, 24 Sep 2021 19:25:56 -0700 |
Drew Adams <drew.adams@oracle.com> writes:
>> How about the attached?
>
> In some cases you say "must", in other cases you say "should".
This inconsistency is there in the documentation already, compare:
:type-error "This field should contain an integer"
With:
@item integer
The value must be an integer.
Sorting it out seems beyond the scope of this bug report. If we even
need to do anything about it.
> You could say that one can always assign an option a value
> that doesn't match its :type spec. So in practice, there's
> no solid enforcement of the law. Still, the law says the
> value must be a nonnegative integer, regardless of whether
> there are ways to escape enforcement. It's the law that
> gets written as the rule. ;-)
I basically agree, but we use "must" and "should" interchangeably all
over Emacs. In context, they mean more or less the same thing.
bug#15809: 24.3.50; wrong defcustom type for `suggest-key-bindings', Mattias Engdegård, 2021/09/25
bug#15809: 24.3.50; wrong defcustom type for `suggest-key-bindings', Mattias Engdegård, 2021/09/25
bug#15809: 24.3.50; wrong defcustom type for `suggest-key-bindings', Stefan Kangas, 2021/09/25
bug#15809: [External] : Re: bug#15809: 24.3.50; wrong defcustom type for `suggest-key-bindings', Drew Adams, 2021/09/25