From: Lars Ingebrigtsen <larsi@gnus.org>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: 7827@debbugs.gnu.org
Subject: bug#7827: Please do not give an error in help when it fails
Date: Tue, 01 Oct 2019 22:53:09 +0200 [thread overview]
Message-ID: <87ftkcw5l6.fsf@gnus.org> (raw)
In-Reply-To: <AANLkTikvbWjC_LiRtS8Lwuq1ZnYtymdf7_ZPH_CmWayd@mail.gmail.com> (Lennart Borgman's message of "Wed, 12 Jan 2011 02:40:14 +0100")
Lennart Borgman <lennart.borgman@gmail.com> writes:
> I just got this error when clicking the [back] button in help:
>
> Debugger entered--Lisp error: (error "Selecting deleted buffer")
> describe-mode(#<killed buffer>)
> apply(describe-mode #<killed buffer>)
> help-xref-go-back(#<buffer *Help*>)
> apply(help-xref-go-back #<buffer *Help*>)
> help-do-xref(214 help-xref-go-back (#<buffer *Help*>))
> help-button-action(#<marker (moves after insertion) at 1 in *Help*>)
> push-button(214)
> call-interactively(push-button nil nil)
>
> That is very unpractical since it prevents from going further back in
> the help stack. (Currently I am trying to find my test case which was
> some help text 611 chars long, but I do not remember what it was.)
>
> Just put the backtrace in the help buffer instead with a short explanation.
I don't see why an error in the help buffer should be treated
differently than anywhere else: If you have debug-on-error bound, then
you should get a proper backtrace.
So I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2019-10-01 20:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 1:40 bug#7827: Please do not give an error in help when it fails Lennart Borgman
2019-10-01 20:53 ` Lars Ingebrigtsen [this message]
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=87ftkcw5l6.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=7827@debbugs.gnu.org \
--cc=lennart.borgman@gmail.com \
/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.