hi!<br><br>among others i've got this pending in my local slime:<br clear="all"><br>&nbsp;&nbsp;&nbsp; (slime-repl-previous-matching-input): Similar behaviour<br>&nbsp;&nbsp;&nbsp; like isearch-forward.<br>&nbsp;&nbsp;&nbsp; (slime-repl-next-matching-input): Ditto. In more details:
<br>&nbsp;&nbsp;&nbsp; You can freely navigate with slime-repl-previous/next-input<br>&nbsp;&nbsp;&nbsp; at any time among the history entries.<br>&nbsp;&nbsp;&nbsp; slime-repl-previous/next-matching-input when invoked<br>&nbsp;&nbsp;&nbsp; sequentially (i.e. pressing M-r multiple times) then it'll
<br>&nbsp;&nbsp;&nbsp; find the next matching regexp and also they can<br>&nbsp;&nbsp;&nbsp; be invoked at any history entry.<br>&nbsp;&nbsp;&nbsp; slime-repl-history-navigation-neutral-commands<br>&nbsp;&nbsp;&nbsp; stores a list of commands that are not reseting this<br>&nbsp;&nbsp;&nbsp; behaviour.
<br><br>the downside (?) is that it removes the old behaviour that when you moved the caret inside a history entry retrieved by slime-repl-previous/next-matching-input it was searching for entries that matched the string between the repl start and the caret. to be honest i didn't grasp that behaviour until i was looking at the code due to the annoyance caused by the inability to search again after a first regexp search.
<br><br>my question is, are people using this lost feature? are you satisfied by the way the repl history works in cvs head?<br><br>-- <br>- attila<br><br>&quot;- The truth is that I've been too considerate, and so became unintentionally cruel...
<br> - I understand.<br> - No, you don't understand! We don't speak the same language!&quot;<br>(Ingmar Bergman - Smultronstället)