Hi Hrvoje. Since you're wading through isearch-mode, if you happen to run accross a fix for the problem with using it's history mechanism, that'd be real cool. :) Some details from my previous note: Me> Since there seems to be an interest in isearch-mode.el right now, I'll ask Me> a question I asked a long time ago - anybody know why using history with Me> isearch is broken? For example, try this: Me> run xemacs -q Me> clear scratch buffer with C-_ Me> enter 'a b c a b c a b c <RET>' Me> isearch for a from beginning of buffer (M-< C-s a) Me> stop isearch, then isearch for b (M-< C-s b) Me> stop isearch, then isearch for c (M-< C-s c) Me> stop isearch, then isearch for c again, using M-p to recall it, Me> search for it twice, second time it starts looking for b instead Me> of c (M-< C-s M-p M-p M-p C-s C-s) Me> I've tried a couple of times (half-heartedly, I admit) to debug it, but Me> haven't had much success other than it looks like the search-ring and Me> search-ring-yank-pointer get out of sync at some point... Me> The vanilla Emacs 20.4 isearch.el doesn't suffer from this, I noted, but Me> they were enough different that it didn't really help me figure it out. Me> Anyone have any ideas? I know it's been this way as far back as 19.13, perhaps longer... I've gone back a once or twice since I posted that, when I've had a few spare minutes, but still haven't been able to figure it out. I think I need to figure out how to use the elisp debugger better - is there any way to watch elisp variables dynamically change while tracing functions? Thanks, Chuck -- Charles K. Hines <chuck_hines(a)vnet.ibm.com&gt; <hinesc(a)us.ibm.com&gt; IBM Logic Synthesis Developer [BooleDozer (TM)] Martial Arts Instructor [Modern Arnis and Balintawak Escrima] "Go back to sleep, Chuck. You're just havin' a nightmare -- of course, we ARE still in Hell." (Gary Larson)