From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: patch gud-gdb to respect other-frame-window?
Date: Mon, 30 Jul 2018 15:30:22 -0500 [thread overview]
Message-ID: <86zhy8piu9.fsf@stephe-leake.org> (raw)
In-Reply-To: <864lggqxpl.fsf@stephe-leake.org> (Stephen Leake's message of "Mon, 30 Jul 2018 15:23:50 -0500")
Stephen Leake <stephen_leake@stephe-leake.org> writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>>> Currently, 'gud-gdb' has its own notion of where to put the *gud-<exec name>*
>>> buffer. Since I use other-frame-window (a GNU ELPA package), I'd like to
>>> override that.
>>
>> Could you explain in more detail what's the problem you're seeing?
>
> Sorry, I was not very clear.
>
> If I type "M-x gud-gdb ...", the window in which the *gdb-<exec>* buffer
> is shown is usually not the currently selected window, but sometimes it
> is, depending on what buffer/window is currently selected. There is a
> logic to it, but it's not what I want.
>
> Since I'm used to other-frame-window, I expect newly created buffers to
> appear in the currently selected window; that's what happens for
> find-file and most other commands.
I just typed "C-h k ...", and the *Help* window appeared in a window
that is not the selected window. So there's more work to do ...
--
-- Stephe
next prev parent reply other threads:[~2018-07-30 20:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-29 17:22 patch gud-gdb to respect other-frame-window? Stephen Leake
2018-07-29 17:30 ` Eli Zaretskii
2018-07-30 6:56 ` Stephen Leake
2018-07-30 7:34 ` martin rudalics
2018-07-30 16:49 ` Stephen Leake
2018-07-31 6:37 ` martin rudalics
2018-07-31 9:21 ` [SPAM UNSURE] " Stephen Leake
2018-07-30 6:23 ` martin rudalics
2018-07-30 17:17 ` Stefan Monnier
2018-07-30 20:23 ` Stephen Leake
2018-07-30 20:28 ` Stefan Monnier
2018-07-30 20:30 ` Stephen Leake [this message]
2018-07-30 21:22 ` Stephen Leake
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86zhy8piu9.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.org \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.