all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
* bug#7827: Please do not give an error in help when it fails
@ 2011-01-12  1:40 Lennart Borgman
  2019-10-01 20:53 ` Lars Ingebrigtsen
  0 siblings, 1 reply; 2+ messages in thread
From: Lennart Borgman @ 2011-01-12  1:40 UTC (permalink / raw)
  To: 7827

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.





^ permalink raw reply	[flat|nested] 2+ messages in thread

* bug#7827: Please do not give an error in help when it fails
  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
  0 siblings, 0 replies; 2+ messages in thread
From: Lars Ingebrigtsen @ 2019-10-01 20:53 UTC (permalink / raw)
  To: Lennart Borgman; +Cc: 7827

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





^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2019-10-01 20:53 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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

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.