On Sun, Jul 14, 2002 at 01:31:59PM -0700, Sean 'Shaleh' Perry wrote:
> Coupling this work with a comprehensive list of undocumented modules, perhaps
> getting them documented along the way would really be a great idea. The
> question really boils down to whether the upstream want this to happen or
>
>> Converting a hack to another hack with no strong reason nor fun is not
>> exactly what I dream of every night.
>>
>> So, I am not sure that such a conversion would be worth the time spent.
>> If despite all of this you still want to tackle on this task and have
>> some ELisp questions (I thi
Florent Rougon writes:
> Bastian Kleineidam <[EMAIL PROTECTED]> wrote:
>
> > python2.1 (2.1.3-3) from sid
> > py2texi.el is a generated file
> > it is included in debian/patches/info-docs.dpatch
> > the fixinfo.el is replaced by it, fixinfo.el is not run.
>
> OK, py2texi and fixinfo have nothing
Hi,
On Wed, Jun 26, 2002 at 10:09:43PM -0700, Sean 'Shaleh' Perry wrote:
> Do you think there would be opposition to using say docbook?
Lets find out.
http://sourceforge.net/tracker/index.php?func=detail&aid=574465&group_id=5470&atid=355470
Greetings,
--
.~.
/V\ Bastian Kleineidam ยท J
> BTW, if you're looking for a really nice and practical solution, you
> should convince/help Python documentation team to switch to another
> source format. LaTeX is really bad choice for such a documentation.
>
this sounds like a great idea, LaTeX is really not meants as a one to many
format.
> "S'P" == Sean 'Shaleh' Perry <[EMAIL PROTECTED]> writes:
S'P> The problem is we now have a piece of a fairly common package
S'P> using script(s) in a language few understand. So if you get
S'P> hit by a bus someone WILL have to reverse engineer that script.
S'P> This is the
Florent Rougon <[EMAIL PROTECTED]> wrote:
> immutable, so repeatedly inserting/replacing small strings into the
> whole document's string, having all the includes recursively
> expanded would be quite bad) or something like (c)StringIO. But then
> you have to do heavy regexp matchi
On 26-Jun-2002 Florent Rougon wrote:
> "Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> wrote:
>
>> The problem is we now have a piece of a fairly common package using
>> script(s) in a language few understand. So if you get hit by a bus
>> someone WILL have to reverse engineer that script. This is the
"Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> wrote:
> The problem is we now have a piece of a fairly common package using
> script(s) in a language few understand. So if you get hit by a bus
> someone WILL have to reverse engineer that script. This is the same
Well, I guess you mean "py2texi.el's up
>
> Converting a hack to another hack with no strong reason nor fun is not
> exactly what I dream of every night.
>
> So, I am not sure that such a conversion would be worth the time spent.
> If despite all of this you still want to tackle on this task and have
> some ELisp questions (I think it
Bastian Kleineidam <[EMAIL PROTECTED]> wrote:
> python2.1 (2.1.3-3) from sid
> py2texi.el is a generated file
> it is included in debian/patches/info-docs.dpatch
> the fixinfo.el is replaced by it, fixinfo.el is not run.
OK, py2texi and fixinfo have nothing in common.
> Dont know, seems that a l
On Sun, Jun 23, 2002 at 12:07:43PM +0200, Florent Rougon wrote:
> Bastian Kleineidam <[EMAIL PROTECTED]> wrote:
> Which python2.1 do you have? It is the same in woody and sid (2.1.3-3)
> and doesn't seem to contain such a file:
python2.1 (2.1.3-3) from sid
py2texi.el is a generated file
it is inc
Hi,
I was surprised to see emacs21 in the build depends of python2.1.
Seems that the only thing is the py2texi.el utility that requires
emacs.
As I dont know any Lisp, is there anyone out there to convert this
beast to Python or Perl? I dont like to install emacs to compile
python :)
Greetings
13 matches
Mail list logo
