Clean up gdb-mi's usage of display-buffer.
authorChong Yidong <cyd@gnu.org>
Sun, 26 Aug 2012 09:16:48 +0000 (17:16 +0800)
committerChong Yidong <cyd@gnu.org>
Sun, 26 Aug 2012 09:16:48 +0000 (17:16 +0800)
commitd97af5a07f045ed1de8045bab25af384c21b08dd
tree6aabcc758b92f8121b679323b808ddd4c6b2309d
parentd5172d4fbc2ca871d18426fb9e84ee6bb87a0e68
Clean up gdb-mi's usage of display-buffer.

* progmodes/gdb-mi.el (gdb-display-buffer-other-frame-action): New
variable, replacing gdb-frame-parameters.
(gdb-frame-io-buffer, gdb-frame-breakpoints-buffer)
(gdb-frame-threads-buffer, gdb-frame-memory-buffer)
(gdb-frame-disassembly-buffer, gdb-frame-stack-buffer)
(gdb-frame-locals-buffer, gdb-frame-registers-buffer): Use it.
(def-gdb-frame-for-buffer): Macro deleted.  It is easier to define
the functions directly with gdb-display-buffer-other-frame-action.
(gdb-display-breakpoints-buffer, gdb-display-threads-buffer)
(gdb-display-memory-buffer, gdb-display-disassembly-buffer)
(gdb-display-stack-buffer, gdb-display-locals-buffer)
(gdb-display-registers-buffer): Define directly.
(def-gdb-display-buffer): Macro deleted.
(gdb-display-buffer): Remove second and third args, callers don't
use them.  Defer to the default display-buffer behavior, apart
from making windows dedicated.
(gdb-setup-windows): Don't call display-buffer unnecessarily.

* window.el (display-buffer-pop-up-frame): Handle a
pop-up-frame-parameters alist entry.
(display-buffer): Document it.

* progmodes/gud.el (gud-display-line): Just use display-buffer.
etc/NEWS
lisp/ChangeLog
lisp/progmodes/gdb-mi.el
lisp/progmodes/gud.el
lisp/window.el