From: Vikas Rawal <vikaslists@agrarianresearch.org>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Latex export of tables
Date: Tue, 16 Apr 2013 17:26:19 +0530 [thread overview]
Message-ID: <20130416115619.GA12405@panahar> (raw)
In-Reply-To: <20130414232953.GC11696@kuru.dyndns-at-home.com>
> > I am using org-mode version 8.0-pre (release_8.0-pre-247-gbc3ccd @
> > /home/vikas/lisp/org-mode/lisp/).
> >
> > I have a table generated by a source block in a document that I would
> > like to export to latex. In the exported tex file, I would like org to
> > insert a line like the following between \end(tabular} and \end{table}
> >
> > \begin{minipage}{\textwidth} \tiny Note: Some descriptive text here. \end{minipage}
>
> I do not think this is possible. You have to realise that Org does not
> aim to support everything you can do with a backend natively. One of
> the primary reasons for that is the backend agnostic abstraction
> provided by Org.
I have seen some way of doing things like this. See section 13.3 at
http://orgmode.org/worg/org-tutorials/org-latex-export.html
I can't get it to work though. Will keep trying.
>
> When in need of specific needs like this, I resort to writing LaTeX
> natively.
I guess one thing about org-mode is that it is addictive. Afterall, if
it is something to do with manipulating text, it ought to be possible
:)
There is also a reason for not doing it natively in latex even if the
org-mode solution is somewhat round-about. I am writing a research
paper using orgmode, with embedded R source blocks in it. I do not
mind embedding some latex source block into it but I would not like to
edit an exported latex file. After all, in the end, the objective is
to be able to have an org file which produces a full paper when exported.
Vikas
next prev parent reply other threads:[~2013-04-16 11:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 8:06 Latex export of tables Vikas Rawal
2013-04-14 23:29 ` Suvayu Ali
2013-04-16 11:56 ` Vikas Rawal [this message]
2013-04-16 13:13 ` Thomas Alexander Gerds
2013-04-16 17:39 ` Suvayu Ali
2013-04-16 20:07 ` Thomas S. Dye
2013-04-16 21:39 ` Suvayu Ali
2013-04-16 23:45 ` Thomas S. Dye
2013-04-17 10:21 ` Myles English
2013-04-16 22:10 ` Best practices for literate programming [was: Latex export of tables] Vikas Rawal
2013-04-17 0:06 ` Thomas S. Dye
2013-04-18 16:53 ` Rasmus
2013-04-18 17:59 ` Aaron Ecay
2013-04-18 18:25 ` Rasmus
2013-04-18 19:48 ` Achim Gratz
2013-04-18 19:42 ` Thomas S. Dye
2013-04-21 17:25 ` Rasmus Pank Roulund
2013-04-17 6:39 ` Suvayu Ali
2013-04-17 9:55 ` Rainer M. Krug
2013-04-17 10:10 ` Suvayu Ali
-- strict thread matches above, loose matches on Subject: below --
2009-10-13 10:35 LaTeX export of tables Francesco Pizzolante
[not found] ` <873a5nr379.fsf-djc/iPCCuDYQheJpep6IedvLeJWuRmrY@public.gmane.org>
2009-10-19 11:58 ` Francesco Pizzolante
2009-10-19 18:05 ` Darlan Cavalcante Moreira
2009-10-20 8:17 ` Carsten Dominik
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=20130416115619.GA12405@panahar \
--to=vikaslists@agrarianresearch.org \
--cc=emacs-orgmode@gnu.org \
--cc=fatkasuvayu+linux@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).