From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 12648@debbugs.gnu.org
Subject: bug#12648: 24.2.50; display-buffer switches to another frame
Date: Mon, 15 Oct 2012 19:26:29 +0200 [thread overview]
Message-ID: <83mwzn4pfe.fsf@gnu.org> (raw)
In-Reply-To: <507C071C.1090402@gmx.at>
> Date: Mon, 15 Oct 2012 14:52:44 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: 12648@debbugs.gnu.org
>
> > I think this is different: setting pop-up-frames non-nil expresses a
> > wish to see certain behavior that the default shouldn't have.
>
> Well, if you call `display-buffer' with the FRAME argument 'visible
> you're explicitly asking for such behavior.
Fair enough.
> > Yes, but is the current behavior useful as it is?
>
> We have a choice between Scylla and Charybdis. People complained that
> making a new frame select the window and reusing an existing frame not
> select the window would break their typing habits ...
>
> > If gud.el should call display-buffer in some different way to avoid
> > selecting the frame with the source, that, too, could be a good
> > solution.
>
> IIUC that's what Chong's `inhibit-switch-frame' alist entry is meant
> for. I haven't tried it yet, though.
Is that supposed to fix the source-in-other-frame case without harming
the source-in-other-window case (which works correctly with the
current code in gud.el)? If so, then all we need is to change gud.el
to use that entry. If some people want the current behavior with
'visible, then so be it; I only want to fix GUD, where I don't believe
anyone would want it.
Thanks.
next prev parent reply other threads:[~2012-10-15 17:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 16:49 bug#12648: 24.2.50; display-buffer switches to another frame Eli Zaretskii
2012-10-14 18:33 ` martin rudalics
2012-10-14 19:28 ` Eli Zaretskii
2012-10-15 12:52 ` martin rudalics
2012-10-15 17:26 ` Eli Zaretskii [this message]
2012-10-16 9:39 ` martin rudalics
2012-10-16 13:27 ` Stefan Monnier
2012-10-17 9:37 ` martin rudalics
2012-10-18 19:46 ` Chong Yidong
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=83mwzn4pfe.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12648@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 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.