0135-0136.html
来自「linux-unix130.linux.and.unix.ebooks130 l」· HTML 代码 · 共 293 行
HTML
293 行
<HTML>
<HEAD>
<TITLE>Linux Complete Command Reference:User Commands:EarthWeb Inc.-</TITLE>
</HEAD>
<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
<SCRIPT>
<!--
function displayWindow(url, width, height) {
var Win = window.open(url,"displayWindow",'width=' + width +
',height=' + height + ',resizable=1,scrollbars=yes');
}
//-->
</SCRIPT>
</HEAD>
-->
<!-- ISBN=0672311046 //-->
<!-- TITLE=Linux Complete Command Reference//-->
<!-- AUTHOR=Red Hat//-->
<!-- PUBLISHER=Macmillan Computer Publishing//-->
<!-- IMPRINT=Sams//-->
<!-- CHAPTER=01 //-->
<!-- PAGES=0001-0736 //-->
<!-- UNASSIGNED1 //-->
<!-- UNASSIGNED2 //-->
<P><CENTER>
<a href="0132-0134.html">Previous</A> | <a href="../ewtoc.html">Table of Contents</A> | <a href="0137-0138.html">Next</A></CENTER></P>
<A NAME="PAGENUM-135"><P>Page 135</P></A>
<P><B>
USING WITH GNU EMACS
</B></P>
<P>The GNU emacs files lisp/term/sun.el,
lisp/sun-mouse.el, lisp/sun-fns.el, and
src/sunfns.c provide emacs support
for the emacstool and function keys. emacstool will automatically set the
TERM environment variable to be sun and unset
the environment variable TERMCAP. That is, these variables will not be inherited from the shell that starts
emacstool. Since the terminal type is SUN (that is, the environment variable
TERM is set to SUN), emacs will automatically load the file
lisp/term/sun. This, in turn, will ensure that
sun-mouse.el is autoloaded when any mouse events are detected. It is suggested that
sun-mouse and sun-fns be loaded in your
site-init.el file, so that they will always be loaded when running on a Sun workstation.
</P>
<P>In addition, emacstool sets the environment variable
IN_EMACSTOOL = "t". Lisp code in your
~/.emacs can use (getenv "IN_EMACSTOOL") to determine whether to do
emacstool-specific initialization. Sun.el uses this to automatically call
emacstool-init if (getenv
"IN_EMACSTOOL") is defined.
</P>
<P>The file src/sunfns.c defines several useful functions for
emacs on the Sun. Among these are procedures to pop up
SunView menus, put and get from the SunView STUFF buffer, and a procedure for changing the cursor icon. If you want to define
or edit cursor icons, there is a rudimentary mouse-driven icon editor in the file
lisp/sun-cursors.el. Try invoking (sc:edit-cursor).
</P>
<P><B>
BUGS
</P></B>
<P>It takes a few milliseconds to create a menu before it pops up.
</P>
<P><B>
ENVIRONMENT VARIABLES
</B></P>
<!-- CODE SNIP //-->
<PRE>
EMACSTOOL, IN_EMACSTOOL, TERM, TERMCAP
</PRE>
<!-- END CODE SNIP //-->
<P><B>
FILES
</B></P>
<!-- CODE SNIP //-->
<PRE>
emacs
</PRE>
<!-- END CODE SNIP //-->
<P><B>
SEE ALSO
</B></P>
<P>emacs(1), .../etc/SUN-SUPPORT, .../lisp/term/sun.el
</P>
<H3><A NAME="ch01_ 65">
etags
</A></H3>
<P>etags—Generate tag file for emacs
</P>
<P>ctags—Generate tag file for vi
</P>
<P><B>
SYNOPSIS
</B></P>
<!-- CODE //-->
<PRE>
etags [ _aCDSVH] [ _i file ][_o tagfile ]
[ --c++ ] [ --no_defines] [ --ignore_indentation ] [ --help ] [ --version ]
[ --include=file ] [ --output=tagfile ] [ --append ] file ...
ctags [ _aCdSVH] [ _BtTuvwx ] [ _o tagfile ]
[ --c++ ] [ --defines ] [ --ignore_indentation ]
[ --backward_search] [ --forward_search ] [ --typedefs ] [ --typedefs_and_c++]
[ --no_warn ] [ --cxref ] [ --help ] [ --version ]
[ --output=tagfile ] [ --append ] [ --update ] file ...
</PRE>
<!-- END CODE //-->
<P><B>
DESCRIPTION
</B></P>
<P>The etags program is used to create a tag table file, in a format understood by
emacs(1); the ctags program is used to create a similar table in a format understood by
vi(1) . Both forms of the program understand the syntax of C, FORTRAN,
Pascal, LaTeX, Scheme, emacs Lisp/Common Lisp, and most assembler_like syntaxes. Both forms read the files specified on
the command line, and write a tag table (defaults:
TAGS for etags, tags for ctags) in the current working directory. The
programs recognize the language used in an input file based on its filename and contents; there are no switches for specifying
the language.
</P>
<A NAME="PAGENUM-136"><P>Page 136</P></A>
<P><B>
OPTIONS
</B></P>
<P>Some options make sense only for the vi-style tag files produced by
ctags; etags does not recognize them. The programs accept unambiguous abbreviations for long option names.
</P>
<TABLE>
<TR><TD>
_a, --append
</TD><TD>
Append to existing tag file. (For
vi-format tag files, see also --update.)
</TD></TR><TR><TD>
_B, --backward_search
</TD><TD>
Tag files written in the format expected by
vi contain regular expression search instructions; the
_B option writes them using the delimiter ?, to search backwards through files.
The default is to use the delimiter / to search forwards through files. Only
ctags accepts this option.
</TD></TR><TR><TD>
_C, --c++
</TD><TD>
Treat files with .c and .h extensions as C++ code, not C code. Files with
.C, .H, .cxx, .hxx, or .cc extensions are always assumed to be C++ code.
</TD></TR><TR><TD>
_d, --defines
</TD><TD>
Create tag entries for C preprocessor definitions, too. This is the default behavior for
etags, so this option is only accepted by ctags.
</TD></TR><TR><TD>
_D, --no_defines
</TD><TD>
Do not create tag entries for C preprocessor definitions. This may make the tags file
much smaller if many header files are tagged. This is the default behavior for
ctags, so this option is only accepted by etags.
</TD></TR><TR><TD>
-i file, --include=file
</TD><TD>
Include a note in
tag file indicating that, when searching for a tag, one should also
consult the tags file file after checking the current file. Only
etags accepts this option.
</TD></TR><TR><TD>
_o tagfile, --output=tagfile
</TD><TD>
Explicit name of file for tag table; overrides default
TAGS or tags. (But ignored with _v or
_x.)
</TD></TR><TR><TD>
_S, --ignore_indentation
</TD><TD>
Don't rely on indentation as much as we normally do. Currently, this means not to
assume that a closing brace in the first column is the final brace of a function or structure
definition in C and C++.
</TD></TR><TR><TD>
_t, --typedefs
</TD><TD>
Record typedefs in C code as tags. Since this is the default behavior of
etags, only ctags accepts this option.
</TD></TR><TR><TD>
_T, --typedefs_and_c++
</TD><TD>
Generate tag entries for
typedefs, struct, enum, and union tags, and C++ member
functions. Since this is the default behavior of
etags, only ctags accepts this option.
</TD></TR><TR><TD>
_u, --update
</TD><TD>
Update tag entries for files specified on command line, leaving tag entries for other files
in place. Currently, this is implemented by deleting the existing entries for the given files
and then rewriting the new entries at the end of the tags file. It is often faster to simply
rebuild the entire tag file than to use this. Only
ctags accepts this option.
</TD></TR><TR><TD>
_v, --vgrind
</TD><TD>
Instead of generating a tag file, write index (in
vgrind format) to standard output. Only ctags accepts this option.
</TD></TR><TR><TD>
_w, --no_warn
</TD><TD>
Suppress warning messages about duplicate entries. The
etags program does not check for duplicate entries, so this option is not allowed with it.
</TD></TR><TR><TD>
_x, --cxref
</TD><TD>
Instead of generating a tag file, write a cross-reference (in
cxref format) to standard output. Only ctags accepts this option.
</TD></TR><TR><TD>
_H, --help
</TD><TD>
Print usage information.
</TD></TR><TR><TD>
_V, --version
</TD><TD>
Print the current version of the program (same as the version of the
emacs etags is shipped with).
</TD></TR></TABLE>
<P><B>
SEE ALSO
</B></P>
<P>emacs entry in info; GNU Emacs Manual, Richard Stallman.
</P>
<P>cxref(1), emacs(1), vgrind(1), vi(1).
</P>
<P><B>
COPYING
</B></P>
<P>Copyright " 1992 Free Software Foundation, Inc. Permission is granted to make and distribute verbatim copies of
this manual provided the copyright notice and this permission notice are preserved on all copies.
</P>
<P>Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim
copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one.
</P>
<P><CENTER>
<a href="0132-0134.html">Previous</A> | <a href="../ewtoc.html">Table of Contents</A> | <a href="0137-0138.html">Next</A></CENTER></P>
</td>
</tr>
</table>
<!-- begin footer information -->
</body></html>⌨️ 快捷键说明
复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?