From: Greg Minshall <firstname.lastname@example.org>
To: Tim Cross <email@example.com>
Subject: Re: quotation marks in table cell vs. org-babel-ref-resolve
Date: Mon, 28 Feb 2022 16:20:42 -0800 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
i have a problem similar to this from a few months ago. in this case,
it seems to be when trying to pass a column with a quoted-string inside
of it. (this is on the "bugfix" branch.) my e-lisp code seems to get
just the initial part of the string from the cell with "odd" contents.
| this, "he said" | is where, | "you go in" there |
#+begin_src elisp :var xl=xl
(message "%S" xl)
when i execute this, *Messages* says
(("this, \"he said\"" "is where," "you go in"))
Code block evaluation complete.
(my complaint: there's no there there. :)
in December, when i reported something similar, Tim pushed back, and
maybe i should elaborate:
> The key question is what is the use case for having this 'mixed'
> content in a table cell?
for better or worse, i most often use org-mode tables as (storage and
data entry mechanisms for) simple data bases. other than the pipe
symbol ('|'), i assume i can put "anything" in a cell, and extract it
later. i find this very valuable.
normally, i pass such tables to some R code (this example, btw, breaks
passing to R code). but occasionally i do other things with them.
the behavior i'm seeing seems to me inconsistent, indicating it is maybe
not intentional. exporting, for example, at least to html. i see the
full contents of the third column.
prev parent reply other threads:[~2022-03-01 0:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 17:28 quotation marks in table cell vs. org-babel-ref-resolve Greg Minshall
2021-12-03 18:26 ` Greg Minshall
2021-12-03 23:45 ` Tim Cross
2021-12-04 3:16 ` Greg Minshall
2021-12-04 21:34 ` Tim Cross
2021-12-06 18:02 ` Greg Minshall
2021-12-06 9:20 ` Greg Minshall
2022-10-23 7:09 ` Ihor Radchenko
2022-03-01 0:20 ` Greg Minshall [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).