From: Adam Thornton <athornton@gmail.com>
To: "Seth J. Morabito" <web@loomcom.com>,
The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] eqn
Date: Mon, 7 Oct 2019 12:14:10 -0700 [thread overview]
Message-ID: <CAP2nic0pd6htp__6Y7o0Won4fb7gFwF-rpgfWN4qGrW+tOfAMA@mail.gmail.com> (raw)
In-Reply-To: <87v9t0tqjq.fsf@loomcom.com>
[-- Attachment #1: Type: text/plain, Size: 1565 bytes --]
And just in case you didn't know about it....
https://github.com/yjwen/org-reveal
This converts org-mode docs to reveal.js presentations.
https://athornton.github.io/Jupyter-PCW-2019/ is an example
On Mon, Oct 7, 2019 at 10:36 AM Seth J. Morabito <web@loomcom.com> wrote:
>
> U'll Be King of the Stars writes:
>
> > On 04/10/2019 15:57, aksr wrote:
> >
> > [1] LaTeX is excellent compared to Markdown. You can build a career
> > on top of it but not on top of Markdown. I don't even consider MD a
> > proper markup format, aside from the simplest cases such as writing
> > introductory README.md files. The only thing that La/TeX and MD have
> > in common for me is that they are both intolerable without Emacs modes
> > (AUCTeX and markdown-down.el).
>
> [With sincere apologies for taking this slightly more off-topic, but
> still within the realm of the vaguely UNIX-y...]
>
> This is one of the reasons I live in Emacs, too. I make extensive use of
> org-mode, not only for organizing my life, but also for generating
> documentation. Org-mode has extensive native support for LaTeX markup,
> and exporting marked-up documents to PDF via LaTeX. Additionally, of
> course, it can export to HTML and even Markdown if you like. But the
> LaTeX support makes it killer.
>
> In fact, veering back on-topic, there is even a mode to export Org-mode
> files to Groff Memorandum Macros documents[1]! It's a pretty powerful
> system.
>
> -Seth
>
>
> [1] https://orgmode.org/worg/exporters/ox-groff.html
> --
> Seth Morabito
> Poulsbo, WA, USA
> web@loomcom.com
>
[-- Attachment #2: Type: text/html, Size: 2341 bytes --]
next prev parent reply other threads:[~2019-10-07 19:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 4:20 Larry McVoy
2019-10-04 4:35 ` Dave Horsfall
2019-10-04 5:12 ` George Michaelson
2019-10-04 13:43 ` Nemo
2019-10-04 14:57 ` aksr
2019-10-04 15:52 ` U'll Be King of the Stars
2019-10-04 16:12 ` Jon Forrest
2019-10-04 17:24 ` Adam Thornton
2019-10-04 18:55 ` Kurt H Maier
2019-10-04 17:43 ` Steffen Nurpmeso
2019-10-06 8:03 ` arnold
2019-10-04 19:02 ` Larry McVoy
2019-10-07 17:26 ` Seth J. Morabito
2019-10-07 19:14 ` Adam Thornton [this message]
2019-10-08 21:11 ` Seth Morabito
2019-10-04 19:25 ` Fabio Scotoni
2019-10-05 1:59 Doug McIlroy
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP2nic0pd6htp__6Y7o0Won4fb7gFwF-rpgfWN4qGrW+tOfAMA@mail.gmail.com \
--to=athornton@gmail.com \
--cc=tuhs@tuhs.org \
--cc=web@loomcom.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.
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 NNTP newsgroup(s).