From: Glenn Morris <rgm@gnu.org>
To: Bastien Guerry <bzg@gnu.org>
Cc: Achim Gratz <Stromeko@nexgo.de>,
Org Mode List <emacs-orgmode@gnu.org>,
Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: [RFC] Moving "manual.org" into core
Date: Sat, 03 Mar 2018 14:48:51 -0500 [thread overview]
Message-ID: <oa606d6iu4.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87bmg5xic2.fsf@bzg.fr> (Bastien Guerry's message of "Sat, 03 Mar 2018 16:57:33 +0100")
I'm sure this is an impressive technical achievement, but can I urge you
to raise this on emacs-devel first, because I think it's potentially
problematic.
I'm not entirely sure what you are proposing here. If the .org version
will become the "preferred form" for modification, it would eg need to
be in the Emacs repository (when the time comes), with suitable Makefile
rules for generating the final products from it, and distributed
correctly in releases. Emacs has got into trouble before in this area.
Bastien Guerry wrote:
> One of my worries was that moving toward editing a manual in .org
> does not match GNU developers good practices and habits, which are
> to edit .texi files. But as long as the .texi file exists I guess
> we can shake the habits by allowing to edit .org files, which are
> more convenient to read and write.
Speaking for myself, I don't want to learn yet another markup syntax for
one single Emacs manual. I find it unlikely that GNU projects will start
requiring Emacs to build their documentation. Although the GNU coding
standards do say:
https://www.gnu.org/prep/standards/html_node/GNU-Manuals.html#GNU-Manuals
Nowadays some other formats such as Docbook and Sgmltexi can be
converted automatically into Texinfo. It is ok to produce the Texinfo
documentation by conversion this way, as long as it gives good results.
so there's no problem from that aspect.
> But still: RMS recently raised the question on emacs-devel of
> whether using .rst for the GNU documentation would be better,
> so using .org for this purpose is not entirely hypothetical.
On the subject of rst, I can only find a topic two years ago that went
nowhere, and note in particular this:
http://lists.gnu.org/archive/html/emacs-devel/2016-02/msg00667.html
"We don't want to replace Texinfo as the source language"
Maybe I'm worried about nothing, but I do suggest asking on emacs-devel.
next prev parent reply other threads:[~2018-03-03 19:49 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-20 14:43 [RFC] Moving "manual.org" into core Nicolas Goaziou
2018-01-20 17:41 ` Achim Gratz
2018-01-20 18:15 ` Nicolas Goaziou
2018-01-20 18:36 ` Achim Gratz
2018-01-20 18:51 ` Nicolas Goaziou
2018-01-20 17:41 ` Thomas S. Dye
2018-01-22 10:51 ` Bastien Guerry
2018-01-22 13:48 ` Nicolas Goaziou
2018-01-22 15:30 ` Kaushal Modi
2018-01-22 16:02 ` Nicolas Goaziou
2018-01-22 17:00 ` Kaushal Modi
2018-01-22 17:20 ` Nicolas Goaziou
2018-01-22 17:31 ` Kaushal Modi
2018-01-22 19:52 ` Nicolas Goaziou
2018-01-23 15:19 ` Kaushal Modi
2018-01-23 16:30 ` Julius Dittmar
2018-01-23 16:33 ` Nicolas Goaziou
2018-01-23 16:37 ` Kaushal Modi
2018-01-22 16:35 ` Bastien Guerry
2018-01-22 16:53 ` Kaushal Modi
2018-01-22 16:35 ` Bastien Guerry
2018-01-22 16:31 ` Bastien Guerry
2018-01-22 17:03 ` Nicolas Goaziou
2018-01-23 8:07 ` org-adapt-indentation 'content (was Re: [RFC] Moving "manual.org" into core) Christian Moe
2018-03-06 19:01 ` Bastien Guerry
2018-01-22 19:04 ` [RFC] Moving "manual.org" into core Achim Gratz
2018-03-03 9:17 ` Nicolas Goaziou
2018-03-03 10:18 ` Bastien Guerry
2018-03-03 11:29 ` Nicolas Goaziou
2018-03-03 15:57 ` Bastien Guerry
2018-03-03 16:15 ` Joseph Vidal-Rosset
2018-03-03 19:48 ` Glenn Morris [this message]
2018-03-04 9:30 ` Bastien Guerry
2018-01-23 20:06 ` Thomas S. Dye
2018-01-22 13:54 ` Rasmus
2018-01-22 15:23 ` Kaushal Modi
2018-01-24 8:39 ` Yasushi SHOJI
2018-01-24 11:28 ` Nicolas Goaziou
2018-01-26 8:52 ` Yasushi SHOJI
2018-01-26 10:32 ` Nicolas Goaziou
2018-01-27 8:40 ` Yasushi SHOJI
2018-01-28 15:17 ` Nicolas Goaziou
2018-01-29 2:40 ` Yasushi SHOJI
2018-01-29 14:41 ` Nicolas Goaziou
2018-02-01 11:43 ` Yasushi SHOJI
2018-02-01 12:11 ` Yasushi SHOJI
2018-02-04 9:05 ` Nicolas Goaziou
2018-02-01 14:55 ` Nicolas Goaziou
2018-02-02 2:07 ` Yasushi SHOJI
2018-02-04 9:40 ` Nicolas Goaziou
2018-02-06 14:11 ` Yasushi SHOJI
2018-01-22 16:41 ` Thomas S. Dye
2018-01-23 8:08 ` Christian Moe
2018-01-23 21:00 ` Samuel Wales
2018-03-04 9:32 ` Bastien Guerry
2018-03-04 10:06 ` Nicolas Goaziou
2018-03-04 10:29 ` Bastien
2018-03-05 14:20 ` Nicolas Goaziou
2018-03-05 16:23 ` Kaushal Modi
2018-03-06 17:41 ` Bastien Guerry
2018-03-06 21:39 ` Achim Gratz
2018-03-05 18:08 ` Thomas S. Dye
2018-03-06 1:08 ` Bastien Guerry
2018-03-06 9:57 ` Thomas S. Dye
2018-03-06 11:55 ` Eric S Fraga
2018-03-06 17:39 ` Bastien
2018-03-06 18:45 ` Thomas S. Dye
2018-03-06 19:19 ` Bastien
2018-03-07 2:53 ` Thomas S. Dye
2018-03-05 19:01 ` Achim Gratz
2018-03-06 19:02 ` Bastien
2018-03-06 18:59 ` Bastien Guerry
[not found] ` <WM!6f8274ba0065f984ff76586f7cf117703ccda15adbb5042672b0d2695ee5ac6b367ee58f70aacbbc9c2b10eecb9672ea!@mailhub-mx3.ncl.ac.uk>
2018-03-05 16:22 ` Phillip Lord
2018-03-06 17:47 ` Bastien Guerry
2018-03-04 10:54 ` Bastien Guerry
2018-03-05 14:26 ` Nicolas Goaziou
2018-03-06 17:43 ` Bastien Guerry
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=oa606d6iu4.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=Stromeko@nexgo.de \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).