Re: Bad value in file-coding-system-alist

[Katsumi Yamaoka <yamaoka@jpl.org>]

>>>>> Lennart Borgman (gmail) wrote:

> Are you sure this is the right fix? Is not this a general problem with
> Custom?

>> *** cus-start.el~	Thu Apr 12 03:05:31 2007
>> --- cus-start.el	Mon Jul  9 01:33:47 2007

[...]

>> ! 			    (coding-system
>> ! 			     :tag "Single coding system"
>> ! 			     :value undecided
>> ! 			     :match (lambda (widget value)
>> ! 				      (and value (not (functionp value)))))

Do you think the `coding-system' widget defined in wid-edit.el
should test whether the value is a coding system?  If so, is it
really harmless?  If it is done, we cannot use a coding system
that is defined afterward for the default value of an option for
example.  Eval the following form and try customizing the
`foo-coding-system' variable.

--8<---------------cut here---------------start------------->8---
(require 'wid-edit)

(plist-put (cdr (get 'coding-system 'widget-type))
	   :match (lambda (widget value) (coding-system-p value)))

(defcustom foo-coding-system 'bar
  "doc"
  :type 'coding-system)
--8<---------------cut here---------------end--------------->8---

You will see that the value appears with the sexp form because
of the `mismatch' error.  I think restricting too much is not a
good idea.  Or is this not what you'd like to say?