# HG changeset patch # User Stefan Monnier # Date 1118087225 0 # Node ID 80ef8a2a052d5b5dcf353f6055e2798722e9e409 # Parent 81d7efcce2ff904ee8d1105646cfdf4a81278c3f (debug): Don't bury the buffer unless it's in a dedicated window. diff -r 81d7efcce2ff -r 80ef8a2a052d lisp/ChangeLog --- a/lisp/ChangeLog Mon Jun 06 19:42:25 2005 +0000 +++ b/lisp/ChangeLog Mon Jun 06 19:47:05 2005 +0000 @@ -1,5 +1,8 @@ 2005-06-06 Stefan Monnier + * emacs-lisp/debug.el (debug): Don't bury the buffer unless it's in + a dedicated window. + * international/latexenc.el (latexenc-find-file-coding-system): Undo part of last patch, to turn off a compiler warning. diff -r 81d7efcce2ff -r 80ef8a2a052d lisp/emacs-lisp/debug.el --- a/lisp/emacs-lisp/debug.el Mon Jun 06 19:42:25 2005 +0000 +++ b/lisp/emacs-lisp/debug.el Mon Jun 06 19:47:05 2005 +0000 @@ -221,12 +221,18 @@ ;; Still visible despite the save-window-excursion? Maybe it ;; it's in a pop-up frame. It would be annoying to delete and ;; recreate it every time the debugger stops, so instead we'll - ;; erase it and hide it but keep it alive. + ;; erase it (and maybe hide it) but keep it alive. (with-current-buffer debugger-buffer (erase-buffer) (fundamental-mode) (with-selected-window (get-buffer-window debugger-buffer 0) - (bury-buffer))) + (when (window-dedicated-p (selected-window)) + ;; If the window is not dedicated, burying the buffer + ;; will mean that the frame created for it is left + ;; around showing smoe random buffer, and next time we + ;; pop to the debugger buffer we'll create yet + ;; another frame. + (bury-buffer)))) (kill-buffer debugger-buffer)) (set-match-data debugger-outer-match-data))) ;; Put into effect the modified values of these variables