make utf-8 default for Cygwin 1.7, rewrite init code determining default coding systems -------------------- ChangeLog entries follow: -------------------- lisp/ChangeLog addition: 2010-02-06 Ben Wing <ben@xemacs.org> * code-init.el: * code-init.el (set-eol-detection): * code-init.el (coding-system-current-system-configuration): * code-init.el (coding-system-default-configuration-table): New. * code-init.el (no-mule-no-eol-detection): * code-init.el (define-coding-system-default-configuration): New. * code-init.el (coding-system-variable-default-value-table): Removed. * code-init.el (no-mule-eol-detection): * code-init.el (coding-system-default-configuration-list): Removed. * code-init.el (coding-system-default-variable-list): * code-init.el (get-coding-system-variable): * code-init.el (set-coding-system-variable): * code-init.el (coding-system-variable-default-value): * code-init.el (reset-coding-categories-to-default): Significant clean-up, add Cygwin-UTF-8 support. 1. Shorten the names of the coding system variables to follow what used to be considered the "abbreviations": default-process-coding-system-read -> process-read default-process-coding-system-write -> process-write buffer-file-coding-system-for-read -> bfcs-for-read default-buffer-file-coding-system -> default-bfcs no-conversion-coding-system-mapping -> no-conv-cs 2. Instead of listing all the defaults in a big, strangely organized table, use a new function `define-coding-system-default-configuration' to define a particular configuration. This uses a hash table stored in `coding-system-default-configuration-table'. Rewrite `coding-system-variable-default-value' appropriately. 3. Rename configurations to eliminate `unix' from the name: unix-no-mule-no-eol-detection -> no-mule-no-eol-detection unix-no-mule-eol-detection -> no-mule-eol-detection unix-mule -> mule This is because these are really for all systems but Windows, not just Unix. 4. Add configuration `cygwin-utf-8', enabled when (featurep 'cygwin-use-utf-8). Uses `utf-8' for all defaults except for `bfcs-for-read', which is `undecided'.

This directory contains XEmacs' automated test suite.  The usual way
of running all the tests is running `make check' from the top-level
source directory.

The test suite is unfinished and it's still lacking some essential
features.  It is nevertheless recommended that you run the tests to
confirm that XEmacs behaves correctly.

If you want to run a specific test case, you can do it from the
command-line like this:

$ xemacs -batch -l test-harness.elc -f batch-test-emacs TEST-FILE

If something goes wrong, you can run the test suite interactively by
loading `test-harness.el' into a running XEmacs and typing
`M-x test-emacs-test-file RET <filename> RET'.  You will see a log of
passed and failed tests, which should allow you to investigate the
source of the error and ultimately fix the bug.

Adding a new test file is trivial: just create a new file here and it
will be run.  There is no need to byte-compile any of the files in
this directory -- the test-harness will take care of any necessary
byte-compilation.

Look at the existing test cases for the examples of coding test cases.
It all boils down to your imagination and judicious use of the macros
`Assert', `Check-Error', `Check-Error-Message', and `Check-Message'.