From: Vikas Rawal <vikaslists@agrarianresearch.org>
To: Axel Kielhorn <org-mode@axelkielhorn.de>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Using Emacs, Org-mode and R for Research Writing in Social Sciences
Date: Thu, 15 May 2014 10:38:44 +0200 [thread overview]
Message-ID: <DA21CBD2-9ECD-45D7-9999-CA71F7A79BD9@agrarianresearch.org> (raw)
In-Reply-To: <388EA2D8-0DBA-4FE1-A954-508EEF25BFCD@axelkielhorn.de>
>>>
>>
>> May be I should specify the packages that are being called, so the user can make sure those are installed or modify the config file. But I prefer the basic set of LaTeX packages being called by default rather than being added in every file.
>
> This will be a problem when one of your collaborators doesn't use your config files.
> There are many packages for tabular/table environments.
> Having them in the document gives a strong hint that there is something different that may collide with the packages another user prefers. (No-one can agree on a basic set of LaTeX packages:-)
>
> If you keep them in the configuration file, the user has to extract the relevant information
>
> (setq org-latex-default-packages-alist …)
>
> from your configuration and add it to their configuration file.
>
> You can always supply a template file with all the relevant
> +LaTeX_HEADER
> definitions.
>
> You can even have lines like
>
> #+LaTeX_HEADER: \usepackage{tabulary} % provides column specification LCRJ
> #+LaTeX_HEADER: \usepackage{threeparttable} % A table with cation and notes
> #+LaTeX_HEADER: \renewcommand{\TPTminimum}{\linewidth} % configure threeparttable
> #+Latex_HEADER: %\usepackage{tgschola} % enable to use the Schola font
> #+Latex_HEADER: %\usepackage{tgbonum} % enable to use the Bonum font
> #+Latex_HEADER: %\usepackage{tgpagella} % enable to use the Pagella font
> #+Latex_HEADER: \usepackage[urw-garamond]{mathdesign} \linespread{1.0609}
This may be a better solution. We could even provide a separate file with sample lines that need to go at the top, which can be modified if needed, to be called in using #+INCLUDE: into a document.
Since Suvayu has offered to have a go at modifying the document for Worg, I would wait for him to do what he thinks may be best.
Vikas
next prev parent reply other threads:[~2014-05-15 8:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 12:57 Using Emacs, Org-mode and R for Research Writing in Social Sciences Vikas Rawal
2014-05-12 13:26 ` Suvayu Ali
2014-05-12 19:36 ` Vikas Rawal
2014-05-12 21:00 ` Thomas S. Dye
2014-05-13 17:48 ` Vikas Rawal
2014-05-13 18:15 ` John Hendy
2014-05-13 18:40 ` Vikas Rawal
2014-05-14 14:19 ` Suvayu Ali
2014-05-14 16:02 ` Vikas Rawal
2014-05-13 19:55 ` Thomas S. Dye
2014-05-13 18:01 ` Eric S Fraga
2014-05-13 18:52 ` Vikas Rawal
2014-05-14 3:38 ` Using Emacs, Org-mode and R for Research Writing in Social Sciencess Ken Mankoff
2014-05-14 7:00 ` Vikas Rawal
2014-05-14 9:02 ` Christopher Witte
2014-05-14 10:15 ` Vikas Rawal
2014-05-14 13:23 ` Ken Mankoff
2014-05-14 13:27 ` Vikas Rawal
2014-05-14 13:27 ` Vikas Rawal
2014-05-14 14:07 ` Using Emacs, Org-mode and R for Research Writing in Social Sciences Axel Kielhorn
2014-05-14 16:51 ` Vikas Rawal
2014-05-14 18:39 ` Axel Kielhorn
2014-05-15 4:49 ` Vikas Rawal
2014-05-15 8:18 ` Axel Kielhorn
2014-05-15 8:38 ` Vikas Rawal [this message]
2014-05-15 11:57 ` Axel Kielhorn
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=DA21CBD2-9ECD-45D7-9999-CA71F7A79BD9@agrarianresearch.org \
--to=vikaslists@agrarianresearch.org \
--cc=emacs-orgmode@gnu.org \
--cc=org-mode@axelkielhorn.de \
/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).