X-Git-Url: https://code.delx.au/gnu-emacs/blobdiff_plain/4d0108a132788e0c3903eb4d5875321ed6e8eef1..b895c72059521fec064ff27b4cfcfa4104081c4e:/doc/misc/cc-mode.texi diff --git a/doc/misc/cc-mode.texi b/doc/misc/cc-mode.texi index 1b79640d77..bc8d24fd99 100644 --- a/doc/misc/cc-mode.texi +++ b/doc/misc/cc-mode.texi @@ -83,12 +83,12 @@ the second with them pointing to the XEmacs manuals. @setfilename ../../info/ccmode.info @settitle CC Mode Manual -@documentencoding UTF-8 +@include docstyle.texi @footnotestyle end @c The following four macros generate the filenames and titles of the @c main (X)Emacs manual and the Elisp/Lispref manual. Leave the -@c Texinfo variable `XEMACS' unset to generate a GNU Emacs version, set it +@c Texinfo variable 'XEMACS' unset to generate a GNU Emacs version, set it @c to generate an XEmacs version, e.g., with @c "makeinfo -DXEMACS cc-mode.texi". @ifset XEMACS @@ -157,7 +157,7 @@ CC Mode @copying This manual is for CC Mode in Emacs. -Copyright @copyright{} 1995--2015 Free Software Foundation, Inc. +Copyright @copyright{} 1995--2016 Free Software Foundation, Inc. @quotation Permission is granted to copy, distribute and/or modify this document @@ -378,7 +378,7 @@ This manual describes @ccmode{} version 5.32. @comment Release.py script can update the version number automatically -@ccmode{} supports the editing of K&R and ANSI C, C++, Objective-C, +@ccmode{} supports the editing of C, C++, Objective-C, Java, CORBA's Interface Definition Language, Pike@footnote{A C-like scripting language with its roots in the LPC language used in some MUD engines. See @uref{http://pike.ida.liu.se/}.} and AWK files. In this @@ -1038,7 +1038,7 @@ Movement}. They might be removed from a future release of @ccmode{}. Since there's a lot of normal text in comments and string literals, @ccmode{} provides features to edit these like in text mode. The goal is to do it seamlessly, i.e., you can use auto fill mode, sentence and -paragraph movement, paragraph filling, adaptive filling etc. wherever +paragraph movement, paragraph filling, adaptive filling etc.@: wherever there's a piece of normal text without having to think much about it. @ccmode{} keeps the indentation, fixes suitable comment line prefixes, and so on. @@ -1156,7 +1156,7 @@ When this is enabled (which it normally is), indentation commands such as @kbd{C-j} indent lines of code according to their syntactic structure. Otherwise, a line is simply indented to the same level as the previous one and @kbd{@key{TAB}} adjusts the indentation in steps -of `c-basic-offset'. +of @code{c-basic-offset}. @end table Full details on how these minor modes work are at @ref{Electric Keys}, @@ -2045,7 +2045,7 @@ conflict). The value may also be an association list to specify different comment styles for different languages. The symbol for the major mode is then looked up in the alist, and the value of that element is interpreted as -above if found. If it isn't found then the symbol `other' is looked up +above if found. If it isn't found then the symbol @code{other} is looked up and its value is used instead. The default value for @code{c-doc-comment-style} is @@ -2461,7 +2461,7 @@ handled a little differently from the other style variables. It's default global binding is the empty list @code{nil}, rather than @code{set-from-style}. Before the style system is initialized, you can add individual elements to @code{c-offsets-alist} by calling -@code{c-set-offset}(@pxref{c-offsets-alist}) just like you would set +@code{c-set-offset} (@pxref{c-offsets-alist}) just like you would set other style variables with @code{setq}. Those elements will then prevail when the style system later initializes a buffer-local copy of @code{c-offsets-alist}. @@ -3299,7 +3299,7 @@ only the symbol @code{after}, then the brace hangs on the right side of the line, as in: @example -// here, open braces always `hang' +// here, open braces always 'hang' void spam( int i ) @{ if( i == 7 ) @{ dosomething(i); @@ -3992,7 +3992,7 @@ Hitting @kbd{C-c C-s} on line 4 gives us: @cindex substatement block @noindent which tells us that this is a brace that @emph{opens} a substatement -block. @footnote{A @dfn{substatement} is the line after a +block.@footnote{A @dfn{substatement} is the line after a conditional statement, such as @code{if}, @code{else}, @code{while}, @code{do}, @code{switch}, etc. A @dfn{substatement block} is a brace block following one of these conditional statements.} @@ -4765,10 +4765,10 @@ covered are illustrated by this C++ example: 2: const 3: @{ 4: /* this line starts a multiline - 5: * comment. This line should get `c' syntax */ + 5: * comment. This line should get 'c' syntax */ 6: 7: char* a_multiline_string = "This line starts a multiline \ - 8: string. This line should get `string' syntax."; + 8: string. This line should get 'string' syntax."; 9: 10: note: 11: @{ @@ -5234,13 +5234,13 @@ This command changes the entry for a syntactic symbol in the current binding of @code{c-offsets-alist}, or it inserts a new entry if there isn't already one for that syntactic symbol. -You can use @code{c-set-offsets} interactively within a @ccmode{} +You can use @code{c-set-offset} interactively within a @ccmode{} buffer to make experimental changes to your indentation settings. @kbd{C-c C-o} prompts you for the syntactic symbol to change (defaulting to that of the current line) and the new offset (defaulting to the current offset). -@code{c-set-offsets} takes two arguments when used programmatically: +@code{c-set-offset} takes two arguments when used programmatically: @var{symbol}, the syntactic element symbol to change and @var{offset}, the new offset for that syntactic element. You can call the command in your @file{.emacs} to change the global binding of @@ -6860,7 +6860,7 @@ to change some of the actual values. @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! @node Performance Issues, Limitations and Known Bugs, Sample Init File, Top @comment node-name, next, previous, up -@chapter Performance Issues +@appendix Performance Issues @cindex performance @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! @@ -6969,7 +6969,7 @@ more info. @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! @node Limitations and Known Bugs, FAQ, Performance Issues, Top @comment node-name, next, previous, up -@chapter Limitations and Known Bugs +@appendix Limitations and Known Bugs @cindex limitations @cindex bugs @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! @@ -7140,7 +7140,7 @@ of XEmacs since 19.16. Due to release schedule skew, it is likely that all of these Emacsen have old versions of @ccmode{} and so should be upgraded. Access to the @ccmode{} source code, as well as more detailed information on Emacsen -compatibility, etc. are all available on the web site: +compatibility, etc.@: are all available on the web site: @quotation @uref{http://cc-mode.sourceforge.net/} @@ -7173,11 +7173,12 @@ configuration. In that case, we'd appreciate it if you isolate the Emacs Lisp code that triggers the bug and include it in your report. @cindex bug report mailing list -Bug reports should be sent to @email{bug-cc-mode@@gnu.org}. You can -also send other questions and suggestions (kudos? @t{;-)} to that -address. It's a mailing list which you can join or browse an archive -of; see the web site at @uref{http://cc-mode.sourceforge.net/} for -further details. +Reporting a bug using @code{c-submit-bug-report} files it in +the GNU Bug Tracker at @url{http://debbugs.gnu.org}, then sends it on +to @email{bug-cc-mode@@gnu.org}. You can also send reports, other +questions, and suggestions (kudos?@: @t{;-)} to that address. It's a +mailing list which you can join or browse an archive of; see the web site at +@uref{http://cc-mode.sourceforge.net/} for further details. @cindex announcement mailing list If you want to get announcements of new @ccmode{} releases, send the