all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tino Calancha <tino.calancha@gmail.com>
To: 26650@debbugs.gnu.org
Subject: bug#26650: 26.0.50; Protect *Backtrace* from accidental killing
Date: Tue, 25 Apr 2017 21:02:24 +0900	[thread overview]
Message-ID: <871ssgvgof.fsf@calancha-pc> (raw)


I often kills the *Backtrace* buffer; then, errors won't show
*Backtrace* again in this session.
Could *Backtrace* be guarded with something like `edebug-kill-buffer'
in kill-buffer-hook?

emacs -Q
;; eval following form:
(error "hi") ; This jump to *Backtrace*
q ; Back to top level

;; Eval it again:
(error "hi") ; This time kill *Backtrace*
C-x k RET

;; Eval it once more:
(error "hi")
;; 'hi' is printed in echo area, but *Backtrace* is not shown.

In GNU Emacs 26.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.22.11)
 of 2017-04-25 built
Repository revision: 5b0fdefb4ca54b0d3dac3047ac1e4b380beb6ba7





             reply	other threads:[~2017-04-25 12:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-25 12:02 Tino Calancha [this message]
2017-04-25 12:13 ` bug#26650: 26.0.50; Protect *Backtrace* from accidental killing npostavs
2017-04-25 12:18   ` Tino Calancha
2017-04-25 12:50     ` npostavs
2017-04-25 13:02       ` Tino Calancha
2017-04-26 10:07       ` Eli Zaretskii
2017-04-26 10:36         ` Tino Calancha
2017-04-26 11:03           ` Eli Zaretskii
2017-04-26 12:52             ` npostavs
2017-04-26 13:57               ` Tino Calancha
2017-04-26 15:33               ` Eli Zaretskii
2017-05-24  0:18                 ` npostavs
2017-04-26 10:49         ` Michael Heerdegen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871ssgvgof.fsf@calancha-pc \
    --to=tino.calancha@gmail.com \
    --cc=26650@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.