From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: template for writing Emacs manuals in Org
Date: Tue, 17 May 2016 14:56:33 -0400 [thread overview]
Message-ID: <87futgikda.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: m237pg7cr6.fsf@tsdye.com
"Thomas S. Dye" <tsd@tsdye.com> writes:
> Aloha Nicolas,
>
> Nicolas Goaziou writes:
>
>> "Thomas S. Dye" <tsd@tsdye.com> writes:
>>
>>> Nicolas Goaziou writes:
>>>>
>>>> Once the manual is up-to-date, we might consider moving it to doc/ in
>>>> main distribution.
>>>
>>> IIRC, Bastien doesn't like this idea.
>>
>> Really? I admit I would be surprised. Do you recall why so, or do you
>> have any reference about it?
>
> That is all I remember from three years ago, but it's not really
> important.
>
> Looking ahead, the question is whether or not maintaining the
> documentation in Org, rather than texinfo, is a possibility, and, if so,
> what are the conditions under which that change will or will not happen?
>
> What are Bastien's expectations and preferences?
>
I believe the main obstacle is that the emacs policy requires a texinfo
manual for all its component parts. If that can be generated
automatically from the org document, then any objections probably
disappear. Of course, Bastien might object to the extra effort required
to do the conversion, but if the conversion is indeed completely
automatic (or, perhaps more likely, a volunteer can be found to take
care of the conversion and any problems that might arise), then he might
be amenable to it. But it would be an extra step required at release
time and would require some coordination.
--
Nick
next prev parent reply other threads:[~2016-05-17 18:56 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 [this message]
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
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=87futgikda.fsf@alphaville.usersys.redhat.com \
--to=ndokos@gmail.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 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.