Thomas Esser <[EMAIL PROTECTED]> writes: > > texdoc -l -s 'regular-expression-for-grep' > > > > This would be slower, of course, but it would help to have it as a > > fallback for situations like > > > > texdoc teTeX > > texdoc amsthm > > > > that fail only because the documentation file is called by a different > > name. > > amsthm is badly chosen, since it does not match amsthdoc.dvi :-) Anyway, > I have just implemented that -s feature (it does not need -l, it only > displays filenames).
I suppose you implemented something that searches through the file names? That is good, certainly, but what I wanted to suggest was an idea of having something that searched through file *contents*. And this would apply mainly for source forms like .tex or .dtx, since (at least as far as I know) we don't have free & fast tools for searching dvi files or pdf files. For example, the documentation for amsthm.sty consists of amsthm.dtx (technical commentary), amsthdoc.tex (for end users), and also an example file thmtest.tex. In the last case it is better for the user to look at thmtest.tex, or thmtest.tex + thmtest.dvi side by side, but not thmtest.dvi by itself, because it does not show how the examples were generated. I could change thmtest.tex so that the .dvi file showed both source code and examples, and maybe I will for the next release; but the dvi viewer I use most of the time is xdvi which does not support searching for strings, and that seems a fairly serious drawback of the dvi format, as things currently stand. > > I am willing to help work on some of these features but I wanted to ask first > > if some or all of them are already being addressed by others. > > Well, it was fun to implement these useful features myself :-) Thanks again for all your good work that has benefited so many people in the TeX community.
