Binding `default-*-coding-system' to nil causes XEmacs 21.5.x to signal invalid-state
Stephen J. Turnbull
stephen at xemacs.org
Wed May 5 10:35:15 EDT 2004
GNU Emacs applications occasionally bind default-process-coding-system
to nil. For example, uudecode.el from Gnus does this. TRAMP's ssh
method will trigger this every time.
This causes XEmacs to get upset and signal `invalid-state', because we
test for that being a cons (src/process.c, l. 533).
Similar considerations apply to default-network-coding-system.
Do we really need to be this strict? If so, what's appropriate here?
(binary . binary)?
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
More information about the XEmacs-Beta