Dear Georg,
> personally, I would have searched the "Sage Developers Guide" for
> information on how "sage -t" works. And if there is nothing to find,
> I'd look directly at the code (.../local/bin/sage-test).
So would I. The wiki is only temporary... See my comments below.
> Admittedly, I
> rarely use the Wiki, because I do not feel comfortable with it --- nor
> do I always have internet access when working with Sage.
>
> But a local Sage install does include a lot of eye-candy documentation
> I like to use.
>
> Proposal:
> Do move (better still: copy) the contents of your Wiki-entry to the
> "Sage Developers Guide".
That's the ultimate goal. However, I don't have a broad view of the doc
system. Right now the page is a only a bunch of tips and tricks gathered on
irc and this very mailing list. It is not at all in a stable state and I don't
feel expert enough to write such a text in the guide, not speaking about my
bad English. In particular, I'd like some expert of the build system and
ReST/sphinx to check that the tips I give are correct. Moreover, aside for the
tricks in my opinion the most important thing on the page are link to short
and extended description on the format that I don't want to (even can't ?)
copy in the Devel Guide.
I was hoping that starting the wiki page, I could get some help on expanding
it, or at least get some re-reader. I have chosen the wiki as a communication
mean to build such a doc because anyone can edit and improve it. But it seems
that as a consequence no-one does :) The trac / patch system seems not to be
interactive enough... Any suggestion ?
Cheers,
Florent
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
