Re: patch gud-gdb to respect other-frame-window?

[Stephen Leake]

Another data point. In a package I'm working on,
'wisi-show-parse-errors' shows errors found by the indent parser in a
small window at the bottom of the screen, using a display action of:

(cons #'display-buffer-at-bottom
                              (list (cons 'window-height
                              #'shrink-window-if-larger-than-buffer))).

But the default setting of 'display-buffer-overriding-action' overrides
that, and now the window takes half the screen.

So sometimes I want the default value that Emacs provides
(for wisi-show-parse-errors etc), and sometimes I don't (for gud-gdb etc).

So I need an exception mechanism; apply my default value for
display-buffer-overriding-action, except in the following buffers/modes.

Or invert that, only apply a default value for the following
buffers/modes/commands.

Ah; that's what 'display-buffer-alist is for. I'll try that.



Stephen Leake <address@hidden> writes:

> Stephen Leake <address@hidden> writes:
>
>> Stefan Monnier <address@hidden> 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