Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!MIZAR.DOCS.UU.SE!perm From: perm@MIZAR.DOCS.UU.SE (Per Mildner) Newsgroups: gnu.emacs.bug Subject: next-complex-command gives wrong error msg Message-ID: <8911282205.AAmizar14157@mizar.DoCS.UU.SE> Date: 28 Nov 89 22:05:52 GMT Sender: daemon@tut.cis.ohio-state.edu Distribution: gnu Organization: GNUs Not Usenet Lines: 21 In GNU Emacs 18.53.8 of Sun Oct 29 1989 on mizar (berkeley-unix) next-complex-command signals an error as: (error (if (= repeat-complex-command-arg 1) ; should be (>= n 1) "No following item in command history" "No preceeding item command history")) ; missing 'in' The current test gives the wrong message if command-history has only one element. This must be one of the least important bugs in emacs :-) Sidenote 1: I found the above bug while implementing read-from-minibuffer-with-history which would be nice to have (in v.19?) together with modified versions of most functions that now prompt in the minibuffer (ie like ZMACS) Sidenote 2: Is there an elegant way to temporarily add a keydef to a keymap without changing it permanently. (with-keydef keymap "\en" 'next-in-history (read-from-minibuffer ... keymap)) Brought to you by Super Global Mega Corp .com