bug#10805: 24.0.93; edebug-trace t may cause stuff being inserted into current buffer

[martin rudalics]

> Yes, of course, that works.  The same applies to the source code
> buffers.  Maybe we could introduce a user option specifying if windows
> in other (visible) frames should be considered or not.  Dunno if that
> would be appropriate, I didn't use edebug much before.  Currently,
> edebug never considers other frames (most of the code seems to have been
> written at a time when Emacs did not yet have frames).  Some users might
> find it handy if they could use source buffers spread over several
> frames, and edebug would work with them.

Adding an appropriate rule for these buffers to `display-buffer-alist'
should be the appropriate solution.  The problem is that it's
non-trivial to identify source code buffers in `display-buffer-alist'.
For example, in the case that the user wants to make buffer display via
edebug behave differently from via `find-file'.

martin