> Now I try to use emacsclient to open something else, but since isearch
> is running the new buffer does not appear on top.
Hmm... indeed, I can reproduce it. Not sure why, yet.
> emacsclient seems to interrupt find-file, swith-to-buffer and areas
> marked to be copied, so I think it is somewhat inconsistent not to
> quit isearch and put the new buffer on top.
Indeed. That it doesn't interrupt isearch is not a surprise: isearch is
implemented quite differently. emacsclient interrupts recursive edits and
minibuffers, but isearch uses neither (it basically temporarily switches
major-mode instead).
I don't think we will be able to find a patch that can break out of isearch
for Emacs-22 (it's probably going to be too big a change). But the fact
that not only it doesn't break out of isearch, but additionally the buffer
isn't displayed at all looks more serious.
> O.T: Microsoft Corp. hasn't really built an X server, have they? It
> looks a bit odd a few lines down in this message.
Good point. I'll change the text to "Windowing system distributor".
Stefan
_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
