From: Dima Kogan <dima@secretsauce.net>
To: martin rudalics <rudalics@gmx.at>
Cc: 20034@debbugs.gnu.org
Subject: bug#20034: 25.0.50; [PATCH] gud never displays a source buffer over the gud window
Date: Sun, 08 Mar 2015 18:25:27 -0700 [thread overview]
Message-ID: <87fv9fklgb.fsf@secretsauce.net> (raw)
In-Reply-To: <54FC1E8C.5050706@gmx.at>
[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]
martin rudalics <rudalics@gmx.at> writes:
> > On my machine this switches to tst.c on top of the gud buffer, replacing
> > gud in its window. With the attached patch this does not happen.
> >
> > This is similar, but not identical to bug
> >
> > http://debbugs.gnu.org/cgi/bugreport.cgi?bug=17675
> >
> > The proposed fix in that bug does not handle the above recipe.
>
> Would your fix handle Bug#17675 as well? And maybe some of the related
> bugs in this area (see Bug#19901, for a recent example)?
Hi. The patch fixes 17676. 19901 is a slightly different problem, and
the attached patch fixes that as well.
> There also was a proposal to only "softly" dedicate some gud window to
> its buffer. See the thread entitled "Use of dedicated windows in
> gdb-mi.el".
I'm not concerned about gdb-mi here; just the old-style gud. I've seen
the new display-buffer behavior similarly affect the behavior of some
other things, like xcscope.el for instance (I'll handle that once this
change is OKed). I feel like the attached patch is the default behavior
I want most of the time, but this is probably different for each user.
Thanks
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-gud-never-displays-a-source-buffer-over-the-gud-wind.patch --]
[-- Type: text/x-diff, Size: 816 bytes --]
From 41bc170051c5541d5379aed97a634ca3ed094682 Mon Sep 17 00:00:00 2001
From: Dima Kogan <dima@secretsauce.net>
Date: Sat, 7 Mar 2015 17:37:20 -0800
Subject: [PATCH] gud never displays a source buffer over the gud window
---
lisp/progmodes/gud.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lisp/progmodes/gud.el b/lisp/progmodes/gud.el
index a12bdd9..f6dadeb 100644
--- a/lisp/progmodes/gud.el
+++ b/lisp/progmodes/gud.el
@@ -2813,7 +2813,7 @@ Obeying it means displaying in another window the specified file and line."
(gud-find-file true-file)))
(window (and buffer
(or (get-buffer-window buffer)
- (display-buffer buffer))))
+ (display-buffer buffer '(nil (inhibit-same-window . t))))))
(pos))
(when buffer
(with-current-buffer buffer
--
2.1.4
next prev parent reply other threads:[~2015-03-09 1:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-08 1:59 bug#20034: 25.0.50; [PATCH] gud never displays a source buffer over the gud window Dima Kogan
2015-03-08 10:03 ` martin rudalics
2015-03-09 1:25 ` Dima Kogan [this message]
2015-03-09 10:37 ` martin rudalics
2015-03-09 16:01 ` Dima Kogan
2015-03-10 8:09 ` martin rudalics
2015-03-16 19:32 ` Dima Kogan
2015-03-17 10:25 ` 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=87fv9fklgb.fsf@secretsauce.net \
--to=dima@secretsauce.net \
--cc=20034@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).