From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Matt Price <moptop99@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: exporting zotxt or orgref links to HTML and ODF
Date: Tue, 27 Jan 2015 14:28:39 +0000 [thread overview]
Message-ID: <87zj948fhk.fsf@ucl.ac.uk> (raw)
In-Reply-To: <CAN_Dec_z8yNSWT7-N7VoqWZpPRNPuCXfc3yXhbBGfcFZ3bJEvA@mail.gmail.com> (Matt Price's message of "Tue, 27 Jan 2015 08:12:18 -0500")
On Tuesday, 27 Jan 2015 at 08:12, Matt Price wrote:
> For me, the main issue with this route is that I don't understand LaTex at
> all, and it seems like there's a bit of a steep learning curve to get to a
> working set up. Maybe someone can recommend a good guide for starting out
> in LaTex? It does seem like somehting one should learn, I suppose.
There are many tutorials on the web. A simple "latex tutorial" web
search brings back many links. I can send you a couple of PDF documents
off-list, if you wish, of documents I have used in the past.
The original text by Leslie Lamport is also a very good starting point.
I do wonder, however, how much you need to know if you are using
org. In fact, you can probably learn a lot by looking at the LaTeX that
org produces... and many of us are happy to help with the odd org-LaTeX
issues that can arise!
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org release_8.3beta-726-gd34b80.dirty
next prev parent reply other threads:[~2015-01-27 14:28 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 16:29 exporting zotxt or orgref links to HTML and ODF Matt Price
[not found] ` <54C67E1A.8080706@law.lsu.edu>
2015-01-26 20:40 ` Matt Price
2015-01-26 21:53 ` Monroe, Will
2015-01-27 8:25 ` Eric S Fraga
2015-01-27 9:23 ` Christian Moe
2015-01-27 13:30 ` Rasmus
2015-01-27 13:51 ` Matt Price
2015-01-27 14:14 ` Rasmus
2015-01-27 18:17 ` John Kitchin
2015-01-27 15:24 ` Christian Moe
2015-01-27 17:24 ` Richard Lawrence
2015-01-27 17:50 ` Rasmus
2015-01-28 4:09 ` Richard Lawrence
2015-01-27 20:01 ` Christian Moe
2015-01-27 22:08 ` Rasmus
2015-01-27 22:15 ` John Kitchin
2015-01-28 2:10 ` Matt Price
2015-01-28 6:37 ` Erik Hetzner
2015-02-01 4:20 ` Erik Hetzner
2015-01-27 12:01 ` Vikas Rawal
2015-01-27 13:12 ` Matt Price
2015-01-27 14:28 ` Eric S Fraga [this message]
2015-01-27 13:31 ` Albert Krewinkel
[not found] ` <m2vbjsvay0.fsf@christianmoe.com>
[not found] ` <CAN_Dec9qBWWWgdX+wQhdgbthMg_ZOgbOMFoXFixSc4=74avMjw@mail.gmail.com>
2015-01-27 14:41 ` Christian Moe
[not found] <CAMfbzvA83eSWe79Ot=yX+_s_g33gpLnP-z+zQ52QFJm+iJTR+Q@mail.gmail.com>
2015-01-28 21:53 ` Matt Price
2015-01-28 23:01 ` John Kitchin
2015-01-29 1:34 ` Matt Price
2015-01-29 1:48 ` John Kitchin
[not found] ` <CAN_Dec80Su+5Nh5mqNxBXsLu_gm93aY77B=2Zrce-TJ1RPKCig@mail.gmail.com>
2015-01-29 13:06 ` John Kitchin
2015-01-29 13:11 ` Vikas Rawal
2015-01-29 13:24 ` John Kitchin
2015-01-29 13:39 ` Vikas Rawal
2015-01-29 13:09 ` John Kitchin
2015-01-29 2:26 ` 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=87zj948fhk.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=moptop99@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).