From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: template for writing Emacs manuals in Org
Date: Tue, 17 May 2016 09:35:32 +0200 [thread overview]
Message-ID: <87futh6ssb.fsf@gmx.us> (raw)
In-Reply-To: 87inyd8gkl.fsf@ericabrahamsen.net
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> What might be nice to have in contrib is an exporter derived from the
> current texinfo exporter, but specifically set up for Gnu project
> manuals: so it does the copyright header, and index macros, and maybe
> even the proper DIR integration (?).
Maybe a "GNU template" would be enough? (template as in C-e #).
> I remember where I originally saw this: it was a long thread on
> emacs.devel about moving documentation to HTML, which struck me as a
> terrible idea. I think Org was raised as a way of lowering the barrier
> to writing texinfo manuals for packages, so that we get the best of both
> worlds: write in Org, read in Info. I think it would be a great idea to
> facilitate that, if possible.
There's a recap here:
https://lwn.net/Articles/625072/
Rasmus
--
To err is human. To screw up 10⁶ times per second, you need a computer
next prev parent reply other threads:[~2016-05-17 7:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-14 7:21 template for writing Emacs manuals in Org Eric Abrahamsen
2016-05-16 17:37 ` Kaushal Modi
2016-05-16 17:55 ` John Hendy
2016-05-16 18:08 ` Rasmus
2016-05-16 18:40 ` Thomas S. Dye
2016-05-16 20:02 ` Nicolas Goaziou
2016-05-16 21:33 ` Thomas S. Dye
2016-05-17 5:52 ` Nicolas Goaziou
2016-05-17 14:44 ` Thomas S. Dye
2016-05-17 15:37 ` Nicolas Goaziou
2016-05-17 18:36 ` Thomas S. Dye
2016-05-17 18:56 ` Charles C. Berry
2016-05-17 18:56 ` Nick Dokos
2016-05-18 9:21 ` Rasmus
2016-05-18 14:56 ` Jonathan Leech-Pepin
2016-05-18 16:20 ` Nicolas Goaziou
2016-05-18 16:43 ` Rasmus
2016-05-17 0:23 ` Eric Abrahamsen
2016-05-17 3:32 ` Thomas S. Dye
2016-05-17 4:16 ` Eric Abrahamsen
2016-05-17 7:35 ` Rasmus [this message]
2016-05-17 8:34 ` Eric Abrahamsen
2016-05-17 13:24 ` Phillip Lord
2016-05-18 23:59 ` Ciaran Mulloy
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=87futh6ssb.fsf@gmx.us \
--to=rasmus@gmx.us \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.