Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!gem.mps.ohio-state.edu!ginosko!uunet!hsi!aati!mlfarm!ron From: ron@mlfarm.UUCP (Ronald Florence) Newsgroups: comp.emacs Subject: broken help functions Message-ID: <290@mlfarm.UUCP> Date: 29 Aug 89 03:10:39 GMT Organization: Maple Lawn Farm, Stonington, CT Lines: 58 I would very much appreciate help with the following rather bizarre problem: We recently compiled a new version of GNU Emacs 18.50, running under Xenix 2.2.3 on an IBM ps2/80, and have begun to encounter intermittant strange behavior from the C-h functions. For example, sometimes if I enter "C-h b" with debug-on-error turned on, the command fails and the debugger backtrace comes up with Signalling: (wrong-type-argument sequencep boundp) describe-bindings() call-interactively(describe-bindings) Another time, I entered "C-h l" and got: Signalling: (wrong-type-argument sequencep t) substitute-command-keys("Type \\[delete-other-windows] to remove help window.") byte-code("..." [standard-output function t get-buffer-window funcall message substitute-command-keys one-window-p "Type \\[delete-other-windows] to remove help window." "Type \\[switch-to-buffer-other-window] RET to restore old contents of help window."] 6) print-help-return-message() byte-code("..." [standard-output nil t "*Help*" princ key-description recent-keys move-to-column 50 search-forward " " newline print-help-return-message] 10) view-lossage() * call-interactively(view-lossage) The elipses represent strings of 8-bit octal characters. If I do not have debug-on-error set, the minibuffer messages when the help functions fail are generally "Wrong type argument: sequencep, S" where "S" can be all sorts of lisp symbols. Frequently the message will include "#