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

[Katsumi Yamaoka <yamaoka@jpl.org>]

>>>>> "Lennart Borgman (gmail)" <lennart.borgman@gmail.com> wrote:

> But is this really the right fix? It looks to me like there is a more
> general bug in customize, please see the message I sent after the one
> you responded to hear.

I see.  Thanks.  I guess the reason the `coding-system' widget
doesn't check whether the value is a coding system is for the
coding systems that are defined afterward, e.g., the ones to be
autoloaded.  So, I think the right fix is to check whether the
value is not a function.  A new patch is below.  WDYT?

*** cus-start.el~	Tue Jul  3 14:41:31 2007
--- cus-start.el	Sat Jul  7 01:41:21 2007
***************
*** 122,129 ****
  				  :value (undecided . undecided)
  				  (coding-system :tag "Decoding")
  				  (coding-system :tag "Encoding"))
! 			    (coding-system :tag "Single coding system"
! 					   :value undecided)
  			    (function :value ignore))))
  	     (selection-coding-system mule coding-system)
  	     ;; dired.c
--- 122,134 ----
  				  :value (undecided . undecided)
  				  (coding-system :tag "Decoding")
  				  (coding-system :tag "Encoding"))
! 			    (coding-system
! 			     :tag "Single coding system"
! 			     :value undecided
! 			     :match (lambda (widget value)
! 				      (and value
! 					   (symbolp value)
! 					   (not (functionp value)))))
  			    (function :value ignore))))
  	     (selection-coding-system mule coding-system)
  	     ;; dired.c

P.S. I'm sorry I'm inactive in the net every weekend.