From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: emacs-orgmode@gnu.org
Subject: Re: org-mode markup vs rst for general content
Date: Fri, 10 Mar 2017 09:09:02 +0000 [thread overview]
Message-ID: <87o9x9sdld.fsf@ucl.ac.uk> (raw)
In-Reply-To: <e047c50c99ba4e8ba5ccfb4029b5aabc@HE1PR01MB1898.eurprd01.prod.exchangelabs.com> (Alan L. Tyree's message of "Thu, 9 Mar 2017 23:27:47 +0000")
[-- Attachment #1: Type: text/plain, Size: 551 bytes --]
On Thursday, 9 Mar 2017 at 23:27, Alan L Tyree wrote:
[...]
> I would say Markdown if you are collaborating with someone not familiar
> with Emacs. The Pandoc version will do a surprising amount. Org-mode
> for nearly everything else, but if you need more, go on to LaTeX.
Excellent summary.
I've been writing technical articles and funding proposals fully in org
(well, with some LaTeX assist using org export directives) for several
years now.
--
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.4-242-g2c27b8
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2017-03-10 13:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 9:14 org-mode markup vs rst for general content Saša Janiška
2017-03-09 18:50 ` John Kitchin
2017-03-09 19:17 ` Uwe Brauer
2017-03-09 20:38 ` John Kitchin
2017-03-09 21:40 ` Uwe Brauer
2017-03-09 22:03 ` Saša Janiška
2017-03-09 23:27 ` Alan L Tyree
2017-03-10 0:17 ` Samuel Wales
2017-03-10 0:49 ` Alan L Tyree
2017-03-10 1:25 ` Alan L Tyree
2017-03-10 11:15 ` Uwe Brauer
2017-03-10 14:47 ` John Kitchin
2017-03-10 16:14 ` Uwe Brauer
2017-03-10 16:24 ` Uwe Brauer
2017-03-10 17:06 ` John Kitchin
2017-03-10 17:41 ` Uwe Brauer
[not found] ` <fc159a4ac13f4e439d8007f9de98d495@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-10 17:57 ` Eric S Fraga
2017-03-10 15:21 ` Saša Janiška
[not found] ` <e047c50c99ba4e8ba5ccfb4029b5aabc@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-10 9:09 ` Eric S Fraga [this message]
2017-03-10 20:32 ` Samuel Wales
2017-03-10 22:28 ` Alan L Tyree
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=87o9x9sdld.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
/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).