Mail Archives: djgpp-workers/1997/04/08/20:11:12
> I think what's there is very clear and concise. It would be good if
> some newbie(s) reads the stuff and comments on it, though, as people
> who know stuff are not the best to judge how it is described to
> newbies.
I've been privately pointing users with newbie-type questions to it,
if I think the guide will answer the question. Nobody has complained
yet.
> 1) ug/intro/installing.html says:
>
> I think the last sentence might be misleading. I suggest
> something like this instead:
I like yours better.
> 2) Descriptions of Unix programs (on installing.html): I suggest to
> pick the short descriptions from the latest FAQ (section 4.5).
> Listing programs like head, join, fold, tac, etc. won't tell
> anything to people who aren't Unix users. (Also, I don't think
I think you would have done a better job than I on that section.
> you should list the symlinks like `gdate' and `gmkdir', just list
> their usual names `date' and `mkdir'.)
I just did "unzip -v | grep .exe"
> 3) ug/basic/32bit.html says:
>
> All DJGPP programs are like "tiny" mode. There is no such
> thing as a "far pointer" in DJGPP.
I put in a note, but I hope it doesn't confuse people into thinking that
"far char *" is supported.
> There is also a typo above ("mode" instead of "model").
Actually, a thinko. It is what I intended, but it wasn't correct.
> 4) Also, it seems like most of the 32bit.html's wording is
> negative: "this doesn't work in DJGPP, that you can't do", etc.
OK, I think it has a better spin on it.
> 5) ug/basic/copy-redistribute.html:
>
> It should mention libiostream.a as non-LGPL'ed, and libgxx.a is
> actually libgpp.a.
Fixed.
> There's a typo here ("implment").
Fixed.
> *every* should be done with HTML tags.
Fixed.
> 6) ug/basic/protected.html should at least explain what a selector
> and descriptor are.
Try it now.
> > Also, I did add djgpp-workers to the mail archive searcher at
> > http://www.delorie.com/djgpp/mail-archives/
>
> Thanks, this works, but sometimes (probably when it doesn't find anything)
> it complains like so:
>
> Couldn't read word, got 0 bytes djgpp-workers.lst: Invalid argument
Hey, it's not perfect.
- Raw text -