xemacs-beta: man/cc-mode.texi comparison

comparison man/cc-mode.texi @ 165:5a88923fcbfe r20-3b9

Import from CVS: tag r20-3b9

author	cvs
date	Mon, 13 Aug 2007 09:44:42 +0200
parents	fe104dbd9147
children	929b76928fce

comparison

equal deleted inserted replaced

-:4e0740e5aab2
+:5a88923fcbfe
 @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 @comment %**start of header (This is for running Texinfo on a region)
 @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 @setfilename  cc-mode.info
-@settitle     CC MODE Version 4 Documentation
+@settitle     CC MODE Version 5 Documentation
 @footnotestyle end
 @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 @comment @setchapternewpage odd !! we don't want blank pages !!
 @comment %**end of header (This is for running Texinfo on a region)
 @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 @comment
-@comment texinfo manual for @file{cc-mode.el} version 4
+@comment TeXinfo manual for CC Mode
-@comment manual version: 2.66
+@comment Generated from the original README file by Krishna Padmasola
-@comment generated from the original README file by Krishna Padmasola
 @comment <krishna@earth-gw.njit.edu>
 @comment
-@comment Barry A. Warsaw <bwarsaw@cnri.reston.va.us>
+@comment Maintained by Barry A. Warsaw <cc-mode-help@python.org>
-@comment Last modification: 1997/03/07 23:36:14
 @comment
 @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 @comment The title is printed in a large font.
 @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-@center @titlefont{CC Mode Version 4}
+@center @titlefont{CC Mode 5.11}
 @sp 2
-@center A GNU Emacs mode for editing C, C++, Objective-C, and Java code.
+@center @subtitlefont{A GNU Emacs mode for editing C, C++, Objective-C, and Java code}
-@center (manual revision: 2.66)
 @sp 2
 @center Barry A. Warsaw
 @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 @macro ccmode
 CC Mode
 @end macro
 @cindex BOCM
-Welcome to @ccmode{}, version 4.  This is a GNU Emacs mode for
-editing files containing C, C++, Objective-C, and Java code.
+Welcome to @ccmode{}.  This is a GNU Emacs mode for editing files
-This incarnation of the mode is descendant from @file{c-mode.el} (also
+containing C, C++, Objective-C, and Java code.  This incarnation of the
-called "Boring Old C Mode" or BOCM @code{:-)}, and @file{c++-mode.el}
+mode is descendant from @file{c-mode.el} (also called "Boring Old C
-version 2, which I have been maintaining since 1992.  @ccmode{}
+Mode" or BOCM @code{:-)}, and @file{c++-mode.el} version 2, which I have
-represents a significant milestone in the mode's life.  It has been
+been maintaining since 1992.  @ccmode{} represents a significant
-fully merged back with Emacs 19's @file{c-mode.el}. Also a new, more
+milestone in the mode's life.  It has been fully merged back with Emacs
-intuitive and flexible mechanism for controlling indentation has been
+19's @file{c-mode.el}. Also a new, more intuitive and flexible mechanism
-developed.
+for controlling indentation has been developed.
-@ccmode{} version 4 supports the editing of K&R and ANSI C, @dfn{ARM}
+@ccmode{} supports the editing of K&R and ANSI C, @dfn{ARM}
 @footnote{``The Annotated C++ Reference Manual'', by Ellis and
 Stroustrup.} C++, Objective-C, and Java files.  In this way, you can
 easily set up consistent coding styles for use in editing all C, C++,
 Objective-C, and Java programs. @ccmode{} does @emph{not} handle
 font-locking (a.k.a. syntax coloring, keyword highlighting) or anything
 prefixed with @code{c-@var{<thing>}}, and @code{c-mode},
 @code{c++-mode}, @code{objc-mode}, and @code{java-mode} entry points are
 provided.  This file is intended to be a replacement for
 @file{c-mode.el} and @file{c++-mode.el}.
-@findex c-version
-The major version number was incremented to 4 with the addition of
-@code{objc-mode}. To find the minor revision number of this release, use
-@kbd{M-x c-version RET}.
-As of this writing (27-Feb-1997), Emacs 19.34, XEmacs 19.14, and XEmacs
-20.0 are all distributed with @ccmode{}, but they may not have the
-latest releases.  You may therefore, want to upgrade your copy of
-@ccmode{}.  See @ref{Getting the latest CC Mode release}.
 @cindex @file{cc-compat.el} file
 This distribution also contains a file called @file{cc-compat.el} which
 should ease your transition from BOCM to @ccmode{}.  It currently
 comes unguaranteed and unsupported, but this may change for future
 versions.  If you have a BOCM configuration you are really happy with,
 @chapter  Getting Connected
 @cindex   Getting Connected
 @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-@file{cc-mode.el} works well with the three main branches of Emacs:
+If you got this version of @ccmode{} with Emacs, it should work just
-XEmacs 19 and XEmacs 20, both maintained by @code{xemacs.org}, and Emacs
+fine right out of the box, and you can safely skip to the next chapter.
-19 maintained by the Free Software Foundation.  Emacs users will want to
+Note however that you may not have the latest @ccmode{} release and may
-use version 19.21 or better, XEmacs users will want 19.6 or better.
+want to upgrade your copy.  See the @file{README} file, or the @ccmode{}
-Earlier versions of these Emacsen have deficiencies and/or bugs which
+Web pages latest information on Emacs version compatibility,
-will adversely affect the performance and usability of @ccmode{}.  You
+@ref{Getting the latest CC Mode release}.
-are better off just getting the latest version of Emacs or XEmacs.
 @cindex @file{cc-mode-18.el} file
-@file{cc-mode.el} will work with Emacs 18 if you use the
+@emph{@ccmode{} no longer works with Emacs 18!}  The
-@file{cc-mode-18.el} compatibility file, but only moderately well.  A
+@file{cc-mode-18.el} file is no longer distributed with @ccmode{}.  If
-word of warning though, @emph{Emacs 18 lacks some fundamental
+you haven't upgraded from Emacs 18 by now, you are out of luck.  The
-functionality and ultimately, using Emacs 18 is a losing
+rest of these installation instructions assume you are using one of the
-battle}.  Hence @ccmode{} under Emacs 18 is no longer supported and
+new Emacs or XEmacs releases, that already come with @ccmode{}.  These
-it is highly recommended that you upgrade to Emacs 19.  If you use
+instructions explain how to upgrade to use the latest @ccmode{}
-@ccmode{} under Emacs 18, you're on your own.  With @ccmode{}
+release.
-version 5, Emacs 18 support will be dropped altogether.
-Note that as of XEmacs 19.13 and Emacs 19.30, your Emacs already comes
-with @ccmode{} version 4 preconfigured for your use.  You should be
-able to safely skip the rest of the setup information in this chapter,
-unless you want to install the latest version of @ccmode{} into one
-of these Emacsen.
 @cindex .emacs file
-The first thing you will want to do is put @file{cc-mode.el} somewhere
-on your @code{load-path} so Emacs can find it.  Do a @kbd{C-h v
+The first thing you will want to do is put the @ccmode{} source files in
-load-path RET} to see all the directories Emacs looks at when loading a
+a subdirectory somewhere on your @code{load-path} so Emacs can find it.
-file.  If none of these directories are appropriate, create a new
+The distribution tarball unpacks into its own subdirectory tagged with
-directory and add it to your @code{load-path}:
+the version number of the release.  E.g. @ccmode{} release 5.00 will
+unpack into the @file{cc-mode-5.00} directory.  Assuming you unpacked
-@noindent
+the distribution in your home directory, you should add the following to
-@emph{[in the shell]}
+your @file{.emacs} file in order to pick up the latest version of
-@example
+@ccmode{} over the one distributed with your Emacs:
-@group
+@example
-% cd
-% mkdir mylisp
+(setq load-path (cons "~/cc-mode-5.00" load-path))
-% mv cc-mode.el mylisp
-% cd mylisp
-@end group
-@end example
-@noindent
-@emph{[in your .emacs file add]}
-@example
-(setq load-path (cons "~/mylisp" load-path))
 @end example
 @cindex byte compile
-Next you want to @dfn{byte compile} @file{cc-mode.el}.  The mode uses a
-lot of macros so if you don't byte compile it, things will be unbearably
+Next you want to @dfn{byte compile} all the @ccmode{} source files.
-slow.  @emph{You can ignore all byte-compiler warnings!}  They are the
+@ccmode{} uses a lot of macros so if you don't byte compile it,
-result of the supporting different versions of Emacs, and none of the
+things will be unbearably slow.  @emph{You can ignore all byte-compiler
-warnings have any effect on operation. Let me say this again:
+warnings!}  They are the result of the supporting different versions of
-@strong{You really can ignore all byte-compiler warnings!}
+Emacs, and none of the warnings have any effect on operation. Let me say
+this again: @strong{You really can ignore all byte-compiler warnings!}
-Here's what to do to byte-compile the file [in emacs]:
-@example
+To byte-compile the source files, be sure you have access to the
+@code{make(1)} program.  In a shell, execute the following commands
-M-x byte-compile-file RET ~/mylisp/cc-mode.el RET
+(again, assuming you unpacked @ccmode{} version 5.00 in your home
+directory@footnote{Of course, the version numbers will probably be
-@end example
+different.}):
-If you are running a version of Emacs or XEmacs that comes with
+@example
-@ccmode{} by default, you can simply add the following to your
-@file{.emacs} file in order to upgrade to the latest version of
+% cd ~/cc-mode-5.00
-@ccmode{}:
+% make
-@example
+@end example
-(load "cc-mode")
+By default, the @file{Makefile} assumes you are using XEmacs.  If you
-@end example
+are using Emacs, execute this instead:
-Users of even older versions of Emacs 19, Emacs 18, or of the older
+@example
-Lucid Emacs will probably be running an Emacs that has BOCM
-@file{c-mode.el} and possible @file{c++-mode.el} pre-dumped.  If your
+% make EMACS=emacs
-Emacs is dumped with either of these files you first need to make Emacs
-``forget'' about those older modes.
+@end example
-If you can do a @kbd{C-h v c-mode-map RET} without getting an error, you
+Next time you start up Emacs you should be using the latest @ccmode{}.
-need to add these lines at the top of your @file{.emacs} file:
+You can test this by visiting a C file and hitting @kbd{M-x c-version
-@example
+RET}; you should see this message in the echo area:
-@group
+@example
-(fmakunbound 'c-mode)
+Using CC Mode version 5.00
-(makunbound  'c-mode-map)
-(fmakunbound 'c++-mode)
+@end example
-(makunbound  'c++-mode-map)
-(makunbound  'c-style-alist)
-@end group
-@end example
-After those lines you will want to add the following autoloads to your
-@file{.emacs} file so that @ccmode{} gets loaded at the right time:
-@example
-@group
-(autoload 'c++-mode  "cc-mode" "C++ Editing Mode" t)
-(autoload 'c-mode    "cc-mode" "C Editing Mode" t)
-(autoload 'objc-mode "cc-mode" "Objective-C Editing Mode" t)
-(autoload 'java-mode "cc-mode" "Java Editing Mode" t)
-@end group
-@end example
-Alternatively, if you want to make sure @ccmode{} is loaded when
-Emacs starts up, you could use this line instead of the autoloads
-above:
-@example
-(require 'cc-mode)
-@end example
-Next, you will want to set up Emacs so that it edits C files in
-@code{c-mode}, C++ files in @code{c++-mode}, Objective-C files in
-@code{objc-mode}, and Java files in @code{java-mode}. You should
-add the following to your @file{.emacs} file, which assumes
-you'll be editing @code{.h} and @code{.c} files as C, @code{.hh},
-@code{.cc}, @code{.H}, and @code{.C} files as C++, @code{.m} files as
-Objective-C, and @code{.java} files as Java code. YMMV:
-@example
-@group
-(setq auto-mode-alist
-(append
-'(("\\.C$"    . c++-mode)
-("\\.H$"    . c++-mode)
-("\\.cc$"   . c++-mode)
-("\\.hh$"   . c++-mode)
-("\\.c$"    . c-mode)
-("\\.h$"    . c-mode)
-("\\.m$"    . objc-mode)
-("\\.java$" . java-mode)
-) auto-mode-alist))
-@end group
-@end example
-You may already have some or all of these settings on your
-@code{auto-mode-alist}, but it won't hurt to put them on there again.
-That's all you need --- I know, I know, it sounds like a lot @code{:-)},
-but after you've done all this, you should only need to quit and restart
-Emacs.  The next time you visit a C, C++, Objective-C, or Java file you
-should be using @ccmode{}.  You can check this easily by hitting
-@kbd{M-x c-version RET}; you should see this message in the echo area:
-@example
-Using CC Mode version 4.@var{xxx}
-@end example
-@noindent
-where @var{xxx} is the latest minor release number.
 @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 @node     New Indentation Engine, Minor Modes, Getting Connected, Top
 @comment  node-name,              next,        previous,          up
 @dfn{hungry-delete mode}, is a simple feature that some people find
 extremely useful.  In fact, you might find yourself wanting
 hungry-delete in @strong{all} your editing modes!
 @kindex DEL
-In a nutshell, when hungry-delete mode is enabled, hitting the @kbd{DEL}
+@kindex Backspace
-character will consume all preceding whitespace, including newlines and
+In a nutshell, when hungry-delete mode is enabled, hitting the
-tabs.  This can really cut down on the number of @kbd{DEL}'s you have to
+@kbd{Backspace} key@footnote{I say ``hit the @kbd{Backspace} key'' but
-type if, for example you made a mistake on the preceding line.
+what I really mean is ``when Emacs receives the @code{BackSpace} keysym
+event''.  The difference usually isn't significant to most users, but
+advanced users will realize that under window systems such as X, any
+physical key (keycap) on the keyboard can be configured to generate any
+keysym.  Also, the use of Emacs on TTYs will affect which keycap
+generates which keysym.  From a pedantic point of view, here we are only
+concerned with the keysym event that Emacs receives.} will consume all
+preceding whitespace, including newlines and tabs.  This can really cut
+down on the number of @kbd{Backspace}'s you have to type if, for example
+you made a mistake on the preceding line.
+@findex c-electric-backspace
+@findex electric-backspace (c-)
+@vindex c-backspace-function
+@vindex backspace-function (c-)
 @findex c-electric-delete
 @findex electric-delete (c-)
 @vindex c-delete-function
 @vindex delete-function (c-)
 @cindex literal
-By default, @ccmode{} actually runs the command
-@code{c-electric-delete} when you hit @kbd{DEL}.  When this command is
+@findex backward-delete-char-untabify
-used to delete a single character (i.e. when it is called interactively
-with no numeric argument), it really runs the function contained in the
+By default, when you hit the @kbd{Backspace} key
-variable @code{c-delete-function}.  This function is called with a
+@ccmode{} runs the command @code{c-electric-backspace}, which deletes
-single argument, which is the number of characters to delete.
+text in the backwards direction.  When deleting a single character, or
-@code{c-delete-function} is also called when the @kbd{DEL} key is typed
+when @kbd{Backspace} is hit in a literal
-inside a literal (see @ref{Auto-newline insertion}.  Inside a literal,
+(see @ref{Auto-newline insertion}),
-@code{c-electric-delete} is not electric, which is typical of all the
+or when hungry-delete mode is disabled, the function
-so-called electric commands.
+contained in the @code{c-backspace-function} variable is called with one
+argument (the number of characters to delete).  This variable is set to
+@code{backward-delete-char-untabify} by default.
+@vindex delete-key-deletes-forward
+@findex delete-char
+Similarly, hitting the @kbd{DEL} key runs the command
+@code{c-electric-delete}.  Some versions of Emacs@footnote{As of this
+writing, 20-Jun-1997, only XEmacs 20 supports this.} support separation
+of the @kbd{Backspace} and @kbd{DEL} keys, so that @kbd{DEL} will delete
+in the forward direction when @code{delete-key-deletes-forward} is
+non-@code{nil}.  If your Emacs supports this, and
+@code{delete-key-deletes-forward} is non-@code{nil}, and hungry-delete
+mode is enabled, then @kbd{DEL} will consume all whitespace following
+point.  When deleting a single character, or when @kbd{DEL} is hit in a
+literal, or when hungry-delete mode is disabled, the function contained
+in the @code{c-delete-function} variable is called with one argument
+(the number of characters to delete).  This variable is set to
+@code{delete-char} by default.
+However, if @code{delete-key-deletes-forward} is @code{nil}, or your
+Emacs does not support separation of @kbd{Backspace} and @kbd{DEL}, then
+@code{c-electric-delete} simply calls @code{c-electric-backspace}.
 @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 @node  Commands, Customizing Indentation, Minor Modes, Top
 @comment  node-name,              next,                    previous,up
 @noindent
 So, for example, because most of the default offsets are defined in
 terms of @code{+}, @code{-}, and @code{0}, if you like the general
 indentation style, but you use 4 spaces instead of 2 spaces per level,
 you can probably achieve your style just by changing
-@code{c-basic-offset} like so (in your @file{.emacs} file)@footnote{The
+@code{c-basic-offset} like so (in your @file{.emacs} file):
-reason you need to use @code{setq-default} instead of @code{setq} is
+@example
-that @code{c-basic-offset} is a buffer local variable, as are most
-configuration variables.  If you were to put this code in, e.g. your
+(setq c-basic-offset 4)
-@code{c-mode-common-hook} function, you could use @code{setq}.
-Alternatively, you can keep these variables global by setting
-@code{c-style-variables-are-local-p} to @code{nil}, but you must do this
-before @code{cc-mode.el} is loaded into your Emacs session.}:
-@example
-(setq-default c-basic-offset 4)
 @end example
 @noindent
 This would change
 @vindex c-mode-hook
 @vindex c++-mode-hook
 @vindex objc-mode-hook
 @vindex java-mode-hook
 @cindex hooks
-To make this change permanent, you need to add some lisp code to your
+To make your changes permanent, you need to add some lisp code to your
-@file{.emacs} file.  @ccmode{} provides several hooks that you can
+@file{.emacs} file, but first you need to decide whether your styles
+should be global in every buffer, or local to each specific buffer.
+If you edit primarily one style of C (or C++, Objective-C, Java) code,
+you may want to make the @ccmode{} style variables have global values so
+that every buffer will share the style settings.  This will allow you to
+set the @ccmode{} variables at the top level of your @file{.emacs}
+file.  This is the default way @ccmode{} works.
+@vindex c-mode-common-hook
+@vindex mode-common-hook (c-)
+@vindex c-style-variables-are-local-p
+@vindex style-variables-are-local-p (c-)
+If you edit many different styles of C (or C++, Objective-C, Java) at
+the same time, you probably want to make the @ccmode{} style variables
+have buffer local values.  If you do this, then you will need to set any
+@ccmode{} style variables in a hook function (e.g. off of
+@code{c-mode-common-hook} instead of at the top level of your
+@file{.emacs} file.  The recommended way to do this is to set the
+variable @code{c-style-variables-are-local-p} to @code{t}
+@strong{before} @ccmode{} is loaded into your Emacs session.
+@ccmode{} provides several hooks that you can
 use to customize the mode according to your coding style.  Each language
 mode has its own hook, adhering to standard Emacs major mode
 conventions.  There is also one general hook:
 @itemize @bullet
 Here's a simplified example of what you can add to your @file{.emacs}
 file to make the changes described in the previous section
 (@ref{Interactive Customization}) more permanent.  See the Emacs manuals
 for more information on customizing Emacs via hooks.  @xref{Sample
 .emacs File} for a more complete sample @file{.emacs} file.
-@footnote{The use of @code{add-hook} in this example only works for
-Emacs 19 and beyond.  Workarounds are available if you are using Emacs
-18.}
 @example
 @group
 (defun my-c-mode-common-hook ()
 ;; my customizations for all of c-mode, c++-mode, objc-mode, java-mode
 you will have to make the variables buffer local.  The variable
 @code{c-style-variables-are-local-p} controls this.
 When @code{c-style-variables-are-local-p} is non-nil, then the style
 variables will have a different settable value for each buffer,
-otherwise all buffers will share the same values.  This variable only
+otherwise all buffers will share the same values.  By default, its value
-takes effect when @ccmode{} is loaded into your Emacs session.  By
+is @code{nil} (i.e. global values).  You @strong{must} set this variable
-default (for backwards compatibility reasons), its value is @code{t}.
+before @ccmode{} is loaded into your Emacs session, and once the
-Note that once the variables are made buffer local, they will retain
+variables are made buffer local, they cannot be made global again
-this property for the remainder of the current Emacs session.  To change
+(unless you restart Emacs of course!)
-this behavior, set @code{c-style-variables-are-local-p} to @code{nil}
-@emph{before} you load @file{cc-mode.el}.
 @menu
 * Custom Indentation Functions::
 * Custom Brace and Colon Hanging::
 * Customizing Semi-colons and Commas::
 @item
 @code{inline-open} --- brace that opens an in-class inline method
 @item
 @code{inline-close} --- brace that closes an in-class inline method
 @item
-@code{func-decl-cont} --- the nether region between a function
+@code{func-decl-cont} --- the region between a function definition's
-declaration's argument list and the defun opening brace.  In C++ and
+argument list and the function opening brace (excluding K&R argument
-Java, this can include the @code{throws} clauses of a method
+declarations).  In C, you cannot put anything but whitespace and comments
-declaration.
+between them; in C++ and Java, @code{throws} declarations and other
+things can appear in this context.
 @item
 @code{knr-argdecl-intro} --- first line of a K&R C argument declaration
 @item
 @code{knr-argdecl} --- subsequent lines in a K&R C argument declaration
 @item
 @cindex friend syntactic symbol
 Returning to the previous example, line 16 is given @code{inline-close}
 syntax, while line 12 is given @code{defun-block-open} syntax, and lines
 13 through 15 are all given @code{statement} syntax.  Line 17 is
-interesting in that it's syntactic analysis list contains three
+interesting in that its syntactic analysis list contains three
 elements:
 @example
 @code{((friend) (inclass . 58) (topmost-intro . 380))}
 @chapter  Performance Issues
 @cindex   Performance Issues
 @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-C and it's derivative languages are highly complex creatures.  Often,
+C and its derivative languages are highly complex creatures.  Often,
 ambiguous code situations arise that require @ccmode{} to scan
 large portions of the buffer to determine syntactic context.  Such
 pathological code@footnote{such as the output of @code{lex(1)}!}
 can cause @ccmode{} to perform fairly badly.
 This section identifies some of the coding styles to watch out for, and
 column zero!
 @cindex @file{cc-lobotomy.el} file
 @vindex cc-lobotomy-pith-list
 You might want to investigate the speed-ups contained in the
-file @file{cc-lobotomy.el}, which is part of the @ccmode{} distribution.
+file @file{cc-lobotomy.el}, which comes as part of the @ccmode{}
+distribution, but is completely unsupported.
 As mentioned previous, @ccmode{} always trades accuracy for speed,
 however it is recognized that sometimes you need speed and can sacrifice
 some accuracy in indentation.  The file @file{cc-lobotomy.el} contains
 hacks that will ``dumb down'' @ccmode{} in some specific ways, making
 that trade-off of speed for accuracy.  I won't go into details of its
 @kindex ESC C-x
 @kindex C-c C-q
 @kindex ESC C-q
 @kindex ESC C-u
 @kindex RET
-@kindex LFD
+@kindex C-j
 @findex newline-and-indent
 @quotation
 @strong{Q.} @emph{How do I re-indent the whole file?}
 @strong{Q.} @emph{Why doesn't the @key{RET} key indent the line to
 where the new text should go after inserting the newline?}
 @strong{A.} Emacs' convention is that @key{RET} just adds a newline,
-and that @key{LFD} adds a newline and indents it.  You can make
+and that @key{C-j} adds a newline and indents it.  You can make
 @key{RET} do this too by adding this to your
 @code{c-mode-common-hook} (see the sample @file{.emacs} file
 @ref{Sample .emacs File}):
 @example
 @strong{Q.} @emph{How do I make strings, comments, keywords, and other
 constructs appear in different colors, or in bold face, etc.?}
 @strong{A.} ``Syntax Colorization'' is an Emacs 19 feature, controlled
 by @code{font-lock-mode}.  It is not part of @ccmode{}.
-@sp 1
-@strong{Q.} @emph{I @code{setq} @code{c-basic-offset} to 4 in my
-@file{.emacs} file, but why does everything still get indented with only
-2 spaces?}
-@vindex c-style-variables-are-local-p
-@vindex style-variables-are-local-p
-@strong{A.} It's because @code{c-basic-offset} is, by default, a
-``buffer local variable'', meaning its value is unique to each buffer.
-The prefered way to customize this is to change its value in a ``mode
-hook'' (most likely @code{c-mode-common-hook}).  Alternatively you can
-use @code{setq-default} to change its value globally.  Better yet,
-before you load @file{cc-mode.el}, set the variable
-@code{c-style-variables-are-local-p} to @code{nil}.  @xref{Advanced
-Customizations}.
 @end quotation
 @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 ;; c-mode-map because c++-mode-map, objc-mode-map, and java-mode-map
 ;; inherit from it.
 (define-key c-mode-map "\C-m" 'newline-and-indent)
 )
-;; the following only works in Emacs 19
-;; Emacs 18ers can use (setq c-mode-common-hook 'my-c-mode-common-hook)
 (add-hook 'c-mode-common-hook 'my-c-mode-common-hook)
 @end example
 @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 @node  Limitations and Known Bugs, Mailing Lists and Submitting Bug Reports, Sample .emacs File, Top
 @item
 Multi-line macros are not handled properly.
 @item
 Re-indenting large regions or expressions can be slow.
-@item
-Use with Emacs 18 can be slow and annoying.  You should seriously
-consider upgrading to Emacs 19.
 @item
 Add-on fill packages may not work as well as @ccmode{}'s built-in
 filling routines.  I no longer recommend you use @code{filladapt} to
 fill comments.
 Usenet newsgroup @code{gnu.emacs.bug}.  You can send other questions,
 suggestions, and kudos to @code{cc-mode-help@@python.org}, or
 @code{help-gnu-emacs@@prep.ai.mit.edu} which is mirrored on newsgroup
 @code{gnu.emacs.help}.
+There are two mailing lists for @ccmode{}.  One is a general discussion
+list and the other is an announce-only list.  You do not need to
+subscribe to either list, but if you want to, only subscribe to one of
+these.  Announcements of new releases get sent to both lists.  To join
+the general discussion list, send a message with the word
+@emph{subscribe} in the body of the message to
+@code{cc-mode-victims-request@@python.org}.  To join just the
+announce-only list, send a message with the word @emph{subscribe} in the
+body of the message to @code{cc-mode-announce-request@@python.org}.
+Both mailing lists are managed by Majordomo, and if you are successfully
+subscribed, you will receive an email message with more information on
+using the list.
 @c !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 @node    Concept Index, Command Index,  Mailing Lists and Submitting Bug Reports, Top
 @comment node-name,    next,  previous,      up
 @unnumbered Concept Index

Mercurial > hg > xemacs-beta

comparison man/cc-mode.texi @ 165:5a88923fcbfe r20-3b9