Hi emacs-windowsers, Sometimes when I try to save with C-x C-s (and also manually with M-x save-buffer), I get an error the following error in the minibuffer:
(wrong-type-argument number-or-marker-p nil) With the debugger enabled, I get the following: Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil) min(nil nil) apply(min (nil nil)) select-safe-coding-system-interactively(1 1706 (gb2312 shift_jis iso-2022-jp utf-8 euc-kr euc-jis-2004 euc-jp euc-tw windows-1258 cp874 iso-2022-jp-2004 windows-1255 cp869 windows-1253 iso-8859-7 adobe-standard-encoding next mac-roman windows-1257 windows-1254 windows-1252 windows-1250 iso-8859-13 windows-1251 koi8-t gb18030 gbk big5-hkscs big5 hz-gb-2312 utf-7 iso-2022-kr iso-2022-jp-2 iso-2022-cn-ext iso-2022-cn 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 iso-2022-7bit-lock eucjp-ms georgian-academy ...) (undecided-dos iso-latin-1-dos) nil chinese-iso-8bit) select-safe-coding-system(1 1706 undecided-dos nil "c:/jroes/work.org") write-region(nil nil "c:/jroes/work.org" nil t "c:/jroes/work.org") basic-save-buffer-2() basic-save-buffer-1() basic-save-buffer() save-buffer(1) call-interactively(save-buffer nil nil) I haven't been able to pinpoint an exact sequence of steps or quite yet, but this happens frequently enough to really give me problems working. I'm using the patched 20080602 EmacsW32 build from the EmacsW32 site. Anyone else running into this problem and/or have a fix? Jonathan Roes
