Re: Default postscript cleans miss *.cps *.fns.
Akim Demaille wrote:
"Tom" == Tom Tromey [EMAIL PROTECTED] writes:
"Akim" == Akim Demaille [EMAIL PROTECTED] writes:
Akim elsif (/^\@(syncode|print)index \w+ (\w*)/) { push
Akim @clean_suffixes, "$1s";
Tom Shouldn't that be "$2s" here?
Yes, definitely. Thanks!
Neither one worked. I grepped for "@(syncode|print)index" in CVS's
texinfo source and got the following:
@printindex cp
Are the two \w segments above a typo or maybe just not the general case?
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] CollabNet ( http://collab.net )
--
It'll take a miracle to get you out of Casablanca and the Germans have outlawed
miracles.
- Sydney Greenstreet as Senor Ferrari, _Casablanca_
Re: Default postscript cleans miss *.cps *.fns.
"Derek" == Derek R Price [EMAIL PROTECTED] writes:
Derek Akim Demaille wrote:
"Tom" == Tom Tromey [EMAIL PROTECTED] writes:
"Akim" == Akim Demaille [EMAIL PROTECTED] writes:
Akim elsif (/^\@(syncode|print)index \w+ (\w*)/) { push
Akim @clean_suffixes, "$1s";
Tom Shouldn't that be "$2s" here?
Yes, definitely. Thanks!
Derek Neither one worked. I grepped for "@(syncode|print)index" in
Derek CVS's texinfo source and got the following:
Derek @printindex cp
Derek Are the two \w segments above a typo or maybe just not the
Derek general case?
Arg, sorry, I wrote this way too hastily. Try this:
elsif (/^\@syncodeindex \w+ (\w*)/
|| /^\@printindex (\w+)/)
{
push @clean_suffixes, "$1s";
}
IIRC, you also had problems with fns. What does a `grep fn *texi*' gives?
Re: Default postscript cleans miss *.cps *.fns.
Akim Demaille wrote:
elsif (/^\@syncodeindex \w+ (\w*)/
|| /^\@printindex (\w+)/)
{
push @clean_suffixes, "$1s";
}
Yep. That works.
IIRC, you also had problems with fns. What does a `grep fn *texi*' gives?
Not much obviously useful, but you prompted me to look in the cvs.fns file.
Except for the first line, lines are of the form:
\entry {\code {command}}{index}
Where command is variable and index is a number. Using `fgrep -w "command"
*.texi*' reveals that each command has a corresponding texinfo command like
the following in the manual:
@deffn Command {command} ...
where `Command' (with a capital 'C') is a literal and ... varies. `fgrep -w
deffn' reveals:
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?
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] CollabNet ( http://collab.net )
--
It is as useless to argue with those who have renounced the use and authority
of reason as to administer medication to the dead.
- Thomas Jefferson
Re: Default postscript cleans miss *.cps *.fns.
| 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?
Re: Default postscript cleans miss *.cps *.fns.
"Tom" == Tom Tromey [EMAIL PROTECTED] writes: "Derek" == Derek R Price [EMAIL PROTECTED] writes: Derek FYI: the *.cps *.fns files are only being created for Derek cvs.texinfo. Tom Did we ever get some resolution for this? Nope, not yet. I'm downloading CVS to check this. Tom Akim, I recall you had a patch which removed a large number of Tom file extensions from the texinfo clean list. Perhaps these Tom should be added back? (I really don't know whether these can be Tom discovered automatically. I don't know that much about tex.) I really think we can discover them all. The thing is that index can be created at will. So unless you actually look for used indexes, you can never be sure you don't forget something.
Re: Default postscript cleans miss *.cps *.fns.
"Tim" == Tim Van Holder [EMAIL PROTECTED] writes: I really think we can discover them all. The thing is that index can be created at will. So unless you actually look for used indexes, you can never be sure you don't forget something. Tim Wouldn't using the -c option to texi2dvi solve this? That way, Tim the index files don't need to be cleaned in the first place. Unfortunately it is a `recent' addition: 4.0. In fact, I'd like to implement texi2dvi --clean-files, which is what Automake really needs, but that's too late for Automake (unless we start shipping texi2dvi...).
Re: Default postscript cleans miss *.cps *.fns.
"Derek" == Derek R Price [EMAIL PROTECTED] writes: Derek FYI: the *.cps *.fns files are only being created for cvs.texinfo. Did we ever get some resolution for this? Akim, I recall you had a patch which removed a large number of file extensions from the texinfo clean list. Perhaps these should be added back? (I really don't know whether these can be discovered automatically. I don't know that much about tex.) Tom
Re: Default postscript cleans miss *.cps *.fns.
Akim Demaille wrote: | Akim Demaille wrote: | | Could you `grep indexcode' your texi sources? Thanks! | | [dprice@empress doc]$ fgrep indexcode cvs.texinfo | [dprice@empress doc]$ Actually I meant _all_ your sources. And in fact, @include would be useful too. Sorry for the delay in response. I'm just catching up on this list and the cc went to the account I'm not using anymore. [dprice@empress doc]$ ls *.t*x* CVSvn.texi CVSvn.texi.in cvs.texinfo cvsclient.texi texinfo.tex [dprice@empress doc]$ egrep 'indexcode|@include' *.t*x* cvsclient.texi:@include CVSvn.texi cvs.texinfo:@include CVSvn.texi texinfo.tex:% @include fileinsert text of that file as input. texinfo.tex: % Read the included file in a group so nested @include's work. texinfo.tex:% they're defined in; @include reads the file inside a group. [dprice@empress doc]$ I wasn't sure whether you wanted texinfo.tex included and there wasn't much output, so I left it in. FYI: the *.cps *.fns files are only being created for cvs.texinfo. Derek -- Derek Price CVS Solutions Architect ( http://CVSHome.org ) mailto:[EMAIL PROTECTED] CollabNet ( http://collab.net ) -- Where are we going? And what's with this handbasket?
Default postscript cleans miss *.cps *.fns.
Building postscript docs from *.texi sources using the default automake targets, the dev version of CVS produces cvs.cps cvs.fns files as side effects. These files aren't removed by 'make clean' and thus break a distcheck. Derek -- Derek Price CVS Solutions Architect ( http://CVSHome.org ) mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com ) -- "I tried to think but nothing happened!" - Curly
Re: Default postscript cleans miss *.cps *.fns.
hi Derek, Could you `grep indexcode' your texi sources? Thanks!
Re: Default postscript cleans miss *.cps *.fns.
Akim Demaille wrote: hi Derek, Hi. :) Could you `grep indexcode' your texi sources? Thanks! [dprice@empress doc]$ fgrep indexcode cvs.texinfo [dprice@empress doc]$ Derek -- Derek Price CVS Solutions Architect ( http://CVSHome.org ) mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com ) -- If thou dost marry, I'll give thee this plague for thy dowry: be thou as chaste as ice, as pure as snow, thou shalt not escape calumny. Get thee to a nunnery. Go, farewell. Or if thou wilt needs marry, marry a fool. For wise men know well enough what monsters you make of them. To a nunnery, go, and quickly, too. Fare- well. - Hamlet, Act III, Scene 1, Lines 135-141
