From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Latex export of tables
Date: Tue, 16 Apr 2013 23:39:17 +0200 [thread overview]
Message-ID: <20130416213917.GA9183@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <m1bo9e9r41.fsf@poto.westell.com>
Hey Tom,
On Tue, Apr 16, 2013 at 10:07:26AM -1000, Thomas S. Dye wrote:
> Aloha all,
>
> Jumping in here with apologies :)
Isn't that why we discuss on mailing lists, so that people can jump in
;).
> > I'm suggesting this because if you continue on this path, i.e. litter
> > your Org file with hacks, soon you will end up with an extremely fragile
> > and complicated Org project. I have been down that road while writing
> > my thesis. At one point I realised the problem and made the decision to
> > split things into two kinds of files: static content (document
> > structuring, text, plots, etc), and dynamic content (babel, TikZ blocks
> > that generate tables, plots, figures, etc used by the static content
> > files). It is still reproducible research, but modular and less hacky
> > (hence more stable).
>
> The path to a fragile and complicated Org project is well-worn, I've
> been down it too many times myself. The habits I've developed over time
> have helped, but I think they are less systematic than what you've
> devised. I'd love to see some notes on your solution as a brief tutorial
> or an expanded FAQ on Worg. I'll be happy to contribute or help if you
> find time to do something like this.
Actually, I am working on a workflow for large writing projects, my PhD
thesis in this case :-p. What I have in mind is have a Makefile based
build system that uses `emacs --batch' to export to LaTeX and html. The
images are generated separately using babel blocks or standalone TeX
files with TikZ code. I intend to make pdf images for LaTeX and convert
them to png/svg with imagemagick/inkscape. Of course all of this is
still a pipe dream; if I get it working, I'll definitely write a Worg
page on it. Of course it will be great if people with interesting ideas
pitch in :). I expect to have an early working environment in a couple
of months.
:)
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2013-04-16 21:39 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
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 [this message]
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=20130416213917.GA9183@kuru.dyndns-at-home.com \
--to=fatkasuvayu+linux@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.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).