Uwe Brauer writes:
> I am running GNU emacs and org mode, whose versions are specified below.
> Sometimes when being in a gnus message buffer and running org-capture
> I obtain an error whose bug trace I attach. Usually I have to restart
> emacs.
>
> ,----
> |
> | Debugger entered--Lisp error: (error "Capture template ‘ms’: No article on
> current line")
> | signal(error ("Capture template ‘ms’: No article on current line"))
> | error("Capture template `%s': %s" "ms" "No article on current line")
> | org-capture(nil)
> | funcall-interactively(org-capture nil)
> | call-interactively(org-capture nil nil)
> | command-execute(org-capture)
With this backtrace alone (which involves org-capture catching the
internal error), I think it's going to be hard for anyone to guess
what's going on here. It sounds like once you encounter this error,
subsequent calls reliably trigger it. Next time you run into it, I'd
suggest re-evaluating org-capture to something like below to hopefully
see a more informative backtrace.
diff --git a/lisp/org-capture.el b/lisp/org-capture.el
index 831c3e1f4..b20124ced 100644
--- a/lisp/org-capture.el
+++ b/lisp/org-capture.el
@@ -693,9 +693,7 @@ (defun org-capture (&optional goto keys)
(string-prefix-p "CAPTURE-" (buffer-name)))
(kill-buffer (current-buffer)))
(set-window-configuration (org-capture-get :return-to-wconf))
- (error "Capture template `%s': %s"
- (org-capture-get :key)
- (error-message-string error))))
+ (signal (car error) (cdr error))))
(when (and (derived-mode-p 'org-mode) (org-capture-get :clock-in))
(condition-case nil
(progn
