unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: 52026@debbugs.gnu.org
Subject: bug#52026: edebug-pop-to-buffer pops up buffer at random windows
Date: Sun, 21 Nov 2021 21:33:52 +0200	[thread overview]
Message-ID: <86czmtl2vz.fsf@mail.linkov.net> (raw)

It's hard to edebug in a predefined window configuration
when edebug pops up source code buffers in random windows,
and thus continually changes the window configuration.

Would it be possible to always show the debugged source files
in the same window?





             reply	other threads:[~2021-11-21 19:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-21 19:33 Juri Linkov [this message]
2021-11-22  8:10 ` bug#52026: edebug-pop-to-buffer pops up buffer at random windows Juri Linkov

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=86czmtl2vz.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=52026@debbugs.gnu.org \
    /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).