From: Vikas Rawal <vikaslists@agrarianresearch.org>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: orgmod: R and threeparttable
Date: Sat, 14 Dec 2013 14:48:27 +0100 [thread overview]
Message-ID: <CAFVt51+UhkC1sYy_fC+fbgDpP-jU4bb_NehpW_V14CWv7275Aw@mail.gmail.com> (raw)
In-Reply-To: <CAFVt51JkmWW5T8+xrmq-u4KPnV=ZeM5E70PqEgtB4Rch_uUGNQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3975 bytes --]
Nicolas,
Special blocks seem to work very well, actually. Thank you.
This is what you had proposed:
#+begin_threeparttable
...
tabular with Org syntax
...
#+begin_tablenotes
... probably some raw LaTeX...
#+end_tablenotes
#+end_threeparttable
It seem to work beautifully even when the table is a result of a source
code block. My experiments suggest that when the result changes, on account
of evaluating the source code block again, the special block structure
around is respected.
Super. I am amazed.
Thank you.
I bow.
Vikas
On Sat, Dec 14, 2013 at 1:06 PM, Vikas Rawal <
vikaslists@agrarianresearch.org> wrote:
>
>
>
> On Sat, Dec 14, 2013 at 12:04 PM, Nicolas Goaziou <n.goaziou@gmail.com>wrote:
>
>> Vikas Rawal <vikaslists@agrarianresearch.org> writes:
>>
>> > I do not know if I am expressing myself clearly. The table is being
>> > generated by an R source code. We need a way of adding notes to such a
>> > table.
>>
>> There are two different problems:
>>
>> 1. How to generate "threeparttable" environment using Org syntax and
>> `latex' export back-end.
>> 2. How to generate Org syntax specified above from a source block.
>>
>> At the moment, my only concern is point 1.
>>
>>
> Yes, this is right.
>
> > Unfortunately, on such matters, one has to work with the conventions in
>
>> > different disciplines. At least in social sciences, it is usually
>> expected
>> > that notes are placed below Tables and Figures, and not as part of
>> > footnotes, which are reserved for notes to text. At least my
>> collaborators
>> > and readers frown when I put table sources and notes in the footnotes.
>>
>> Understood. You didn't answer to my suggestion to use special blocks,
>> though.
>>
>>
> I do not know how to use special blocks. I will read the manual and see
> what can be done with those. I f special blocks cannot give a statisfactory
> solution (I do not know), other questions you raise may be relevant in
> exploring a better solution.
>
>
>>
>>
>> If my suggestion to use special blocks doesn't apply, you still need to
>> properly define your problem. In particular:
>>
>> - How table notes are generated? Do you want to hijack footnotes in
>> table to produce them?
>>
> - Should note numbers be configurable?
>>
>
> We should be able to add something to #+RESULTS block. I would think that
> the natural way would be to specify threeparttable in #+attr_latex. It
> would be ideal to put contents of a footer under a separate headline
> (tagged noexport) somewhere in the document with a custom_id property. This
> custom_id could be specified along with threeparttable in the above
> #+attr_latex. Something like the following:
>
> #+attr_latex: threeparttable [[notes_custom_id_1]]
> #+RESUlTS:
> |x|y|z|
> |1|2|2|
>
> * Table notes :noexport:
> :PROPERTIES:
> :CUSTOM_ID: notes_custom_id_1
> :END:
> + first note here
> + second note here
> + third note here
>
> - Should "threeparttable" be generated only when table contains at least
>> a note and some global option is set to a non-nil value? Or should
>> a user explicitly write that he requires such an environment for the
>> current table?
>>
>
> I would think threeparttable be generated when you have something like the
> above specified in #+attr_latex.
>
>
>> - Can another environment than "tabular" be used within
>> "threeparttable"?
>> - Is the "table" environment around mandatory?
>> - ...
>>
>
> I use tabulary inside threeparttable (that is, when I give raw latex
> code).
>
> The code I used has table environment around it. I am no expert on latex
> and I must have put it together using whatever I could find on
> threeparttable. I cannot say whether this is mandatory. I am sure other
> people on this list would just know this. Otherwise, I can experiment.
>
> I am really stretching my capabilities and knowledge of org. So, please
> excuse me, if what I said is nonsensical.
>
> Vikas
>
>
>
[-- Attachment #2: Type: text/html, Size: 6387 bytes --]
next prev parent reply other threads:[~2013-12-14 13:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 11:12 orgmod: R and threeparttable Vikas Rawal
2013-12-11 20:43 ` John Hendy
2013-12-13 7:07 ` Vikas Rawal
2013-12-14 8:08 ` Vikas Rawal
2013-12-14 8:46 ` Nicolas Goaziou
2013-12-14 9:40 ` Vikas Rawal
2013-12-14 11:04 ` Nicolas Goaziou
2013-12-14 12:06 ` Vikas Rawal
2013-12-14 13:48 ` Vikas Rawal [this message]
2013-12-15 9:50 ` Vikas Rawal
2013-12-15 9:55 ` Vikas Rawal
2013-12-15 9:58 ` Nicolas Goaziou
2013-12-15 10:21 ` Vikas Rawal
2013-12-15 10:46 ` Nicolas Goaziou
2013-12-15 10:50 ` Vikas Rawal
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=CAFVt51+UhkC1sYy_fC+fbgDpP-jU4bb_NehpW_V14CWv7275Aw@mail.gmail.com \
--to=vikaslists@agrarianresearch.org \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
/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).