Mercurial > emacs
changeset 6567:baf8fe0c51e3
(debug): Behave sensibly if pop-up-frames is set.
| author | Karl Heuer <kwzh@gnu.org> |
|---|---|
| date | Tue, 29 Mar 1994 02:20:04 +0000 |
| parents | 248eede22658 |
| children | c87ae1f14148 |
| files | lisp/emacs-lisp/debug.el |
| diffstat | 1 files changed, 13 insertions(+), 4 deletions(-) [+] |
line wrap: on
line diff
--- a/lisp/emacs-lisp/debug.el Tue Mar 29 01:39:51 1994 +0000 +++ b/lisp/emacs-lisp/debug.el Tue Mar 29 02:20:04 1994 +0000 @@ -60,7 +60,7 @@ (debug-on-error nil) (debug-on-quit nil) (debugger-buffer (let ((default-major-mode 'fundamental-mode)) - (generate-new-buffer "*Backtrace*"))) + (get-buffer-create "*Backtrace*"))) (debugger-old-buffer (current-buffer)) (debugger-step-after-exit nil) ;; Don't keep reading from an executing kbd macro! @@ -136,9 +136,18 @@ (buffer-read-only t)) (message "") (recursive-edit)))) - ;; So that users do not try to execute debugger commands - ;; in an invalid context - (kill-buffer debugger-buffer) + ;; Kill or at least neuter the backtrace buffer, so that users + ;; don't try to execute debugger commands in an invalid context. + (if (get-buffer-window debugger-buffer 'visible) + ;; 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 but leave it visible. + (save-excursion + (set-buffer debugger-buffer) + (erase-buffer) + (fundamental-mode)) + (kill-buffer debugger-buffer)) (store-match-data debugger-match-data))) ;; Put into effect the modified values of these variables ;; in case the user set them with the `e' command.