Re: XEmacs Packages have been pre-released (2016-02-08-16)

Hi, On Wed, Mar 30, 2016 at 11:18 PM, Raymond Toy <toy.raymond(a)gmail.com&gt; wrote: The 1.98 cc-mode package. The below "fix" makes sure I don't run into issues with errors in looking-at in non-cc-mode buffers. Due to index out of bounds or wrong or missing RE. I don't care to debug it further if I don't run into it again. I added the following "check" for c-buffer-is-cc-mode. What I saw related to the fix is described above. Other issue follows. The issues with cc-mode I get are quire reproducible, except they do not manifest in a "fresh" process. So, for example when XEmacs can't eval t (yes, this happens, see backtrace below). If I restart a new process and start to edit a file, there are no issues; it only happens when I have a mixture of modes and/or buffers -- but seems consistently related to cc-mode or its dependencies. Can it be because the package is compiled with 21.5 and not 21.4? Is there an easy way to recompile the package? Or all packages? Backtrace, from trying to enter javascript mode, I just ran into before replying. Debugger entered--Lisp error: (void-variable t) eval(t) custom-initialize-reset(comint-input-ignoredups t) custom-declare-variable(comint-input-ignoredups t "*If non-nil, don't add input matching the last on the input ring.\nThis mirrors the optional behavior of bash.\n\nThis variable is buffer-local." :type boolean:group comint) load-internal("comint" nil t nil binary) load("comint" nil t nil) require(comint) byte-code("..." [require cc-mode comint] 2) load-internal("javascript-mode" nil nil nil binary) load("javascript-mode" nil nil nil) command-execute(javascript-mode t) execute-extended-command(nil) call-interactively(execute-extended-command) _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta