|
|
1.1 root 1: .TH PFIND 1P "22 June 1983"
2: .UC 4
3: .SH NAME
4: pfind \- find files in projects
5: .SH SYNOPSIS
6: .B pfind
7: [\fB\-l\fR] [\fB\-P \fRpdirname] [\fB\-T \fRtypexpr] file ...
8: .SH DESCRIPTION
9: .I Pfind
10: descends recursively through a project hierarchy seeking
11: .I files.
12: .SH OPTIONS
13: .IP \fB\-l\fR
14: List in long format, giving the full pathname of
15: .I file.
16: .IP "\fB\-P \fIpdirname\fR"
17: Specify a project other than the current working project. If
18: .I pdirname
19: is a project directory,
20: .I pfind
21: will search only that directory.
22: .IP "\fB\-T \fItypexpr\fR"
23: Only search project directories corresponding to boolean type label expression,
24: .I typexpr.
25: .SH EXAMPLES
26: If the file `core' exists in the project directory `work' of the current
27: working project `spms', the command `pfind core' will print:
28: .PP
29: ...^work/core
30: .PP
31: and the command `pfind -l core' might print something like:
32: .PP
33: /usr/pjn/spms/work/core
34: .SH "SEE ALSO"
35: find(1)
36: .SH DIAGNOSTICS
37: Exit status 0 is normal. Exit status 1 indicates an error.
38: .SH AUTHOR
39: Peter J. Nicklin
40: .SH BUGS
41: Should be able to do pattern matching on file names.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.