From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Daniele Pizzolli <dan@toel.it>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] babel eval of emacs-lisp: orgtbl-to-orgtbl: Wrong type argument: listp, t
Date: Mon, 23 Feb 2015 10:43:38 -0500 [thread overview]
Message-ID: <m2a904iqfp.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <867fv8sr6v.fsf@me.localhost.invalid>
>
> thanks for the explanation.
>
> Unfortunately my lisp knowledge is too limited to understand you. As a
> naive org-mode user, if possible I do not want to be exposed to org
> internals error, especially the confusing ones, where the custom code
> works fine. Maybe we can get a warning instead of an error?
>
> It is not a really big issue, a newcomer can be confused, if not scared,
> having an error on the fist babel usage.
I agree. Even for experienced people, this is pretty annoying. Something
as simple as
#+BEGIN_SRC emacs-lisp
'((1 . nil) (2 . 3))
#+END_SRC
fails with a cryptic error. While this works fine. I would vote for a
fall-back to code or even a plain string in this case.
#+BEGIN_SRC emacs-lisp :results code
'((1 . nil) (2 . 3))
#+END_SRC
#+RESULTS:
#+BEGIN_SRC emacs-lisp
((1)
(2 . 3))
#+END_SRC
>
> Best,
> Daniele
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
next prev parent reply other threads:[~2015-02-23 15:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 12:48 [BUG] babel eval of emacs-lisp: orgtbl-to-orgtbl: Wrong type argument: listp, t Daniele Pizzolli
2015-02-23 12:57 ` John Kitchin
2015-02-23 13:17 ` Daniele Pizzolli
2015-02-23 15:43 ` John Kitchin [this message]
2015-02-23 17:46 ` Nicolas Goaziou
2015-02-23 18:07 ` John Kitchin
2015-02-24 16:50 ` Nicolas Goaziou
2015-02-24 18:21 ` John Kitchin
2015-02-24 23:36 ` [PATCH] was " Charles C. Berry
2015-02-25 13:44 ` Nicolas Goaziou
2015-02-23 19:30 ` Daniele Pizzolli
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2a904iqfp.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--cc=dan@toel.it \
--cc=emacs-orgmode@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).