From: martin rudalics <rudalics@gmx.at>
To: michael_heerdegen@web.de
Cc: 10805@debbugs.gnu.org
Subject: bug#10805: 24.0.93; edebug-trace t may cause stuff being inserted into current buffer
Date: Fri, 17 Feb 2012 10:58:45 +0100 [thread overview]
Message-ID: <4F3E24D5.7090003@gmx.at> (raw)
In-Reply-To: <878vk2kxsf.fsf@web.de>
> 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
next prev parent reply other threads:[~2012-02-17 9:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 22:29 bug#10805: 24.0.93; edebug-trace t may cause stuff being inserted into current buffer Michael Heerdegen
2012-02-14 10:53 ` martin rudalics
2012-02-14 23:53 ` Michael Heerdegen
2012-02-15 9:56 ` martin rudalics
2012-02-17 2:18 ` Michael Heerdegen
2012-02-17 9:58 ` martin rudalics [this message]
2012-02-17 15:12 ` Stefan Monnier
2012-02-18 17:04 ` martin rudalics
2012-10-04 13:17 ` martin rudalics
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F3E24D5.7090003@gmx.at \
--to=rudalics@gmx.at \
--cc=10805@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).