GNU bug report logs -
#6187
23.1; can't save: "Wrong type argument: number-of-marker-p, nil"
Previous Next
Reported by: Ryo Furue <furue <at> hawaii.edu>
Date: Fri, 14 May 2010 06:22:02 UTC
Severity: normal
Merged with 5948
Found in version 23.1
Done: Chong Yidong <cyd <at> stupidchicken.com>
Bug is archived. No further changes may be made.
Full log
Message #20 received at 6187 <at> debbugs.gnu.org (full text, mbox):
Hi,
I'm writing this without understanding what is wrong, so I apologize
if this is off the point.
| > ;>>>> BEGIN BACK TRACE >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
| > Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
| > min(nil)
| > apply(min nil)
| > select-safe-coding-system-interactively(1 1362 (utf-8
| > adobe-standard-encoding next mac-roman gb18030 utf-7 utf-16
| > utf-16be-with-signature utf-16le-with-signature utf-16be utf-16le
| > x-ctext iso-2022-7bit utf-8-auto utf-8-with-signature emacs-mule
| > raw-text iso-2022-8bit-ss2 utf-7-imap utf-8-emacs no-conversion
| > compound-text-with-extensions ctext-no-compositions
| > iso-2022-7bit-lock iso-2022-7bit-ss2) (japanese-iso-8bit-unix) nil
| > utf-8)
|
| This is pretty strange. The code in question is
|
| (when (and unsafe (not (stringp from)))
| (pop-to-buffer bufname)
| (goto-char (apply 'min (mapcar #'(lambda (x) (car (cadr x)))
| unsafe))))
|
| If `unsafe' is an empty list, it should not have passed the `and'
| conditional.
Right after I got the error, I did "M-x describe-variable unsafe"
and obtained:
unsafe's value is
((japanese-iso-8bit-unix))
Documentation:
Not documented as a variable.
Is this of some interest?
Regards,
Ryo
This bug report was last modified 12 years and 235 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.