GNU bug report logs - #17675
24.4.50; *gud* buffer keeps on getting buried

Previous Next

Package: emacs;

Reported by: Michael Welsh Duggan <mwd <at> md5i.com>

Date: Tue, 3 Jun 2014 15:18:02 UTC

Severity: normal

Found in version 24.4.50

Done: Dima Kogan <dima <at> secretsauce.net>

Bug is archived. No further changes may be made.

Full log


Message #11 received at 17675 <at> debbugs.gnu.org (full text, mbox):

From: Michael Welsh Duggan <mwd <at> md5i.com>
To: martin rudalics <rudalics <at> gmx.at>
Cc: Michael Welsh Duggan <mwd <at> md5i.com>, 17675 <at> debbugs.gnu.org
Subject: Re: bug#17675: 24.4.50; *gud* buffer keeps on getting buried
Date: Tue, 03 Jun 2014 20:52:24 -0400
martin rudalics <rudalics <at> gmx.at> writes:

>> At this point, notice that *gud-foo* buffer is gone, as foo.c has
>> replaced it.  At some point in time in the past, foo.c would end up
>> replacing the other window (the *scratch* buffer).  That would be the
>> desired behavior, as I would be able to continue using the *gud* buffer.
>>
>>      C-x 4 b RET   (accepting default "*gud-foo*")
>>      n RET RET
>>
>> Now *input/output of foo* replaced the *gud-foo* buffer.  I can't say
>> much about this, as I normally use gdb a different way.  But it seems
>> sub-optimal.  For my usual debugging habits, see Sequence 2.
>
> Here ...
>
>> Same set-up as for sequence 1, then as follows:
>>
>>      M-x gud-gdb RET
>>      RET               (accepting default "gdb --fullname foo")
>>      start RET
>>
>> At this point, notice that *gud-foo* buffer is gone, as foo.c has
>> replaced it.  At some point in time in the past, foo.c would end up
>> replacing the other window (the *scratch* buffer).  That would be the
>> desired behavior, as I would be able to continue using the *gud* buffer.
>
> ... and here it would be helpful to check whether `display-buffer' runs
> `display-buffer-use-some-window' and why it uses that window.  I usually
> edebug this from a second frame.

It's being selected by display-buffer-in-previous-window in this
particular test case.  Maybe gud needs to bind inhibit-same-window to t
before calling display-buffer (from gud-display-line).

-- 
Michael Welsh Duggan
(md5i <at> md5i.com)




This bug report was last modified 6 years and 363 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.