unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Georg Brandl <g.brandl@gmx.net>
To: emacs-devel@gnu.org
Subject: Re: Using Git to manage your Emacs changes
Date: Sun, 25 Apr 2010 18:47:07 +0200	[thread overview]
Message-ID: <hr1rn1$lft$1@dough.gmane.org> (raw)
In-Reply-To: <87vdbghcgy.fsf@notengoamigos.org>

Am 24.04.2010 21:33, schrieb Jason Earl:

>>    Does it really matter that much?  I am certain that their are other
>>    parts of the GNU system (like, perhaps, TeX), where the hackers in
>>    question don't follow GNU policies.  In fact, Bazaar doesn't
>>    completely follow GNU policies (no texinfo documentation, and no
>>    real plans to generate it either).
>>
>> While TeX is part of the GNU system, it is not part of the GNU
>> project.  I hope that bazaar will adpot texinfo manuals soon, I think
>> someone was working on that.
> 
> Bazaar has this marked as a bug (wishlist), but they are essentially
> waiting for someone to come up with a way to make texinfo documentation
> from their existing rst documentation.  In fact, it could easily be
> argued that they are moving farther away from texinfo as they have moved
> from simply requiring docutils to requiring the more complicated sphinx
> documentation build system.

As the Sphinx maintainer and at the same time avid Emacs user, I feel I have
to chime in here.

I wouldn't say that using Sphinx is moving farther away from texinfo.  As
far as I know, there is no docutils writer for texinfo right now.
Most of the work of supporting Texinfo as a Sphinx output format would be
required for docutils as well, i.e. the conversion from a node tree to
Texinfo markup.

Additional overhead is only necessary for Sphinx' custom nodes, and for
determining how to interpret cross-references and how to map the multi-file
structure of a Sphinx project to the output.  This is simply stuff that
isn't supported by "plain" docutils but has to be supported by Texinfo,
so the mapping shouldn't be hard.

> On the bright side, if someone could modify Sphinx to generate texinfo
> then I would get my Python documentation back in texinfo format as well.

I'm absolutely not opposed to supporting Texinfo.  Anyone who wants to take
this on will have my support, but as with many feature requests, I do not
have the time to do it myself.

Georg

-- 
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor either indent thou
two, excepting that thou then proceed to four. Tabs are right out.





  parent reply	other threads:[~2010-04-25 16:47 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-07 19:23 Using Git to manage your Emacs changes John Wiegley
2010-04-07 19:32 ` David Reitter
2010-04-07 20:25   ` John Wiegley
2010-04-07 21:22     ` David Reitter
2010-04-21 17:30   ` Ted Zlatanov
2010-04-21 18:12     ` David Reitter
2010-04-21 19:29       ` John Wiegley
2010-04-21 20:42         ` Eli Zaretskii
2010-04-22  7:17           ` John Wiegley
2010-04-22  9:41             ` Lennart Borgman
2010-04-22 10:28               ` Andreas Schwab
2010-04-22 11:09                 ` Lennart Borgman
2010-04-22 11:29                   ` Andreas Schwab
2010-04-22 16:20                     ` endless version control debates [was Re: Using Git to manage your Emacs changes] Glenn Morris
2010-04-22 17:02                       ` endless version control debates Óscar Fuentes
2010-04-22 17:07                       ` endless version control debates [was Re: Using Git to manage your Emacs changes] Leo
2010-04-22 17:52                         ` Chad Brown
2010-04-22 19:16                           ` Andreas Schwab
2010-04-22 20:09                             ` Chad Brown
2010-04-23  2:50                               ` endless version control debates Miles Bader
2010-04-22 20:16                           ` endless version control debates [was Re: Using Git to manage your Emacs changes] Leo
2010-04-22 20:46                             ` Eli Zaretskii
2010-04-22 21:10                             ` Jeff Clough
2010-04-22 10:40               ` Using Git to manage your Emacs changes Miles Bader
2010-04-23  8:38                 ` Juri Linkov
2010-04-23  9:29                   ` Ævar Arnfjörð Bjarmason
2010-04-24 13:20                   ` Richard Stallman
2010-04-24 15:27                     ` Jason Earl
2010-04-24 15:45                       ` Ævar Arnfjörð Bjarmason
2010-04-24 17:10                       ` Alfred M. Szmidt
2010-04-24 19:33                         ` Jason Earl
2010-04-24 20:33                           ` Alfred M. Szmidt
2010-04-24 20:36                           ` Eli Zaretskii
2010-04-24 21:54                             ` Jason Earl
2010-04-25  8:26                             ` Stephen J. Turnbull
2010-04-27 20:59                             ` Karl Fogel
2010-04-25 16:47                           ` Georg Brandl [this message]
2010-04-26 14:33                       ` Richard Stallman
2010-04-26 17:35                         ` Eli Zaretskii
2010-04-21 22:16         ` Andreas Schwab
2010-04-07 20:53 ` Giuseppe Scrivano
2010-04-07 20:37   ` Thierry Volpiatto
2010-04-08 22:27     ` John Wiegley
2010-04-08 22:43       ` Jonas Bernoulli
2010-04-09  6:04       ` Thierry Volpiatto
2010-04-08 16:57 ` Ken Raeburn

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='hr1rn1$lft$1@dough.gmane.org' \
    --to=g.brandl@gmx.net \
    --cc=emacs-devel@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.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).