From: "Thomas S. Dye" <tsd@tsdye.online>
To: emacs-orgmode@gnu.org
Subject: Bug: Babel :var order affects :colnames [9.2 (9.2-41-g010a35-elpaplus @ /home/dk/.emacs.d/elpa/org-plus-contrib-20190122/)]
Date: Wed, 23 Jan 2019 23:53:25 -1000 [thread overview]
Message-ID: <87bm46qt4a.fsf@tsdye.online> (raw)
Remember to cover the basics, that is, what you expected to happen
and
what in fact did happen. You don't know how to make a good
report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
------------------------------------------------------------------------
I expect =colnames-bug-bad= to parse =test-table= like
=colnames-bug-good=. The only difference is the order of :var
assignments.
**** ECM
#+name: colnames-bug-bad
#+header: :var str="Foo" :var tab=test-table
#+header: :colnames yes
#+BEGIN_SRC R
data.frame(tab)
#+END_SRC
#+RESULTS: colnames-bug-bad
| cell.1 | cell.2 |
|--------+--------|
#+name: colnames-bug-good
#+header: :var tab=test-table :var str="Foo"
#+header: :colnames yes
#+BEGIN_SRC R
data.frame(tab)
#+END_SRC
#+RESULTS: colnames-bug-good
| head.1 | head.2 |
|--------+--------|
| cell.1 | cell.2 |
#+name: test-table
| head.1 | head.2 |
|--------+--------|
| cell.1 | cell.2 |
Let me know if you have questions.
All the best,
Tom
Emacs : GNU Emacs 26.1 (build 2, x86_64-pc-linux-gnu, GTK+
Version 3.22.30)
of 2018-05-28
Package: Org mode version 9.2 (9.2-41-g010a35-elpaplus @
/home/dk/.emacs.d/elpa/org-plus-contrib-20190122/)
--
Thomas S. Dye
http://tsdye.online/tsdye
next reply other threads:[~2019-01-24 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 9:53 Thomas S. Dye [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-28 23:34 Bug: Babel :var order affects :colnames [9.2 (9.2-41-g010a35-elpaplus @/home/dk/.emacs.d/elpa/org-plus-contrib-20190122/)] Thomas S. Dye
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=87bm46qt4a.fsf@tsdye.online \
--to=tsd@tsdye.online \
--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).