| cvs.texinfo:@deffn Command {cvs add} [@code{-k} kflag] [@code{-m}
| message] files @dots{}
| cvs.texinfo:@end deffn
| cvs.texinfo:@deffn Command {cvs remove} [options] files @dots{}
| cvs.texinfo:@end deffn
| cvs.texinfo:@deffn Command {cvs annotate} [@code{-flR}] [@code{-r
| rev}|@code{-D date}] files @dots{}
| cvs.texinfo:@end deffn
| cvs.texinfo:@deffn Command {cvs watch on} [@code{-lR}] files
| @dots{}
| cvs.texinfo:@end deffn
| cvs.texinfo:@deffn Command {cvs watch off} [@code{-lR}] files
| @dots{}
| cvs.texinfo:@end deffn
| cvs.texinfo:@deffn Command {cvs watch add} [@code{-a} action]
| [@code{-lR}] files @dots{}
| cvs.texinfo:@end deffn
| cvs.texinfo:@deffn Command {cvs watch remove} [@code{-a} action]
| [@code{-lR}] files @dots{}
| cvs.texinfo:@end deffn
| cvs.texinfo:@deffn Command {cvs edit} [options] files @dots{}
| cvs.texinfo:@end deffn
| cvs.texinfo:@deffn Command {cvs unedit} [@code{-lR}] files @dots{}
| cvs.texinfo:@end deffn
| cvs.texinfo:@deffn Command {cvs watchers} [@code{-lR}] files
| @dots{}
| cvs.texinfo:@end deffn
| cvs.texinfo:@deffn Command {cvs editors} [@code{-lR}] files @dots{}
|
| cvs.texinfo:@end deffn
|
| Which is the same order the entries appear in cvs.fns. Glancing at the
| texinfo manual reveals that `Command' is a category argument and not
| literal. Will that do the trick?
In fact it was my understanding that what you describe explains why
you have some content in .fn, not .fns. To get .fns, you need to use
the index somewhere.
Is there a command index somewhere? How is it created in the Texinfo file?
