cscope.1

tvapp用于播放tv程序

``file''.)
.TP
.B ^r
Rebuild the cross-reference.
.TP
.B !
Start an interactive shell (type ^d to return to cscope).
.TP
.B ^l
Redraw the screen.
.TP
.B ?
Give help information about cscope commands.
.TP
.B ^d
Exit cscope.
.PP
.PP   
.B NOTE: If the first character of the text to be searched for matches
.B one of the above commands, escape it by typing a  (backslash) first.
.PP
.B Substituting new text for old text
.PP
After the text to be changed has been typed, cscope will prompt for
the new text, and then it will display the lines containing the old
text. Select the lines to be changed with these single-character
commands:
.PP
.TP
.B 0-9a-zA-Z
Mark or unmark the line to be changed.
.TP
.B * 
Mark or unmark all displayed lines to be changed.
.TP
.B <Space>
Display next set of lines.
.TP
.B +
Display next set of lines.
.TP
.B - 
Display previous set of lines.
.TP
.B a
Mark or unmark all lines to be changed.
.TP
.B ^d
Change the marked lines and exit.
.TP
.B <Esc>
Exit without changing the marked lines.
.TP
.B !
Start an interactive shell (type ^d to return to cscope).
.TP
.B ^l
Redraw the screen.
.TP
.B ?
Give help information about cscope commands.
.TP
.B  Special keys
.PP
If your terminal has arrow keys that work in vi, you can use them
to move around the input fields. The up-arrow key is useful to move to
the previous
input field instead of using the <Tab> key repeatedly. If you have
<CLEAR>, <NEXT>, or <PREV> keys they will act as the ^l, +, and -
commands, respectively.
.PP   
.B Line-Oriented interface
.PP  
The -l option lets you use cscope where a screen-oriented interface
would not be useful, for example, from another screen-oriented
program.
.PP  
cscope will prompt with >> when it is ready for an input line starting
with the field number (counting from 0) immediately followed by the
search pattern, for example, ``lmain'' finds the definition of the
main function.
.PP   
If you just want a single search, instead of the -l option use the -L
and -num pattern options, and you won't get the >> prompt.
.PP 
For -l, cscope outputs the number of reference lines
cscope: 2 lines
.PP  
For each reference found, cscope outputs a line consisting of the file
name, function name, line number, and line text, separated by spaces,
for example,
main.c main 161 main(argc, argv)
.PP
Note that the editor is not called to display a single reference,
unlike the screen-oriented interface.
.PP
You can use the c command to toggle ignore/use letter case when
searching. (When ignoring letter case, search for ``FILE'' will match
``File'' and ``file''.)
.PP
You can use the r command to rebuild the database.
.PP
cscope will quit when it detects end-of-file, or when the first
character of an input line is ``^d'' or ``q''.
.PP   
.SH "ENVIRONMENT VARIABLES"
.TP
.B CSCOPE_EDITOR
Overrides the EDITOR and VIEWER variables. Use this if you wish to use
a different editor with cscope than that specified by your
EDITOR/VIEWER variables.
.TP
.B CSCOPE_LINEFLAG
Format of the line number flag for your editor. By default, cscope
invokes your editor via the equivalent of ``editor +N file'', where
``N'' is the line number that the editor should jump to. This format
is used by both emacs and vi. If your editor needs something
different, specify it in this variable, with ``%s'' as a placeholder
for the line number.  Ex: if your editor needs to be invoked as
``editor -#103 file'' to go to line 103, set this variable to
``-#%s''.
.TP
.B CSCOPE_LINEFLAG_AFTER_FILE
Set this variable to ``yes'' if your editor needs to be invoked with
the line number option after the filename to be edited. To continue
the example from CSCOPE_LINEFLAG, above: if your editor needs to see
``editor file -#number'', set this environment variable. Users of most
standard editors (vi, emacs) do not need to set this variable.
.TP
.B EDITOR
Preferred editor, which defaults to vi.
.TP
.B HOME
Home directory, which is automatically set at login.
.TP
.B INCLUDEDIRS
Colon-separated list of directories to search for #include
files.
.TP
.B SHELL
Preferred shell, which defaults to sh.
.TP
.B SOURCEDIRS
Colon-separated list of directories to search for additional
source files.
.TP
.B TERM
Terminal type, which must be a screen terminal.
.TP
.B TERMINFO
Terminal information directory full path name. If your terminal
is not in the standard terminfo directory, see curses
and terminfo for how to make your own terminal description.
.TP
.B TMPDIR
Temporary file directory, which defaults to /var/tmp.
.TP
.B VIEWER
Preferred file display program (such as less), which overrides
EDITOR (see above).
.TP
.B VPATH
A colon-separated list of directories, each of which has the
same directory structure below it. If VPATH is set, cscope
searches for source files in the directories specified; if it
is not set, cscope searches only in the current directory.
.PP
.SH FILES
.TP
.B cscope.files
Default files containing -I, -p, -q, and -T options and the
list of source files (overridden by the -i option).
.TP
.B cscope.out
Symbol cross-reference file (overridden by the -f option),
which is put in the home directory if it cannot be created in
the current directory.
.TP
.PD 0
.B cscope.in.out
.TP
.B cscope.po.out
.PD 1
Default files containing the inverted index used for quick
symbol searching (-q option). If you use the -f option to
rename the cross-reference file (so it's not cscope.out), the
names for these inverted index files will be created by adding
 .in and .po to the name you supply with -f. For example, if you
indicated -f xyz, then these files would be named xyz.in and
xyz.po.
.TP
.B INCDIR
Standard directory for #include files (usually /usr/include).
.SH Notices
.I cscope
recognizes function definitions of the form:
.PD 0
.TP
fname blank ( args ) white arg_decs white {
.PD 1 
.TP
where:
.I fname
is the function name
.TP
.I blank
is zero or more spaces or tabs, not including newlines
.TP
.I args
is any string that does not contain a ``"'' or a newline
.TP
.I white
is zero or more spaces, tabs, or newlines
.TP
.I arg_decs
are zero or more argument declarations (arg_decs may include
comments and white space)
.PP
It is not necessary for a function declaration to start at the
beginning of a line. The return type may precede the function name;
cscope will still recognize the declaration. Function definitions that
deviate from this form will not be recognized by cscope.
.PP
The ``Function'' column of the search output for the menu option Find
functions called by this function: input field will only display the
first function called in the line, that is, for this function
.PP
 e()
 {
         return (f() + g());
 }
.PP
the display would be
.PP
   Functions called by this function: e
   File Function Line
   a.c f 3 return(f() + g());
.PP   
Occasionally, a function definition or call may not be recognized
because of braces inside #if statements. Similarly, the use of a
variable may be incorrectly recognized as a definition.
.PP
A 
.B typedef
name preceding a preprocessor statement will be incorrectly
recognized as a global definition, for example,
.PP
 LDFILE  *
 #if AR16WR
.PP
Preprocessor statements can also prevent the recognition of a global
definition, for example,
.PP
 char flag
 #ifdef ALLOCATE_STORAGE
      = -1
 #endif
 ;
.PP
A function declaration inside a function is incorrectly recognized as
a function call, for example,
.PP
 f()
 {
         void g();
 }
.PP
is incorrectly recognized as a call to g.
.PP   
.I cscope
recognizes C++ classes by looking for the class keyword, but
doesn't recognize that a struct is also a class, so it doesn't
recognize inline member function definitions in a structure. It also
doesn't expect the class keyword in a
.I typedef
, so it incorrectly
recognizes X as a definition in
.PP
 typedef class X  *  Y;
.PP
It also doesn't recognize operator function definitions
.PP
 Bool Feature::operator==(const Feature & other)
 {
   ...
 }
.PP
Nor does it recognize function definitions with a function pointer
argument
.PP
 ParseTable::Recognize(int startState, char *pattern,
   int finishState, void (*FinalAction)(char *))
 {
   ...
 }