Re: [Chicken-users] ideas

[Perry E. Metzger]

Peter Keller <address@hidden> writes:
> As for plain text, honestly, I've never wanted any of the manuals I read
> in plain text. I usually print them out or look at the HTML conversion
> since HTML gives you the searching ability you woulda gotten under
> plain text, except you get tables and stuff, and if you care you can use
> 'lynx/links' to read it on vt100.

I find "emacs" is a fine documentation reader and gives me excellent
searching ability. :)

I rather like doing things this way. I find the cut and paste for
examples between the documentation window in emacs and the window I'm
working on is particularly pleasant.

Of course, TeXinfo will also give you HTML and nicely formatted
postscript or PDF.

> > Given all this, it seems Texinfo might be the right thing, at least
> > for the main manual. I still favor having calls documented with man
> > pages but that's another story.
> 
> Well, my point is, why use a derivative of (La)Tex, which scribe and
> texinfo are, if you could just use LaTeX itself with all of the features
> it has not being limited in any way. I mean, if you replace @ with \
> in Texinfo, it basically IS TeX--but limited.

You can escape to "normal" TeX if you like. I agree that it is more
limited than one would like, but it seems in many ways like the path
of least resistance, for good or ill. :(


-- 
Perry E. Metzger                address@hidden
--
"Ask not what your country can force other people to do for you..."