On 1 April 2013 04:23, Simon Toedt <[email protected]> wrote:
> On Tue, Mar 26, 2013 at 5:34 PM, Cedric Blancher
> <[email protected]> wrote:
>> On 26 March 2013 11:01, Simon Toedt <[email protected]> wrote:
>>> I have a request:
>>> While AST and UWIN are awesome it'll be nice to have more detailed,
>>> uptodate documentation with examples. Please don't be offended but
>>> there are many great things in AST and UWIN which are little known
>>> because the documentation is, well, very RISC-like.
>>
>> Well, what can I say? David and Glenn are researchers and run AST and
>> UWIN like a research project. What's needed here is someone else who
>> writes documentation from a programmers pov.
>
> Well, what can I say about this? The documents in /usr/doc leave a
> distinctive WOW feeling. But its not a positive one. There is no way
> to read them from the console when there is no terminal browser like
> w3m installed. index.html contains lots of dead links, e.g. the first
> link for C/C++ compilers referencing /usr/doc/compilers.html is DEAD.
> There's dead documentation links all over the place. And from there it
> goes all down the drain. The hallmark might be the "Feedback survey"
> which goes to file:///~gsf/cgi-bin/uwin.cgi. WOW
>
> David, Glenn and the others working on UWIN: Please find someone to
> write end user documentation. Or hire one.

If you start fixing UWIN documentation please verify these items:
- man ksh fails because there's no groff. That's a bit silly because
ksh93 is actually one of the highlights of UWIN
- man vi doesn't work. Neither do the vi cursor keys in the Windows
console. There's no emacs either and therefore UWIN doesn't ship with
a usable editor by default. Bummer.
- man Intro doesn't give an overview about what's there and how stuff
works. Any other Linux/Unix have Intro(1,2,3,4,...) manual pages. UWIN
has none.
The list can be continued endlessly... ;(

Ced
-- 
Cedric Blancher <[email protected]>
Institute Pasteur
_______________________________________________
ast-developers mailing list
[email protected]
http://lists.research.att.com/mailman/listinfo/ast-developers

Reply via email to