Bug: lisp error on user error [9.3.6 (9.3.6-43-gc77edd-elpa @ /home/minshall/.emacs.d/elpa/org-20200413/)]

Bug: lisp error on user error [9.3.6 (9.3.6-43-gc77edd-elpa @ /home/minshall/.emacs.d/elpa/org-20200413/)]

[Greg Minshall]

hi.  the following example should possibly result in an error message,
but actually causes a lisp error/backtrace.  i have a code block with
":results vertatim :colnames yes", and am returning a simple character
string (so, no headers -- tsk, tsk, a user error).  this happens with
'emacs -Q'.  if either the ":results verbatim" or the ":colnames yes" is
left out, i get no error.  below is a sample file.  cheers.

Emacs  : GNU Emacs 26.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.10)
 of 2019-08-29
Package: Org mode version 9.3.6 (9.3.6-43-gc77edd-elpa @ /home/minshall/.emacs.d/elpa/org-20200413/)

----
evaluating the R code block gives an error in lisp code

#+name: getRenabled
#+BEGIN_SRC elisp
  (progn
    (setq debug-on-error t)
    (org-babel-do-load-languages
     'org-babel-load-languages
     '((R . t)))
    1)
#+END_SRC

#+begin_src R :var first=getRenabled :results verbatim :colnames yes
"that"
#+end_src

Re: Bug: lisp error on user error [9.3.6 (9.3.6-43-gc77edd-elpa @ /home/minshall/.emacs.d/elpa/org-20200413/)]

[Bastien]

Hi Greg,

Greg Minshall <minshall@umich.edu> writes:

> hi.  the following example should possibly result in an error message,
> but actually causes a lisp error/backtrace.  i have a code block with
> ":results vertatim :colnames yes", and am returning a simple character
> string (so, no headers -- tsk, tsk, a user error).  this happens with
> 'emacs -Q'.  if either the ":results verbatim" or the ":colnames yes" is
> left out, i get no error.  below is a sample file.

thanks for reporting this.  I've pushed a quick fix in master so that
it now displays an error as the output and does not choke at the user
as it did before.

Best,

-- 
 Bastien

Re: Bug: lisp error on user error [9.3.6 (9.3.6-43-gc77edd-elpa @ /home/minshall/.emacs.d/elpa/org-20200413/)]

[Greg Minshall]

Bastien,

> thanks for reporting this.  I've pushed a quick fix in master so that
> it now displays an error as the output and does not choke at the user
> as it did before.

thank you!