From: "Saša Janiška" <gour@atmarama.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-mode markup vs rst for general content
Date: Fri, 10 Mar 2017 16:21:53 +0100 [thread overview]
Message-ID: <874lz1nomm.fsf@atmarama.com> (raw)
In-Reply-To: bc565af8-58eb-a833-e1ce-94ae76a8bcff@gmail.com
Alan L Tyree <alantyree@gmail.com> writes:
> I have also written in rst: it is a slightly richer language out of
> the box with provisions for sidebars, cautions, etc, but unless you
> really need those things, I would stick with org-mode. I find the
> syntax of rst to be very fiddly. Most of the special effects can be
> obtained with css in any case.
Thank you.
> Org-mode for nearly everything else, but if you need more, go on to
> LaTeX.
Thanks a lot! Yeah, I did some books in the past using LyX/LaTeX when I
wanted high-quality output, so that option is always on here…in the
meantime I just want something mroe easy for authoring and it looks that
org-mode is good enough for such purpose…
> This may be more than you wanted to know :-).
Not at all. ;)
Sincerely,
Gour
--
next prev parent reply other threads:[~2017-03-10 15:22 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 [this message]
[not found] ` <e047c50c99ba4e8ba5ccfb4029b5aabc@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-10 9:09 ` Eric S Fraga
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=874lz1nomm.fsf@atmarama.com \
--to=gour@atmarama.com \
--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).