From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: template for writing Emacs manuals in Org
Date: Tue, 17 May 2016 12:16:26 +0800 [thread overview]
Message-ID: <87inyd8gkl.fsf@ericabrahamsen.net> (raw)
In-Reply-To: m27fet741n.fsf@tsdye.com
"Thomas S. Dye" <tsd@tsdye.com> writes:
> Aloha Eric,
>
> Eric Abrahamsen writes:
>
>> "Thomas S. Dye" <tsd@tsdye.com> writes:
>>
>>> Rasmus writes:
>>>
>>>> Once upon a time Tom ported the Org manual. It's on his github, probably
>>>> under tsdye.
>>>
>>> https://github.com/tsdye/orgmanual
>>
>> Hey, that's perfect! Dunno if that's what I was remembering, but that's
>> exactly what I was after. Even better if it ends up in contrib/
>>
>> Off to copy and paste now...
>
> I hope you find it useful. Still, I'd be interested to see Oleh
> Krehel's approach. It is bound to be more sophisticated than mine.
Well, we can cobble something together :) Mostly I was interested in the
index macros -- Info manuals are far more useful with indexes, and to be
honest I was doing anything to avoid learning how to write texinfo.
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 (?).
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.
E
next prev parent reply other threads:[~2016-05-17 4:16 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 [this message]
2016-05-17 7:35 ` Rasmus
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
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=87inyd8gkl.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).