Re: c-tests.el test failure in 21.5
Malcolm Purvis wrote:
>>>>>"Vin" == Vin Shelton
<acs(a)xemacs.org> writes:
>>>>>
>>>>>
Vin> Does anyone else see this?
It's a long standing known problem with running the unit tests on a non-Mule
XEmacs and is related to EOL detection. Ben's the only one who understands
the code well enough to give a correct fix.
More information can be last thread that discussed it:
http://list-archive.xemacs.org/xemacs-beta/200411/msg00140.html
Malcolm
the cause of this test failure is simply that eol detection is not
always enabled. in particular, from code-init.el:
(defcustom eol-detection-enabled-p (or (featurep 'mule)
(memq system-type '(windows-nt
cygwin32))
(featurep 'unix-default-eol-detection))
"True if XEmacs automatically detects the EOL type when reading files.
Normally, this is always the case on Windows or when international (Mule)
support is compiled into this XEmacs. Otherwise, it is currently off by
default, but this may change. Don't set this; nothing will happen.
Instead,
use the Options menu or `set-eol-detection'."
:group 'encoding
:type 'boolean
;; upon initialization, we don't want the whole business of
;; set-eol-detection to be called. We will init everything appropriately
;; later in the same file, when reset-language-environment is called.
:initialize #'(lambda (var val)
(setq eol-detection-enabled-p (eval val)))
:set #'(lambda (var val)
(set-eol-detection val)
(setq eol-detection-enabled-p val)))
`unix-default-eol-detection' gets set by the appropriate configure option.
so either we disable this test when we have no eol detection, or we turn
on eol detection by default.
ben