When app-emacs/table is installed, a copy of table.el is installed in /usr/share/emacs/site-lisp/table, referred to by /usr/share/emacs/site-lisp/site-gentoo.el, and caused to be loaded if the user activates the use of site-gentoo.el in the init file (~/.emacs.el). This version of table.el is incompatible with cvs emacs's native table.el, /usr/share/emacs/23.0.0/lisp/textmodes/table.el Starting emacs-23 or opening a file causes an error: > Wrong type argument: integerp, (48 . 57) > or other numbers, like: > map-char-table: Wrong type argument: integerp, (127 . 127) When I enabled debug on advice from emacs help list, this was observed in the error messages: table--deep-copy-rebind-keymap((keymap #^[nil nil keymap #^^[3 0 mark-sexp A comment was elicited, that Looks like you have an old table.el in your load-path. The table.el file included in Emacs's CVS trunk has no such function. Removing app-emacs/table resolves this problem with emacs-23, as of 29 August 2007. Other versions, emacs-21, emacs-22, and emacs-22-cvs are also installed on this system, and all work fine with app-emacs/table installed. Reproducible: Always Steps to Reproduce: 1. Install emacs-cvs (23) 2. Start emacs 3. Also opening a file 4. Actual Results: : message is found in minibuffer on startup. , these messages may be received when trying to open a file. HOwever, the second time the file attempted, it opens with no complaint. Expected Results: No error message The error was narrowed down to the presence of table.el in /usr/share/emacs/site-lisp/table, called by site-gentoo.el, that is incompatible with CVS emacs.
Please specify for which version (including revision!) of app-emacs/table you have installed, and reopen then.
(In reply to comment #1) > Please specify for which version (including revision!) of app-emacs/table you > have installed, and reopen then. > app-emacs/table-1.5.54-r1
Please try if this is still an issue for table-1.5.54-r2.
(In reply to comment #3) > Please try if this is still an issue for table-1.5.54-r2. > This problem has been SOLVED. Thank you.
Anyway, thanks for reporting.
