db@its63b.ed.ac.uk (D Berry) (05/16/88)
GNU emacs 18.51, SUNOS 3.2 Has anyone got the stuff in chistory.el to work? The function list-command-history prints the command history to a temporary buffer, then calls eobp to see if anything has been printed. However, it seems to do this in the wrong buffer - if you call list-command-history from an empty buffer it complains that there isn't a command history even if one exists! If I call list-command-history from a non-empty buffer I get a different error. It complains that (lambda (lisp-syntax) (<bytecode stuff>)) has the wrong number of arguments. At that point I gave up. -- ------------------------------------------------------------------------------- "England has become ... an intolerant, rascist, homophobic, narrow-minded authoritarian rat hole run by vicious suburban-minded materialistic philistines" -- Hanif Kureishi ------------------------------------------------------------------------------- Dave Berry. db%lfcs.ed.ac.uk@nss.cs.ucl.ac.uk
akhanna@bbn.com (Atul Khanna) (05/16/88)
>Has anyone got the stuff in chistory.el to work? The function >list-command-history prints the command history to a temporary buffer, >then calls eobp to see if anything has been printed. However, it >seems to do this in the wrong buffer - if you call list-command-history >from an empty buffer it complains that there isn't a command history >even if one exists! > >If I call list-command-history from a non-empty buffer I get a different >error. It complains that (lambda (lisp-syntax) (<bytecode stuff>)) has >the wrong number of arguments. At that point I gave up. In the definition of Command-history-setup (in chistory.el), replace the line (lisp-mode-variables) with (lisp-mode-variables emacs-lisp-mode-syntax-table). This works for me anyway. -------------------------------------------------------------------------- Atul C Khanna (akhanna@bbn.com) BBN Communications Corporation 50 Moulton Street Cambridge, MA 02238 .!{decvax, wjh12, ihnp4, harvard}!bbnccv!akhanna