From: martin rudalics <rudalics@gmx.at>
To: Stephen Leake <stephen_leake@stephe-leake.org>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: patch gud-gdb to respect other-frame-window?
Date: Tue, 31 Jul 2018 08:37:51 +0200 [thread overview]
Message-ID: <5B6003BF.1010002@gmx.at> (raw)
In-Reply-To: <868t5sr7nb.fsf@stephe-leake.org>
> The current design of 'other-frame-window' only defines the behavior
> when the other-frame or other-window prefixes are invoked;
In that case the special behavior specified by 'other-frame-window' is
supposed to prevail any preferences stored in 'display-buffer-alist'.
This is precisely one of the cases 'display-buffer-overriding-action'
has been added for.
> the behavior
> with no prefix is left to the default Emacs code,
Which means that in such case 'other-frame-window' should refrain from
touching 'display-buffer-overriding-action' and leave the decision of
what to do to 'display-buffer-alist'.
> or to a user-provided
> 'display-buffer-overriding-action'.
There should be no such thing. If someone sees an absolute need for
it, we have a design bug.
>> It's a simple statement that 'other-frame-window' thinks that it is
>> always right in its decision and the user has to either take it or
>> leave it.
>
> Not quite; it is only right when the prefixes are invoked.
Then 'other-frame-window' does something it should not do when no
prefixes are invoked.
martin
next prev parent reply other threads:[~2018-07-31 6:37 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 [this message]
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
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=5B6003BF.1010002@gmx.at \
--to=rudalics@gmx.at \
--cc=emacs-devel@gnu.org \
--cc=stephen_leake@stephe-leake.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.