From: Michael Heerdegen <michael_heerdegen@web.de>
To: martin rudalics <rudalics@gmx.at>
Cc: 10805@debbugs.gnu.org
Subject: bug#10805: 24.0.93; edebug-trace t may cause stuff being inserted into current buffer
Date: Wed, 15 Feb 2012 00:53:44 +0100 [thread overview]
Message-ID: <87vcn97z07.fsf@web.de> (raw)
In-Reply-To: <4F3A3D3C.8020002@gmx.at> (martin rudalics's message of "Tue, 14 Feb 2012 11:53:48 +0100")
Note that my experience with `edebug-trace' is also zero, I only tried
it out, so take my comments with some care.
> More or less so, yes. This is yet another incarnation of the "unless
> WINDOW already is the selected window, its buffer becomes the current
> buffer" problem of `select-window'.
Maybe. But please keep in mind that `edebug-trace-display' is about
_displaying_ a buffer. We don't want the user to edit the trace buffer,
so calling `select-window' is in fact not necessary in this case. The
former window is instantly re-selected by `edebug-trace-display'.
Please also note (another issue, but related) that if the trace buffer
is already visible in another (visible) frame, a new window pops up in
the current frame nevertheless, which is kind of annoying if source
files are spread over multiple frames.
Thanks,
Michael.
next prev parent reply other threads:[~2012-02-14 23:53 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 [this message]
2012-02-15 9:56 ` martin rudalics
2012-02-17 2:18 ` Michael Heerdegen
2012-02-17 9:58 ` martin rudalics
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=87vcn97z07.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=10805@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).