perm@MIZAR.DOCS.UU.SE (Per Mildner) (11/29/89)
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))
gildea@ALEXANDER.BBN.COM (Stephen Gildea) (11/29/89)
Date: Tue, 28 Nov 89 23:05:52 +0100
From: Per Mildner <perm@mizar.docs.uu.se>
To: bug-gnu-emacs@prep.ai.mit.edu
Subject: next-complex-command gives wrong error msg
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 :-)
Not quite :-) Even less important is that "preceding" is misspelled.
< Stephen