Commit | Line | Data |
---|---|---|
6bf7aab6 DL |
1 | \input texinfo |
2 | ||
6b61353c KH |
3 | @c Notes to self regarding line handling: |
4 | @c | |
5 | @c Empty lines are often significant before @end directives; avoid them. | |
6 | @c | |
7 | @c Empty lines before and after @example directives are significant in | |
8 | @c info output but not in TeX. Empty lines inside @example directives | |
9 | @c are significant. | |
10 | ||
11 | @c Conventions for formatting examples: | |
12 | @c o If the example contains empty lines then put the surrounding empty | |
13 | @c lines inside the @example directives. Put them outside otherwise. | |
14 | @c o Use @group inside the example only if it shows indentation where | |
15 | @c the relation between lines inside is relevant. | |
16 | @c o Format line number columns like this: | |
17 | @c 1: foo | |
18 | @c 2: bar | |
19 | @c ^ one space | |
20 | @c ^^ two columns, right alignment | |
21 | @c o Check line lengths in TeX output; they can typically be no longer | |
22 | @c than 70 chars, 60 if the paragraph is indented. | |
23 | ||
24 | @comment TBD: Document the finer details of statement anchoring? | |
25 | ||
6bf7aab6 DL |
26 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
27 | @comment %**start of header (This is for running Texinfo on a region) | |
28 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
29 | ||
d7bd46ed GM |
30 | @comment No overfull hbox marks in the dvi file. |
31 | @finalout | |
6bf7aab6 | 32 | |
94cae5a8 | 33 | @setfilename ../info/ccmode |
cb7f2e96 | 34 | @settitle CC Mode Manual |
d7bd46ed | 35 | @footnotestyle end |
6bf7aab6 DL |
36 | |
37 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
38 | @comment @setchapternewpage odd !! we don't want blank pages !! | |
39 | @comment %**end of header (This is for running Texinfo on a region) | |
40 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
41 | ||
42 | ||
43 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6b61353c | 44 | @comment |
6bf7aab6 DL |
45 | @comment Texinfo manual for CC Mode |
46 | @comment Generated from the original README file by Krishna Padmasola | |
47 | @comment <krishna@earth-gw.njit.edu> | |
cb7f2e96 GM |
48 | @comment |
49 | @comment Authors: | |
50 | @comment Barry A. Warsaw | |
51 | @comment Martin Stjernholm | |
52 | @comment | |
f214c025 | 53 | @comment Maintained by Martin Stjernholm <bug-cc-mode@gnu.org> |
6b61353c | 54 | @comment |
6bf7aab6 DL |
55 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
56 | ||
6b61353c KH |
57 | @comment Define an index for syntactic symbols. |
58 | @defindex ss | |
59 | ||
60 | @comment Combine key, syntactic symbol and concept indices into one. | |
61 | @syncodeindex ss cp | |
62 | @syncodeindex ky cp | |
63 | ||
18f952d5 KB |
64 | @copying |
65 | This manual is for CC Mode in Emacs. | |
cb7f2e96 | 66 | |
6b61353c KH |
67 | Copyright @copyright{} 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, |
68 | 2003 Free Software Foundation, Inc. | |
94cae5a8 | 69 | |
18f952d5 | 70 | @quotation |
94cae5a8 GM |
71 | Permission is granted to copy, distribute and/or modify this document |
72 | under the terms of the GNU Free Documentation License, Version 1.1 or | |
73 | any later version published by the Free Software Foundation; with the | |
74 | Invariant Sections being ``The GNU Manifesto'', ``Distribution'' and | |
75 | ``GNU GENERAL PUBLIC LICENSE'', with the Front-Cover texts being ``A GNU | |
76 | Manual'', and with the Back-Cover Texts as in (a) below. A copy of the | |
77 | license is included in the section entitled ``GNU Free Documentation | |
78 | License'' in the Emacs manual. | |
79 | ||
80 | (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify | |
81 | this GNU Manual, like GNU software. Copies published by the Free | |
82 | Software Foundation raise funds for GNU development.'' | |
83 | ||
84 | This document is part of a collection distributed under the GNU Free | |
85 | Documentation License. If you want to distribute this document | |
86 | separately from the collection, you can do so by adding a copy of the | |
87 | license to the document, as described in section 6 of the license. | |
18f952d5 KB |
88 | @end quotation |
89 | @end copying | |
90 | ||
18f952d5 KB |
91 | @comment Info directory entry for use by install-info. The indentation |
92 | @comment here is by request from the FSF folks. | |
93 | @dircategory Emacs | |
94 | @direntry | |
6b61353c KH |
95 | * CC Mode: (ccmode). Emacs mode for editing C, C++, Objective-C, |
96 | Java, Pike, AWK, and CORBA IDL code. | |
18f952d5 | 97 | @end direntry |
6bf7aab6 DL |
98 | |
99 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
cb7f2e96 | 100 | @comment TeX title page |
6bf7aab6 DL |
101 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
102 | ||
103 | @titlepage | |
104 | @sp 10 | |
105 | ||
6b61353c | 106 | @center @titlefont{CC Mode 5.30} |
6bf7aab6 DL |
107 | @sp 2 |
108 | @center @subtitlefont{A GNU Emacs mode for editing C and C-like languages} | |
109 | @sp 2 | |
6b61353c | 110 | @center Barry A. Warsaw, Martin Stjernholm, Alan Mackenzie (AWK support) |
6bf7aab6 DL |
111 | |
112 | @page | |
113 | @vskip 0pt plus 1filll | |
18f952d5 | 114 | @insertcopying |
6bf7aab6 DL |
115 | @end titlepage |
116 | ||
6bf7aab6 DL |
117 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
118 | @comment The Top node contains the master menu for the Info file. | |
119 | @comment This appears only in the Info file, not the printed manual. | |
120 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
121 | ||
d7bd46ed GM |
122 | @node Top, Introduction, (dir), (dir) |
123 | @comment node-name, next, previous, up | |
124 | ||
125 | @macro ccmode | |
126 | CC Mode | |
127 | @end macro | |
128 | ||
129 | @ifinfo | |
130 | @top @ccmode{} | |
6bf7aab6 | 131 | |
d7bd46ed | 132 | @ccmode{} is a GNU Emacs mode for editing files containing C, C++, |
6b61353c KH |
133 | Objective-C, Java, CORBA IDL (and the variants PSDL and CIDL), Pike |
134 | code and to a certain extent, AWK code @xref{AWK Mode}. It provides | |
135 | syntax-based indentation, font locking, and has several handy commands | |
136 | and some minor modes to make the editing easier. It does not provide | |
137 | tools to look up and navigate between functions, classes etc - there are | |
138 | other packages for that. | |
d7bd46ed | 139 | @end ifinfo |
6bf7aab6 DL |
140 | |
141 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
142 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
143 | ||
144 | @menu | |
d7bd46ed GM |
145 | * Introduction:: |
146 | * Getting Connected:: | |
6b61353c | 147 | * Indentation Engine:: |
6bf7aab6 | 148 | * Minor Modes:: |
d7bd46ed | 149 | * Text Filling and Line Breaking:: |
6b61353c KH |
150 | * Macro Handling:: |
151 | * Font Locking:: | |
6bf7aab6 DL |
152 | * Commands:: |
153 | * Customizing Indentation:: | |
154 | * Syntactic Symbols:: | |
d7bd46ed | 155 | * Indentation Functions:: |
6b61353c KH |
156 | * AWK Mode:: |
157 | * Odds and Ends:: | |
6bf7aab6 | 158 | * Performance Issues:: |
cb7f2e96 | 159 | * Limitations and Known Bugs:: |
6bf7aab6 | 160 | * Frequently Asked Questions:: |
d7bd46ed | 161 | * Getting the Latest CC Mode Release:: |
d7bd46ed | 162 | * Mailing Lists and Submitting Bug Reports:: |
cb7f2e96 | 163 | * Sample .emacs File:: |
d7bd46ed GM |
164 | |
165 | --- Indices --- | |
166 | ||
6b61353c | 167 | * Command and Function Index:: |
d7bd46ed | 168 | * Variable Index:: |
6b61353c | 169 | * Concept Index:: |
d7bd46ed | 170 | |
6b61353c | 171 | @detailmenu |
d7bd46ed GM |
172 | --- The Detailed Node Listing --- |
173 | ||
6b61353c | 174 | Indentation Engine |
d7bd46ed GM |
175 | |
176 | * Syntactic Analysis:: | |
177 | * Indentation Calculation:: | |
178 | ||
179 | Minor Modes | |
180 | ||
181 | * Auto-newline Insertion:: | |
182 | * Hungry-deletion of Whitespace:: | |
183 | ||
6b61353c KH |
184 | Font Locking |
185 | ||
186 | * Font Locking Preliminaries:: | |
187 | * Faces:: | |
188 | * Documentation Comments:: | |
189 | ||
d7bd46ed GM |
190 | Auto-newline Insertion |
191 | ||
192 | * Hanging Braces:: | |
193 | * Hanging Colons:: | |
6b61353c | 194 | * Hanging Semicolons and Commas:: |
d7bd46ed GM |
195 | * Other Electric Commands:: |
196 | * Clean-ups:: | |
197 | ||
198 | Commands | |
199 | ||
200 | * Indentation Commands:: | |
201 | * Movement Commands:: | |
202 | * Other Commands:: | |
203 | ||
204 | Customizing Indentation | |
205 | ||
206 | * Interactive Customization:: | |
207 | * Permanent Customization:: | |
208 | * Hooks:: | |
209 | * Styles:: | |
210 | * Advanced Customizations:: | |
211 | ||
212 | Styles | |
213 | ||
214 | * Built-in Styles:: | |
6b61353c | 215 | * Choosing a Style:: |
d7bd46ed GM |
216 | * Adding Styles:: |
217 | * File Styles:: | |
218 | ||
219 | Advanced Customizations | |
220 | ||
221 | * Custom Indentation Functions:: | |
222 | * Custom Brace and Colon Hanging:: | |
6b61353c | 223 | * Customizing Semicolons and Commas:: |
d7bd46ed | 224 | * Other Special Indentations:: |
6b61353c KH |
225 | |
226 | AWK Mode | |
227 | ||
228 | * Initialising AWK Mode:: | |
229 | * AWK Mode Font Locking:: | |
230 | * AWK Mode Defuns:: | |
231 | @end detailmenu | |
6bf7aab6 DL |
232 | @end menu |
233 | ||
d7bd46ed | 234 | |
6bf7aab6 | 235 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
d7bd46ed GM |
236 | @node Introduction, Getting Connected, Top, Top |
237 | @comment node-name, next, previous, up | |
6b61353c | 238 | @chapter Introduction |
6bf7aab6 DL |
239 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
240 | ||
6bf7aab6 DL |
241 | @cindex BOCM |
242 | ||
d7bd46ed | 243 | Welcome to @ccmode{}, a GNU Emacs mode for editing files containing C, |
6b61353c KH |
244 | C++, Objective-C, Java, CORBA IDL (and the variants CORBA PSDL and |
245 | CIDL), Pike and to a certain extent, AWK code (@pxref{AWK Mode}). This | |
246 | incarnation of the mode is descended from @file{c-mode.el} (also called | |
247 | ``Boring Old C Mode'' or BOCM @t{:-)}, and @file{c++-mode.el} version 2, | |
248 | which Barry has been maintaining since 1992. Late in 1997, Martin | |
d7bd46ed | 249 | joined the @ccmode{} Maintainers Team, and implemented the Pike support. |
6b61353c KH |
250 | As of 2000 Martin has taken over as the sole maintainer. @ccmode{} did |
251 | not originally contain the font lock support for its languages --- that | |
252 | was added in version 5.30. AWK support was also added in 5.30 by Alan | |
253 | Mackenzie. | |
d7bd46ed GM |
254 | |
255 | This manual describes @ccmode{} | |
256 | @comment The following line must appear on its own, so that the automated | |
6b61353c | 257 | version 5.30. |
d7bd46ed | 258 | @comment Release.py script can update the version number automatically |
6bf7aab6 | 259 | |
6b61353c KH |
260 | @ccmode{} supports the editing of K&R and ANSI C, C++, Objective-C, |
261 | Java, CORBA's Interface Definition Language, Pike@footnote{A C-like | |
262 | scripting language with its roots in the LPC language used in some MUD | |
263 | engines. See @uref{http://pike.ida.liu.se/}.} and AWK files. In this | |
264 | way, you can easily set up consistent font locking and coding styles for | |
265 | use in editing all of these languages, although AWK is not yet as | |
266 | uniformly integrated as the other languages. | |
6bf7aab6 DL |
267 | |
268 | @findex c-mode | |
269 | @findex c++-mode | |
270 | @findex objc-mode | |
271 | @findex java-mode | |
272 | @findex idl-mode | |
d7bd46ed | 273 | @findex pike-mode |
6b61353c | 274 | @findex awk-mode |
94cae5a8 | 275 | Note that the name of this package is ``@ccmode{},'' but there is no top |
6bf7aab6 | 276 | level @code{cc-mode} entry point. All of the variables, commands, and |
6b61353c | 277 | functions in @ccmode{} are prefixed with @code{c-@var{thing}}, and |
d7bd46ed | 278 | @code{c-mode}, @code{c++-mode}, @code{objc-mode}, @code{java-mode}, |
6b61353c KH |
279 | @code{idl-mode}, @code{pike-mode}, and @code{awk-mode} entry points are |
280 | provided. This package is intended to be a replacement for | |
281 | @file{c-mode.el}, @file{c++-mode.el} and @file{awk-mode.el}. | |
282 | ||
283 | @c @cindex @file{cc-compat.el} file | |
284 | @c This distribution also contains a file | |
285 | @c called @file{cc-compat.el} which should ease your transition from BOCM | |
286 | @c to @ccmode{}. If you have a BOCM configuration you are really happy | |
287 | @c with, and want to postpone learning how to configure @ccmode{}, take a | |
288 | @c look at that file. It maps BOCM configuration variables to @ccmode{}'s | |
289 | @c indentation model. It is not actively supported so for the long run, | |
290 | @c you should learn how to customize @ccmode{} to support your coding | |
291 | @c style. | |
6bf7aab6 DL |
292 | |
293 | A special word of thanks goes to Krishna Padmasola for his work in | |
294 | converting the original @file{README} file to Texinfo format. I'd also | |
295 | like to thank all the @ccmode{} victims who help enormously during the | |
296 | early beta stages of @ccmode{}'s development. | |
297 | ||
298 | ||
299 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6b61353c | 300 | @node Getting Connected, Indentation Engine, Introduction, Top |
d7bd46ed | 301 | @comment node-name, next, previous, up |
6b61353c | 302 | @chapter Getting Connected |
6bf7aab6 DL |
303 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
304 | ||
305 | If you got this version of @ccmode{} with Emacs or XEmacs, it should | |
306 | work just fine right out of the box. Note however that you may not have | |
307 | the latest @ccmode{} release and may want to upgrade your copy. | |
308 | ||
309 | If you are upgrading an existing @ccmode{} installation, please see the | |
310 | @file{README} file for installation details. @ccmode{} may not work | |
311 | with older versions of Emacs or XEmacs. See the @ccmode{} release notes | |
6b61353c KH |
312 | at @uref{http://cc-mode.sourceforge.net} for the latest information on |
313 | Emacs version and package compatibility (@pxref{Getting the Latest CC | |
314 | Mode Release}). | |
6bf7aab6 | 315 | |
6b61353c | 316 | @deffn Command c-version |
6bf7aab6 DL |
317 | @findex version (c-) |
318 | You can find out what version of @ccmode{} you are using by visiting a C | |
319 | file and entering @kbd{M-x c-version RET}. You should see this message in | |
320 | the echo area: | |
6bf7aab6 | 321 | |
6b61353c | 322 | @example |
6bf7aab6 | 323 | Using CC Mode version 5.XX |
6bf7aab6 DL |
324 | @end example |
325 | ||
326 | @noindent | |
327 | where @samp{XX} is the minor release number. | |
6b61353c | 328 | @end deffn |
6bf7aab6 DL |
329 | |
330 | ||
331 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6b61353c | 332 | @node Indentation Engine, Minor Modes, Getting Connected, Top |
d7bd46ed | 333 | @comment node-name, next, previous, up |
6b61353c | 334 | @chapter Indentation Engine |
6bf7aab6 DL |
335 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
336 | ||
6b61353c KH |
337 | @ccmode{} has an indentation engine that provides a flexible and general |
338 | mechanism for customizing indentation. It separates indentation | |
339 | calculation into two steps: first, @ccmode{} analyzes the line of code | |
340 | being indented to determine the kind of language construct it's looking | |
341 | at, then it applies user defined offsets to the current line based on | |
342 | this analysis. | |
6bf7aab6 DL |
343 | |
344 | This section will briefly cover how indentation is calculated in | |
6b61353c KH |
345 | @ccmode{}. It is important to understand the indentation model being |
346 | used so that you will know how to customize @ccmode{} for your personal | |
347 | coding style. All the details are in @ref{Customizing Indentation}, and | |
348 | later chapters. | |
349 | ||
350 | @defopt c-syntactic-indentation | |
351 | @vindex syntactic-indentation (c-) | |
352 | Syntactic analysis for indentation is done when this is non-@code{nil} | |
353 | (which is the default). When it's @code{nil} every line is just | |
354 | indented to the same level as the previous one, and @kbd{TAB} | |
355 | (@code{c-indent-command}) adjusts the indentation in steps of | |
356 | @code{c-basic-offset}. The indentation style has no effect, nor any of | |
357 | the indentation associated variables, e.g. @code{c-special-indent-hook}. | |
358 | @end defopt | |
6bf7aab6 DL |
359 | |
360 | @menu | |
361 | * Syntactic Analysis:: | |
362 | * Indentation Calculation:: | |
363 | @end menu | |
364 | ||
365 | ||
366 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6b61353c | 367 | @node Syntactic Analysis, Indentation Calculation, , Indentation Engine |
d7bd46ed | 368 | @comment node-name, next, previous, up |
6b61353c | 369 | @section Syntactic Analysis |
d7bd46ed | 370 | @cindex syntactic analysis |
6bf7aab6 DL |
371 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
372 | ||
6bf7aab6 | 373 | @cindex relative buffer position |
6b61353c | 374 | @cindex syntactic symbols |
6bf7aab6 DL |
375 | @cindex syntactic component |
376 | @cindex syntactic component list | |
6bf7aab6 DL |
377 | The first thing @ccmode{} does when indenting a line of code, is to |
378 | analyze the line, determining the @dfn{syntactic component list} of the | |
d7bd46ed | 379 | construct on that line. A syntactic component consists of a pair of |
6b61353c KH |
380 | elements (in lisp parlance, a @emph{cons cell}), the first being |
381 | a @dfn{syntactic symbol}, the second being a @dfn{relative | |
6bf7aab6 | 382 | buffer position}. Syntactic symbols describe elements of C code |
6b61353c | 383 | @footnote{Unless otherwise noted, the term ``C code'' refers to all |
d7bd46ed GM |
384 | the C-like languages.}, e.g. @code{statement}, @code{substatement}, |
385 | @code{class-open}, @code{class-close}, etc. @xref{Syntactic Symbols}, | |
386 | for a complete list of currently recognized syntactic symbols and their | |
387 | semantics. The style variable @code{c-offsets-alist} also contains the | |
388 | list of currently supported syntactic symbols. | |
6bf7aab6 DL |
389 | |
390 | Conceptually, a line of C code is always indented relative to the | |
391 | indentation of some line higher up in the buffer. This is represented | |
392 | by the relative buffer position in the syntactic component. | |
393 | ||
394 | Here is an example. Suppose we had the following code as the only thing | |
d7bd46ed GM |
395 | in a C++ buffer @footnote{The line numbers in this and future examples |
396 | don't actually appear in the buffer, of course!}: | |
6bf7aab6 | 397 | |
6b61353c KH |
398 | @example |
399 | 1: void swap( int& a, int& b ) | |
400 | 2: @{ | |
401 | 3: int tmp = a; | |
402 | 4: a = b; | |
403 | 5: b = tmp; | |
404 | 6: @} | |
6bf7aab6 DL |
405 | @end example |
406 | ||
407 | @kindex C-c C-s | |
408 | @findex c-show-syntactic-information | |
409 | @findex show-syntactic-information (c-) | |
6b61353c KH |
410 | We can use the command @kbd{C-c C-s} (bound to |
411 | @code{c-show-syntactic-information}) to simply report what the | |
6bf7aab6 | 412 | syntactic analysis is for the current line. Running this command on |
6b61353c KH |
413 | line 4 of this example, we'd see in the echo area@footnote{With a |
414 | universal argument (i.e. @kbd{C-u C-c C-s}) the analysis is inserted | |
415 | into the buffer as a comment on the current line.}: | |
6bf7aab6 | 416 | |
6b61353c KH |
417 | @example |
418 | ((statement 35)) | |
6bf7aab6 DL |
419 | @end example |
420 | ||
421 | This tells us that the line is a statement and it is indented relative | |
422 | to buffer position 35, which happens to be the @samp{i} in @code{int} on | |
423 | line 3. If you were to move point to line 3 and hit @kbd{C-c C-s}, you | |
424 | would see: | |
6bf7aab6 | 425 | |
6b61353c KH |
426 | @example |
427 | ((defun-block-intro 29)) | |
6bf7aab6 DL |
428 | @end example |
429 | ||
430 | This indicates that the @samp{int} line is the first statement in a top | |
431 | level function block, and is indented relative to buffer position 29, | |
432 | which is the brace just after the function header. | |
433 | ||
434 | Here's another example: | |
6bf7aab6 | 435 | |
6b61353c KH |
436 | @example |
437 | 1: int add( int val, int incr, int doit ) | |
438 | 2: @{ | |
439 | 3: if( doit ) | |
440 | 4: @{ | |
441 | 5: return( val + incr ); | |
442 | 6: @} | |
443 | 7: return( val ); | |
444 | 8: @} | |
6bf7aab6 DL |
445 | @end example |
446 | ||
447 | @noindent | |
448 | Hitting @kbd{C-c C-s} on line 4 gives us: | |
6bf7aab6 | 449 | |
6b61353c KH |
450 | @example |
451 | ((substatement-open 46)) | |
6bf7aab6 DL |
452 | @end example |
453 | ||
454 | @cindex substatement | |
d7bd46ed | 455 | @cindex substatement block |
6bf7aab6 DL |
456 | @noindent |
457 | which tells us that this is a brace that @emph{opens} a substatement | |
458 | block. @footnote{A @dfn{substatement} is the line after a | |
459 | conditional statement, such as @code{if}, @code{else}, @code{while}, | |
460 | @code{do}, @code{switch}, etc. A @dfn{substatement | |
461 | block} is a brace block following one of these conditional statements.} | |
462 | ||
463 | @cindex comment-only line | |
464 | Syntactic component lists can contain more than one component, and | |
465 | individual syntactic components need not have relative buffer positions. | |
466 | The most common example of this is a line that contains a @dfn{comment | |
467 | only line}. | |
6bf7aab6 | 468 | |
6b61353c KH |
469 | @example |
470 | 1: void draw_list( List<Drawables>& drawables ) | |
471 | 2: @{ | |
472 | 3: // call the virtual draw() method on each element in list | |
473 | 4: for( int i=0; i < drawables.count(), ++i ) | |
474 | 5: @{ | |
475 | 6: drawables[i].draw(); | |
476 | 7: @} | |
477 | 8: @} | |
6bf7aab6 DL |
478 | @end example |
479 | ||
480 | @noindent | |
481 | Hitting @kbd{C-c C-s} on line 3 of this example gives: | |
6bf7aab6 | 482 | |
6b61353c KH |
483 | @example |
484 | ((comment-intro) (defun-block-intro 46)) | |
6bf7aab6 DL |
485 | @end example |
486 | ||
487 | @noindent | |
488 | and you can see that the syntactic component list contains two syntactic | |
489 | components. Also notice that the first component, | |
490 | @samp{(comment-intro)} has no relative buffer position. | |
491 | ||
492 | ||
493 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6b61353c | 494 | @node Indentation Calculation, , Syntactic Analysis, Indentation Engine |
d7bd46ed | 495 | @comment node-name, next, previous, up |
6b61353c KH |
496 | @section Indentation Calculation |
497 | @cindex indentation | |
6bf7aab6 DL |
498 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
499 | ||
6bf7aab6 | 500 | Indentation for a line is calculated using the syntactic |
d7bd46ed | 501 | component list derived in step 1 above (@pxref{Syntactic Analysis}). |
6bf7aab6 DL |
502 | Each component contributes to the final total indentation of the line in |
503 | two ways. | |
504 | ||
505 | First, the syntactic symbols are looked up in the @code{c-offsets-alist} | |
d7bd46ed GM |
506 | style variable, which is an association list of syntactic symbols and |
507 | the offsets to apply for those symbols. These offsets are added to a | |
6bf7aab6 DL |
508 | running total. |
509 | ||
510 | Second, if the component has a relative buffer position, @ccmode{} | |
511 | adds the column number of that position to the running total. By adding | |
512 | up the offsets and columns for every syntactic component on the list, | |
513 | the final total indentation for the current line is computed. | |
514 | ||
515 | Let's use our two code examples above to see how this works. Here is | |
516 | our first example again: | |
6bf7aab6 | 517 | |
6b61353c KH |
518 | @example |
519 | 1: void swap( int& a, int& b ) | |
520 | 2: @{ | |
521 | 3: int tmp = a; | |
522 | 4: a = b; | |
523 | 5: b = tmp; | |
524 | 6: @} | |
6bf7aab6 DL |
525 | @end example |
526 | ||
6b61353c | 527 | Let's say point is on line 3 and we hit the @kbd{TAB} key to reindent |
6bf7aab6 DL |
528 | the line. Remember that the syntactic component list for that |
529 | line is: | |
6bf7aab6 | 530 | |
6b61353c KH |
531 | @example |
532 | ((defun-block-intro 29)) | |
6bf7aab6 DL |
533 | @end example |
534 | ||
535 | @noindent | |
536 | @ccmode{} looks up @code{defun-block-intro} in the | |
d7bd46ed GM |
537 | @code{c-offsets-alist} style variable. Let's say it finds the value |
538 | @samp{4}; it adds this to the running total (initialized to zero), | |
539 | yielding a running total indentation of 4 spaces. | |
6bf7aab6 DL |
540 | |
541 | Next @ccmode{} goes to buffer position 29 and asks for the current | |
542 | column. This brace is in column zero, so @ccmode{} | |
543 | adds @samp{0} to the running total. Since there is only one syntactic | |
544 | component on the list for this line, indentation calculation is | |
545 | complete, and the total indentation for the line | |
546 | is 4 spaces. | |
547 | ||
548 | Here's another example: | |
6bf7aab6 | 549 | |
6b61353c KH |
550 | @example |
551 | 1: int add( int val, int incr, int doit ) | |
552 | 2: @{ | |
553 | 3: if( doit ) | |
554 | 4: @{ | |
555 | 5: return( val + incr ); | |
556 | 6: @} | |
557 | 7: return( val ); | |
558 | 8: @} | |
6bf7aab6 DL |
559 | @end example |
560 | ||
561 | If we were to hit @kbd{TAB} on line 4 in the above example, the same | |
562 | basic process is performed, despite the differences in the syntactic | |
563 | component list. Remember that the list for this line is: | |
6bf7aab6 | 564 | |
6b61353c KH |
565 | @example |
566 | ((substatement-open 46)) | |
6bf7aab6 DL |
567 | @end example |
568 | ||
569 | Here, @ccmode{} first looks up the @code{substatement-open} symbol | |
570 | in @code{c-offsets-alist}. Let's say it finds the value @samp{4}. This | |
571 | yields a running total of 4. @ccmode{} then goes to | |
572 | buffer position 46, which is the @samp{i} in @code{if} on line 3. This | |
573 | character is in the fourth column on that line so adding this to the | |
574 | running total yields an indentation for the line of 8 spaces. | |
575 | ||
576 | Simple, huh? | |
577 | ||
578 | Actually, the mode usually just does The Right Thing without you having | |
579 | to think about it in this much detail. But when customizing | |
580 | indentation, it's helpful to understand the general indentation model | |
581 | being used. | |
582 | ||
6bf7aab6 DL |
583 | As you configure @ccmode{}, you might want to set the variable |
584 | @code{c-echo-syntactic-information-p} to non-@code{nil} so that the | |
585 | syntactic component list and calculated offset will always be echoed in | |
586 | the minibuffer when you hit @kbd{TAB}. | |
587 | ||
588 | ||
589 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6b61353c | 590 | @node Minor Modes, Text Filling and Line Breaking, Indentation Engine, Top |
d7bd46ed | 591 | @comment node-name, next, previous, up |
6b61353c | 592 | @chapter Minor Modes |
6bf7aab6 DL |
593 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
594 | ||
595 | @ccmode{} contains two minor-mode-like features that you should | |
6b61353c | 596 | find useful while entering new C code. The first is called |
6bf7aab6 DL |
597 | @dfn{auto-newline} mode, and the second is called @dfn{hungry-delete} |
598 | mode. These minor modes can be toggled on and off independently, and | |
599 | @ccmode{} can be configured so that it starts up with any | |
600 | combination of these minor modes. By default, both of these minor modes | |
601 | are turned off. | |
602 | ||
603 | The state of the minor modes is always reflected in the minor mode list | |
604 | on the modeline of the @ccmode{} buffer. When auto-newline mode is | |
6b61353c KH |
605 | enabled, you will see @samp{C/a} on the mode line@footnote{The @samp{C} |
606 | would be replaced with the name of the language in question for the | |
607 | other languages @ccmode{} supports.}. When hungry delete mode is | |
608 | enabled you will see @samp{C/h} and if both modes were enabled, you'd | |
609 | see @samp{C/ah}. | |
6bf7aab6 DL |
610 | |
611 | @kindex C-c C-a | |
612 | @kindex C-c C-d | |
613 | @kindex C-c C-t | |
614 | @findex c-toggle-hungry-state | |
615 | @findex c-toggle-auto-state | |
616 | @findex c-toggle-auto-hungry-state | |
617 | @findex toggle-hungry-state (c-) | |
618 | @findex toggle-auto-state (c-) | |
619 | @findex toggle-auto-hungry-state (c-) | |
47d7776c | 620 | @ccmode{} provides key bindings which allow you to toggle the minor |
6bf7aab6 | 621 | modes on the fly while editing code. To toggle just the auto-newline |
6b61353c KH |
622 | state, hit @kbd{C-c C-a} (bound to @code{c-toggle-auto-state}). When |
623 | you do this, you should see the @samp{a} indicator either appear or | |
624 | disappear on the modeline. Similarly, to toggle just the | |
625 | hungry-delete state, use @kbd{C-c C-d} (@code{c-toggle-hungry-state}), | |
626 | and to toggle both states, use @kbd{C-c C-t} | |
627 | (@code{c-toggle-auto-hungry-state}). | |
6bf7aab6 DL |
628 | |
629 | To set up the auto-newline and hungry-delete states to your preferred | |
630 | values, you would need to add some lisp to your @file{.emacs} file that | |
631 | called one of the @code{c-toggle-*-state} functions directly. When | |
632 | called programmatically, each function takes a numeric value, where | |
633 | a positive number enables the minor mode, a negative number disables the | |
634 | mode, and zero toggles the current state of the mode. | |
635 | ||
636 | So for example, if you wanted to enable both auto-newline and | |
637 | hungry-delete for all your C file editing, you could add the following | |
638 | to your @file{.emacs} file: | |
6bf7aab6 | 639 | |
6b61353c | 640 | @example |
6bf7aab6 | 641 | (add-hook 'c-mode-common-hook |
6b61353c | 642 | (lambda () (c-toggle-auto-hungry-state 1))) |
6bf7aab6 DL |
643 | @end example |
644 | ||
6bf7aab6 | 645 | @menu |
d7bd46ed GM |
646 | * Auto-newline Insertion:: |
647 | * Hungry-deletion of Whitespace:: | |
6bf7aab6 DL |
648 | @end menu |
649 | ||
6bf7aab6 | 650 | |
d7bd46ed GM |
651 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
652 | @node Auto-newline Insertion, Hungry-deletion of Whitespace, , Minor Modes | |
653 | @comment node-name, next, previous, up | |
6b61353c KH |
654 | @section Auto-newline Insertion |
655 | @cindex auto-newline | |
6bf7aab6 DL |
656 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
657 | ||
6b61353c | 658 | @cindex electric characters |
6bf7aab6 | 659 | Auto-newline minor mode works by enabling certain @dfn{electric |
6b61353c KH |
660 | characters}. Special characters such as the left and right braces, |
661 | colons, semicolons, etc., have been made electric to perform some | |
662 | magic formatting in addition to inserting the typed character. As a | |
663 | general rule, electric characters are only electric when the following | |
664 | conditions apply: | |
6bf7aab6 DL |
665 | |
666 | @itemize @bullet | |
667 | @item | |
668 | Auto-newline minor mode is enabled, as evidenced by a @samp{C/a} or | |
669 | @samp{C/ah} indicator on the modeline. | |
670 | ||
6b61353c | 671 | @item |
6bf7aab6 DL |
672 | @cindex literal |
673 | @cindex syntactic whitespace | |
6bf7aab6 | 674 | The character was not typed inside of a literal @footnote{A |
6b61353c | 675 | @dfn{literal} is defined as any comment, string, or preprocessor macro |
6bf7aab6 DL |
676 | definition. These constructs are also known as @dfn{syntactic |
677 | whitespace} since they are usually ignored when scanning C code.}. | |
678 | ||
679 | @item | |
6bf7aab6 DL |
680 | No numeric argument was supplied to the command (i.e. it was typed as |
681 | normal, with no @kbd{C-u} prefix). | |
6bf7aab6 DL |
682 | @end itemize |
683 | ||
684 | @menu | |
685 | * Hanging Braces:: | |
686 | * Hanging Colons:: | |
6b61353c | 687 | * Hanging Semicolons and Commas:: |
d7bd46ed | 688 | * Other Electric Commands:: |
6bf7aab6 DL |
689 | * Clean-ups:: |
690 | @end menu | |
691 | ||
6bf7aab6 | 692 | |
d7bd46ed GM |
693 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
694 | @node Hanging Braces, Hanging Colons, , Auto-newline Insertion | |
695 | @comment node-name, next, previous, up | |
696 | @subsection Hanging Braces | |
697 | @cindex hanging braces | |
6bf7aab6 DL |
698 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
699 | ||
700 | @findex c-electric-brace | |
701 | @findex electric-brace (c-) | |
6b61353c KH |
702 | @kindex @{ |
703 | @kindex @} | |
704 | ||
6bf7aab6 DL |
705 | When you type either an open or close brace (i.e. @kbd{@{} or @kbd{@}}), |
706 | the electric command @code{c-electric-brace} gets run. This command has | |
707 | two electric formatting behaviors. First, it will perform some | |
6b61353c | 708 | reindentation of the line the brace was typed on, and second, it will |
6bf7aab6 | 709 | add various newlines before and/or after the typed brace. |
6b61353c | 710 | Reindentation occurs automatically whenever the electric behavior is |
6bf7aab6 | 711 | enabled. If the brace ends up on a line other than the one it was typed |
6b61353c | 712 | on, then that line is also reindented. |
d7bd46ed GM |
713 | |
714 | The default in auto-newline mode is to insert newlines both before and | |
715 | after a brace, but that can be controlled by the | |
6b61353c KH |
716 | @code{c-hanging-braces-alist} style variable. |
717 | ||
718 | @defopt c-hanging-braces-alist | |
719 | @vindex hanging-braces-alist (c-) | |
720 | ||
721 | This variable contains a mapping between syntactic symbols related to | |
722 | braces, and a list of places to insert a newline. The syntactic symbols | |
723 | that are useful for this list are @code{brace-list-intro}, | |
724 | @code{statement-cont}, @code{inexpr-class-open}, | |
725 | @code{inexpr-class-close}, and all the @code{*-open} and @code{*-close} | |
726 | symbols. @xref{Syntactic Symbols}, for a more detailed description of | |
727 | these syntactic symbols, except for @code{inexpr-class-open} and | |
728 | @code{inexpr-class-close}, which aren't actual syntactic symbols. | |
d7bd46ed GM |
729 | |
730 | The braces of anonymous inner classes in Java are given the special | |
731 | symbols @code{inexpr-class-open} and @code{inexpr-class-close}, so that | |
732 | they can be distinguished from the braces of normal classes@footnote{The | |
6b61353c | 733 | braces of anonymous classes produce a combination of |
d7bd46ed GM |
734 | @code{inexpr-class}, and @code{class-open} or @code{class-close} in |
735 | normal indentation analysis.}. | |
736 | ||
6b61353c KH |
737 | Note that the aggregate constructs in Pike mode, @samp{(@{}, @samp{@})}, |
738 | @samp{([}, @samp{])}, and @samp{(<}, @samp{>)}, do not count as brace | |
739 | lists in this regard, even though they do for normal indentation | |
740 | purposes. It's currently not possible to set automatic newlines on | |
741 | these constructs. | |
742 | ||
6bf7aab6 | 743 | The value associated with each syntactic symbol in this association list |
6b61353c | 744 | is called an @var{action}, which can be either a function or a list. |
393759c7 | 745 | @xref{Custom Brace and Colon Hanging}, for a more detailed discussion of |
6b61353c | 746 | using a function as a brace hanging @var{action}. |
6bf7aab6 | 747 | |
6b61353c | 748 | When the @var{action} is a list, it can contain any combination of the |
6bf7aab6 DL |
749 | symbols @code{before} and @code{after}, directing @ccmode{} where to |
750 | put newlines in relationship to the brace being inserted. Thus, if the | |
751 | list contains only the symbol @code{after}, then the brace is said to | |
752 | @dfn{hang} on the right side of the line, as in: | |
6bf7aab6 | 753 | |
6b61353c | 754 | @example |
6bf7aab6 DL |
755 | // here, open braces always `hang' |
756 | void spam( int i ) @{ | |
757 | if( i == 7 ) @{ | |
758 | dosomething(i); | |
759 | @} | |
760 | @} | |
6bf7aab6 DL |
761 | @end example |
762 | ||
763 | When the list contains both @code{after} and @code{before}, the braces | |
764 | will appear on a line by themselves, as shown by the close braces in the | |
765 | above example. The list can also be empty, in which case no newlines | |
766 | are added either before or after the brace. | |
767 | ||
d7bd46ed GM |
768 | If a syntactic symbol is missing entirely from |
769 | @code{c-hanging-braces-alist}, it's treated in the same way as an | |
6b61353c | 770 | @var{action} with a list containing @code{before} and @code{after}, so |
d7bd46ed GM |
771 | that braces by default end up on their own line. |
772 | ||
6bf7aab6 | 773 | For example, the default value of @code{c-hanging-braces-alist} is: |
6bf7aab6 | 774 | |
6b61353c KH |
775 | @example |
776 | ((brace-list-open) | |
777 | (brace-entry-open) | |
778 | (statement-cont) | |
779 | (substatement-open after) | |
780 | (block-close . c-snug-do-while) | |
781 | (extern-lang-open after) | |
782 | (inexpr-class-open after) | |
783 | (inexpr-class-close before)) | |
6bf7aab6 DL |
784 | @end example |
785 | ||
6b61353c KH |
786 | @noindent which says that @code{brace-list-open}, |
787 | @code{brace-entry-open} and @code{statement-cont}@footnote{Brace lists | |
788 | inside statements, such as initializers for static array variables | |
789 | inside functions in C, are recognized as @code{statement-cont}. All | |
790 | normal substatement blocks are recognized with other symbols.} braces | |
791 | should both hang on the right side and allow subsequent text to follow | |
792 | on the same line as the brace. Also, @code{substatement-open}, | |
793 | @code{extern-lang-open}, and @code{inexpr-class-open} braces should hang | |
794 | on the right side, but subsequent text should follow on the next line. | |
795 | The opposite holds for @code{inexpr-class-close} braces; they won't | |
796 | hang, but the following text continues on the same line. Here, in the | |
797 | @code{block-close} entry, you also see an example of using a function as | |
798 | an @var{action}. In all other cases, braces are put on a line by | |
799 | themselves. | |
800 | @end defopt | |
6bf7aab6 DL |
801 | |
802 | ||
803 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6b61353c | 804 | @node Hanging Colons, Hanging Semicolons and Commas, Hanging Braces, Auto-newline Insertion |
d7bd46ed GM |
805 | @comment node-name, next, previous, up |
806 | @subsection Hanging Colons | |
807 | @cindex hanging colons | |
6bf7aab6 DL |
808 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
809 | ||
d7bd46ed GM |
810 | Using a mechanism similar to brace hanging (@pxref{Hanging Braces}), |
811 | colons can also be made to hang using the style variable | |
6b61353c KH |
812 | @code{c-hanging-colons-alist}. |
813 | ||
814 | @defopt c-hanging-colons-alist | |
815 | @vindex hanging-colons-alist (c-) | |
816 | ||
817 | The syntactic symbols appropriate for this association list are: | |
818 | @code{case-label}, @code{label}, @code{access-label}, | |
819 | @code{member-init-intro}, and @code{inher-intro}. Note however that for | |
820 | @code{c-hanging-colons-alist}, @var{action}s as functions are not | |
821 | supported. See also @ref{Custom Brace and Colon Hanging} for details. | |
6bf7aab6 | 822 | |
6bf7aab6 DL |
823 | In C++, double-colons are used as a scope operator but because these |
824 | colons always appear right next to each other, newlines before and after | |
825 | them are controlled by a different mechanism, called @dfn{clean-ups} in | |
393759c7 | 826 | @ccmode{}. @xref{Clean-ups}, for details. |
6b61353c | 827 | @end defopt |
6bf7aab6 DL |
828 | |
829 | ||
830 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6b61353c | 831 | @node Hanging Semicolons and Commas, Other Electric Commands, Hanging Colons, Auto-newline Insertion |
d7bd46ed | 832 | @comment node-name, next, previous, up |
6b61353c KH |
833 | @subsection Hanging Semicolons and Commas |
834 | @cindex hanging semicolons | |
d7bd46ed | 835 | @cindex hanging commas |
6bf7aab6 DL |
836 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
837 | ||
838 | Semicolons and commas are also electric in @ccmode{}, but since | |
839 | these characters do not correspond directly to syntactic symbols, a | |
840 | different mechanism is used to determine whether newlines should be | |
841 | automatically inserted after these characters. @xref{Customizing | |
6b61353c | 842 | Semicolons and Commas}, for details. |
6bf7aab6 DL |
843 | |
844 | ||
845 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6b61353c | 846 | @node Other Electric Commands, Clean-ups, Hanging Semicolons and Commas, Auto-newline Insertion |
d7bd46ed GM |
847 | @comment node-name, next, previous, up |
848 | @subsection Other Electric Commands | |
6bf7aab6 DL |
849 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
850 | ||
6b61353c KH |
851 | A few other keys also provide electric behavior, often only to reindent |
852 | the line. Common to all of them is that they only reindent if used in | |
853 | normal code (as opposed to in a string literal or comment), and | |
854 | @code{c-syntactic-indentation} isn't @code{nil}. They are: | |
855 | ||
856 | @table @kbd | |
857 | @item # | |
6bf7aab6 DL |
858 | @kindex # |
859 | @findex c-electric-pound | |
6bf7aab6 | 860 | @findex electric-pound (c-) |
6b61353c | 861 | @vindex c-electric-pound-behavior |
6bf7aab6 | 862 | @vindex electric-pound-behavior (c-) |
6b61353c KH |
863 | Pound (bound to @code{c-electric-pound}) is electric when typed as the |
864 | first non-whitespace character on a line and not within a macro | |
865 | definition. In this case, the variable @code{c-electric-pound-behavior} | |
866 | is consulted for the electric behavior. This variable takes a list | |
867 | value, although the only element currently defined is @code{alignleft}, | |
868 | which tells this command to force the @samp{#} character into column | |
869 | zero. This is useful for entering preprocessor macro definitions. | |
870 | ||
871 | Pound is not electric in AWK buffers, where @samp{#} starts a comment, | |
872 | and is bound to @code{self-insert-command} like any typical printable | |
873 | character. | |
6bf7aab6 | 874 | |
6b61353c KH |
875 | @item * |
876 | @kindex * | |
877 | @itemx / | |
878 | @kindex / | |
6bf7aab6 | 879 | @findex c-electric-star |
6bf7aab6 | 880 | @findex electric-star (c-) |
6b61353c | 881 | @findex c-electric-slash |
6bf7aab6 | 882 | @findex electric-slash (c-) |
6b61353c KH |
883 | Stars and slashes (bound to @code{c-electric-star} and |
884 | @code{c-electric-slash} respectively) are also electric under certain | |
885 | circumstances. If a @samp{*} is inserted as the second character of a C | |
886 | style block comment on a comment-only line, then the comment delimiter | |
887 | is indented as defined by @code{c-offsets-alist}. A comment-only line | |
888 | is defined as a line which contains only a comment, as in: | |
889 | ||
6bf7aab6 DL |
890 | @example |
891 | @group | |
177c0ea7 | 892 | void spam( int i ) |
6bf7aab6 | 893 | @{ |
6b61353c KH |
894 | // this is a comment-only line... |
895 | if( i == 7 ) // but this is not | |
6bf7aab6 DL |
896 | @{ |
897 | dosomething(i); | |
898 | @} | |
899 | @} | |
6bf7aab6 DL |
900 | @end group |
901 | @end example | |
902 | ||
6b61353c KH |
903 | Likewise, if a @samp{/} is inserted as the second slash in a C++ style |
904 | line comment (also only on a comment-only line), then the line is | |
905 | indented as defined by @code{c-offsets-alist}. | |
6bf7aab6 | 906 | |
6b61353c KH |
907 | In AWK mode, @samp{*} and @samp{/} do not delimit comments and are |
908 | bound to @code{self-insert-command}. | |
909 | ||
910 | @item < | |
6bf7aab6 | 911 | @kindex < |
6b61353c | 912 | @itemx > |
6bf7aab6 | 913 | @kindex > |
6b61353c KH |
914 | @findex c-electric-lt-gt |
915 | @findex electric-lt-gt (c-) | |
916 | Less-than and greater-than signs (bound to @code{c-electric-lt-gt}) are | |
6bf7aab6 | 917 | electric, but only in C++ mode. Hitting the second of two @kbd{<} or |
6b61353c | 918 | @kbd{>} keys reindents the line if it is a C++ style stream operator. |
6bf7aab6 | 919 | |
6b61353c | 920 | @item ( |
d7bd46ed | 921 | @kindex ( |
6b61353c | 922 | @itemx ) |
d7bd46ed | 923 | @kindex ) |
6b61353c KH |
924 | @findex c-electric-paren |
925 | @findex electric-paren (c-) | |
926 | The normal parenthesis characters @samp{(} and @samp{)} reindent the | |
927 | current line. This is useful for getting the closing parenthesis of an | |
928 | argument list aligned automatically. | |
929 | @end table | |
930 | ||
931 | @deffn Command c-electric-continued-statement | |
932 | @findex electric-continued-statement (c-) | |
933 | ||
934 | Certain keywords, depending on language, are electric to cause | |
935 | reindentation when they are preceded only by whitespace on the line. | |
936 | The keywords are those that continue an earlier statement instead of | |
937 | starting a new one: @code{else}, @code{while}, @code{catch} (only in C++ | |
938 | and Java) and @code{finally} (only in Java). | |
939 | ||
940 | An example: | |
941 | ||
942 | @example | |
943 | @group | |
944 | for (i = 0; i < 17; i++) | |
945 | if (a[i]) | |
946 | res += a[i]->offset; | |
947 | else | |
948 | @end group | |
949 | @end example | |
950 | ||
951 | Here, the @code{else} should be indented like the preceding @code{if}, | |
952 | since it continues that statement. @ccmode{} will automatically reindent | |
953 | it after the @code{else} has been typed in full, since it's not until | |
954 | then it's possible to decide whether it's a new statement or a | |
955 | continuation of the preceding @code{if}. | |
956 | ||
957 | @vindex abbrev-mode | |
958 | @findex abbrev-mode | |
959 | @cindex Abbrev mode | |
960 | @ccmode{} uses Abbrev mode (@pxref{Abbrevs,,, emacs, The Emacs Editor}) | |
961 | to accomplish this. It's therefore turned on by default in all language | |
962 | modes except IDL mode, since CORBA IDL doesn't have any statements. | |
963 | @end deffn | |
6bf7aab6 | 964 | |
6bf7aab6 | 965 | |
d7bd46ed GM |
966 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
967 | @node Clean-ups, , Other Electric Commands, Auto-newline Insertion | |
968 | @comment node-name, next, previous, up | |
969 | @subsection Clean-ups | |
970 | @cindex clean-ups | |
6bf7aab6 DL |
971 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
972 | ||
cb7f2e96 GM |
973 | @dfn{Clean-ups} are mechanisms complementary to colon and brace hanging. |
974 | On the surface, it would seem that clean-ups overlap the functionality | |
975 | provided by the @code{c-hanging-*-alist} variables. Clean-ups are | |
94cae5a8 | 976 | however used to adjust code ``after-the-fact,'' i.e. to adjust the |
cb7f2e96 GM |
977 | whitespace in constructs after they are typed. |
978 | ||
979 | Most of the clean-ups are only applicable to counteract automatically | |
980 | inserted newlines, and will therefore only have any effect if the | |
981 | auto-newline minor mode is turned on. Others will work all the time. | |
6bf7aab6 | 982 | |
6b61353c | 983 | @defopt c-cleanup-list |
d7bd46ed | 984 | @vindex cleanup-list (c-) |
6bf7aab6 | 985 | @cindex literal |
6b61353c | 986 | |
d7bd46ed | 987 | You can configure @ccmode{}'s clean-ups by setting the style variable |
6bf7aab6 | 988 | @code{c-cleanup-list}, which is a list of clean-up symbols. By default, |
d7bd46ed GM |
989 | @ccmode{} cleans up only the @code{scope-operator} construct, which is |
990 | necessary for proper C++ support. Note that clean-ups are only | |
991 | performed when the construct does not occur within a literal | |
992 | (@pxref{Auto-newline Insertion}), and when there is nothing but | |
993 | whitespace appearing between the individual components of the construct. | |
6b61353c | 994 | @end defopt |
6bf7aab6 | 995 | |
6b61353c | 996 | These are the clean-ups that are only active in the auto-newline minor |
cb7f2e96 | 997 | mode: |
6bf7aab6 | 998 | |
6b61353c KH |
999 | @c TBD: Would like to use some sort of @deffoo here; @table indents a |
1000 | @c bit too much in dvi output. | |
1001 | @table @code | |
1002 | @item brace-else-brace | |
1003 | Clean up @samp{@} else @{} constructs by placing the entire construct on | |
1004 | a single line. Clean-up occurs when the open brace after the | |
1005 | @samp{else} is typed. So for example, this: | |
1006 | ||
6bf7aab6 DL |
1007 | @example |
1008 | @group | |
6bf7aab6 DL |
1009 | void spam(int i) |
1010 | @{ | |
6b61353c | 1011 | if( i==7 ) @{ |
6bf7aab6 DL |
1012 | dosomething(); |
1013 | @} | |
1014 | else | |
1015 | @{ | |
6bf7aab6 DL |
1016 | @end group |
1017 | @end example | |
6b61353c | 1018 | |
6bf7aab6 | 1019 | @noindent |
6b61353c KH |
1020 | appears like this after the last open brace is typed: |
1021 | ||
6bf7aab6 DL |
1022 | @example |
1023 | @group | |
6bf7aab6 DL |
1024 | void spam(int i) |
1025 | @{ | |
1026 | if( i==7 ) @{ | |
1027 | dosomething(); | |
1028 | @} else @{ | |
6bf7aab6 DL |
1029 | @end group |
1030 | @end example | |
1031 | ||
6b61353c KH |
1032 | @item brace-elseif-brace |
1033 | Similar to the @code{brace-else-brace} clean-up, but this cleans up | |
1034 | @samp{@} else if (...) @{} constructs. For example: | |
1035 | ||
6bf7aab6 DL |
1036 | @example |
1037 | @group | |
6bf7aab6 DL |
1038 | void spam(int i) |
1039 | @{ | |
6b61353c | 1040 | if( i==7 ) @{ |
6bf7aab6 DL |
1041 | dosomething(); |
1042 | @} | |
d7bd46ed GM |
1043 | else if( i==3 ) |
1044 | @{ | |
6bf7aab6 DL |
1045 | @end group |
1046 | @end example | |
6b61353c | 1047 | |
6bf7aab6 | 1048 | @noindent |
6b61353c KH |
1049 | appears like this after the last open parenthesis is typed: |
1050 | ||
d7bd46ed GM |
1051 | @example |
1052 | @group | |
d7bd46ed GM |
1053 | void spam(int i) |
1054 | @{ | |
1055 | if( i==7 ) @{ | |
1056 | dosomething(); | |
1057 | @} else if( i==3 ) | |
1058 | @{ | |
d7bd46ed GM |
1059 | @end group |
1060 | @end example | |
6b61353c | 1061 | |
d7bd46ed | 1062 | @noindent |
6b61353c KH |
1063 | and like this after the last open brace is typed: |
1064 | ||
6bf7aab6 DL |
1065 | @example |
1066 | @group | |
6bf7aab6 DL |
1067 | void spam(int i) |
1068 | @{ | |
1069 | if( i==7 ) @{ | |
1070 | dosomething(); | |
1071 | @} else if( i==3 ) @{ | |
6bf7aab6 DL |
1072 | @end group |
1073 | @end example | |
1074 | ||
6b61353c KH |
1075 | @item brace-catch-brace |
1076 | Analogous to @code{brace-elseif-brace}, but cleans up @samp{@} catch | |
1077 | (...) @{} in C++ and Java mode. | |
1078 | ||
1079 | @item empty-defun-braces | |
1080 | Clean up braces following a top-level function or class definition that | |
1081 | contains no body. Clean up occurs when the closing brace is typed. | |
1082 | Thus the following: | |
d7bd46ed | 1083 | |
6bf7aab6 DL |
1084 | @example |
1085 | @group | |
6bf7aab6 DL |
1086 | class Spam |
1087 | @{ | |
1088 | @} | |
6bf7aab6 DL |
1089 | @end group |
1090 | @end example | |
6b61353c | 1091 | |
6bf7aab6 DL |
1092 | @noindent |
1093 | is transformed into this when the close brace is typed: | |
6b61353c | 1094 | |
6bf7aab6 DL |
1095 | @example |
1096 | @group | |
6bf7aab6 DL |
1097 | class Spam |
1098 | @{@} | |
6bf7aab6 DL |
1099 | @end group |
1100 | @end example | |
1101 | ||
6b61353c KH |
1102 | @item defun-close-semi |
1103 | Clean up the terminating semicolon on top-level function or class | |
1104 | definitions when they follow a close brace. Clean up occurs when the | |
1105 | semicolon is typed. So for example, the following: | |
1106 | ||
6bf7aab6 DL |
1107 | @example |
1108 | @group | |
6bf7aab6 DL |
1109 | class Spam |
1110 | @{ | |
1111 | @} | |
1112 | ; | |
6bf7aab6 DL |
1113 | @end group |
1114 | @end example | |
6b61353c | 1115 | |
6bf7aab6 | 1116 | @noindent |
6b61353c | 1117 | is transformed into this when the semicolon is typed: |
6bf7aab6 DL |
1118 | |
1119 | @example | |
1120 | @group | |
6bf7aab6 DL |
1121 | class Spam |
1122 | @{ | |
1123 | @}; | |
6bf7aab6 DL |
1124 | @end group |
1125 | @end example | |
1126 | ||
6b61353c KH |
1127 | @item list-close-comma |
1128 | Clean up commas following braces in array and aggregate initializers. | |
1129 | Clean up occurs when the comma is typed. | |
1130 | ||
1131 | @item scope-operator | |
1132 | Clean up double colons which may designate a C++ scope operator split | |
1133 | across multiple lines@footnote{Certain C++ constructs introduce | |
1134 | ambiguous situations, so @code{scope-operator} clean-ups may not always | |
1135 | be correct. This usually only occurs when scoped identifiers appear in | |
1136 | switch label tags.}. Clean up occurs when the second colon is typed. | |
1137 | You will always want @code{scope-operator} in the @code{c-cleanup-list} | |
1138 | when you are editing C++ code. | |
1139 | @end table | |
6bf7aab6 | 1140 | |
cb7f2e96 GM |
1141 | The following clean-ups are always active when they occur on |
1142 | @code{c-cleanup-list}, and are thus not affected by the auto-newline | |
1143 | minor mode: | |
1144 | ||
6b61353c KH |
1145 | @table @code |
1146 | @item space-before-funcall | |
1147 | Insert a space between the function name and the opening parenthesis of | |
1148 | a function call. This produces function calls in the style mandated by | |
1149 | the GNU coding standards, e.g. @samp{signal (SIGINT, SIG_IGN)} and | |
1150 | @samp{abort ()}. Clean up occurs when the opening parenthesis is typed. | |
1151 | ||
1152 | @item compact-empty-funcall | |
1153 | Clean up any space between the function name and the opening parenthesis | |
1154 | of a function call that has no arguments. This is typically used | |
1155 | together with @code{space-before-funcall} if you prefer the GNU function | |
1156 | call style for functions with arguments but think it looks ugly when | |
1157 | it's only an empty parenthesis pair. I.e. you will get @samp{signal | |
1158 | (SIGINT, SIG_IGN)}, but @samp{abort()}. Clean up occurs when the | |
1159 | closing parenthesis is typed. | |
1160 | @end table | |
cb7f2e96 | 1161 | |
6bf7aab6 DL |
1162 | |
1163 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
d7bd46ed GM |
1164 | @node Hungry-deletion of Whitespace, , Auto-newline Insertion, Minor Modes |
1165 | @comment node-name, next, previous, up | |
6b61353c KH |
1166 | @section Hungry-deletion of Whitespace |
1167 | @cindex hungry-deletion | |
6bf7aab6 DL |
1168 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
1169 | ||
1170 | Hungry deletion of whitespace, or as it more commonly called, | |
1171 | @dfn{hungry-delete mode}, is a simple feature that some people find | |
1172 | extremely useful. In fact, you might find yourself wanting | |
1173 | hungry-delete in @strong{all} your editing modes! | |
1174 | ||
1175 | @kindex DEL | |
6b61353c KH |
1176 | @kindex C-d |
1177 | ||
1178 | In a nutshell, when hungry-delete mode is enabled, hitting the @kbd{DEL} | |
1179 | or @kbd{C-d} keys will consume all preceding or following whitespace, | |
1180 | including newlines and tabs. This can really cut down on the number of | |
1181 | times you have to hit these keys if, for example, you made a mistake on | |
6bf7aab6 DL |
1182 | the preceding line. |
1183 | ||
6b61353c | 1184 | @deffn Command c-electric-backspace |
6bf7aab6 | 1185 | @findex electric-backspace (c-) |
6b61353c KH |
1186 | This command is run by default when you hit the @kbd{DEL} key. It |
1187 | deletes any amount of whitespace in the backwards direction if | |
1188 | hungry-delete mode is enabled. When it's disabled, or when used with | |
1189 | a prefix argument or in a literal (@pxref{Auto-newline Insertion}), | |
1190 | the function contained in the @code{c-backspace-function} variable is | |
1191 | called with the prefix argument. | |
1192 | @end deffn | |
1193 | ||
1194 | @defvar c-backspace-function | |
6bf7aab6 | 1195 | @vindex backspace-function (c-) |
6b61353c KH |
1196 | @findex backward-delete-char-untabify |
1197 | Hook that gets called by @code{c-electric-backspace} when it doesn't | |
1198 | do an ``electric'' deletion of the preceding whitespace. The default | |
1199 | value is @code{backward-delete-char-untabify}. | |
1200 | @end defvar | |
1201 | ||
1202 | @deffn Command c-electric-delete-forward | |
1203 | @findex electric-delete-forward (c-) | |
1204 | This function, which is bound to @kbd{C-d} by default, works just like | |
1205 | @code{c-electric-backspace} but in the forward direction. When it | |
1206 | doesn't do an ``electric'' deletion of the following whitespace, it | |
1207 | calls the function in @code{c-delete-function} with its prefix | |
1208 | argument. | |
1209 | @end deffn | |
1210 | ||
1211 | @defvar c-delete-function | |
1212 | @vindex delete-function (c-) | |
1213 | @findex delete-char | |
1214 | Hook that gets called by @code{c-electric-delete-forward} when it | |
1215 | doesn't do an ``electric'' deletion of the following whitespace. The | |
1216 | default value is @code{delete-char}. | |
1217 | @end defvar | |
1218 | ||
1219 | Above we have only talked about the @kbd{DEL} and @kbd{C-d} key events, | |
1220 | without connecting them to the physical keys commonly known as | |
1221 | @key{Backspace} and @key{Delete}. The default behavior of those two | |
1222 | depends on the flavor of (X)Emacs you are using. | |
6bf7aab6 DL |
1223 | |
1224 | @findex c-electric-delete | |
1225 | @findex electric-delete (c-) | |
6b61353c | 1226 | @vindex delete-key-deletes-forward |
6bf7aab6 | 1227 | |
6b61353c KH |
1228 | In XEmacs 20.3 and beyond, the @key{Backspace} key is bound to |
1229 | @code{c-electric-backspace} and the @key{Delete} key is bound to | |
1230 | @code{c-electric-delete}. You control the direction it deletes in by | |
1231 | setting the variable @code{delete-key-deletes-forward}, a standard | |
1232 | XEmacs variable. When this variable is non-@code{nil}, | |
1233 | @code{c-electric-delete} will do forward deletion with | |
1234 | @code{c-electric-delete-forward}, otherwise it does backward deletion | |
1235 | with @code{c-electric-backspace}. | |
1236 | ||
1237 | In other Emacs versions, @ccmode{} doesn't bind either @key{Backspace} | |
1238 | or @key{Delete}. In XEmacs 19 and Emacs prior to 21 that means that | |
1239 | it's up to you to fix them. Emacs 21 automatically binds them as | |
1240 | appropriate to @kbd{DEL} and @kbd{C-d}. | |
1241 | ||
1242 | Another way to use hungry deletion is to bind | |
1243 | @code{c-hungry-backspace} and @code{c-hungry-delete-forward} directly | |
1244 | to keys, and not use the mode toggling. For example @kbd{C-c C-d} and | |
1245 | @kbd{C-c DEL} to match plain @kbd{C-d} and @kbd{DEL}, | |
6bf7aab6 | 1246 | |
6b61353c KH |
1247 | @example |
1248 | (add-hook | |
1249 | 'c-mode-common-hook | |
1250 | (lambda () | |
1251 | (define-key c-mode-base-map | |
1252 | [?\C-c ?\d] 'c-hungry-backspace) | |
1253 | (define-key c-mode-base-map | |
1254 | [?\C-c ?\C-d] 'c-hungry-delete-forward))) | |
1255 | @end example | |
6bf7aab6 | 1256 | |
6b61353c KH |
1257 | @deffn Command c-hungry-backspace |
1258 | @findex hungry-backspace (c-) | |
1259 | Delete any amount of whitespace in the backwards direction (regardless | |
1260 | whether hungry-delete mode is enabled or not). | |
1261 | @end deffn | |
6bf7aab6 | 1262 | |
6b61353c KH |
1263 | @deffn Command c-hungry-delete-forward |
1264 | @findex hungry-delete-forward (c-) | |
1265 | Delete any amount of whitespace in the forward direction (regardless | |
1266 | whether hungry-delete mode is enabled or not). | |
1267 | @end deffn | |
6bf7aab6 DL |
1268 | |
1269 | ||
1270 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6b61353c | 1271 | @node Text Filling and Line Breaking, Macro Handling, Minor Modes, Top |
d7bd46ed | 1272 | @comment node-name, next, previous, up |
6b61353c KH |
1273 | @chapter Text Filling and Line Breaking |
1274 | @cindex text filling | |
1275 | @cindex line breaking | |
1276 | @cindex comment handling | |
6bf7aab6 DL |
1277 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
1278 | ||
d7bd46ed GM |
1279 | Since there's a lot of normal text in comments and string literals, |
1280 | @ccmode{} provides features to edit these like in text mode. The goal | |
1281 | is to do it as seamlessly as possible, i.e. you can use auto fill mode, | |
1282 | sentence and paragraph movement, paragraph filling, adaptive filling etc | |
1283 | wherever there's a piece of normal text without having to think much | |
1284 | about it. @ccmode{} should keep the indentation, fix the comment line | |
1285 | decorations, and so on, for you. It does that by hooking in on the | |
1286 | different line breaking functions and tuning relevant variables as | |
1287 | necessary. | |
1288 | ||
1289 | @vindex c-comment-prefix-regexp | |
1290 | @vindex comment-prefix-regexp (c-) | |
1291 | @cindex comment line prefix | |
1292 | @vindex comment-start | |
1293 | @vindex comment-end | |
1294 | @vindex comment-start-skip | |
1295 | @vindex paragraph-start | |
1296 | @vindex paragraph-separate | |
1297 | @vindex paragraph-ignore-fill-prefix | |
1298 | @vindex adaptive-fill-mode | |
1299 | @vindex adaptive-fill-regexp | |
1300 | @vindex adaptive-fill-first-line-regexp | |
1301 | To make Emacs recognize comments and treat text in them as normal | |
1302 | paragraphs, @ccmode{} makes several standard | |
1303 | variables@footnote{@code{comment-start}, @code{comment-end}, | |
1304 | @code{comment-start-skip}, @code{paragraph-start}, | |
1305 | @code{paragraph-separate}, @code{paragraph-ignore-fill-prefix}, | |
1306 | @code{adaptive-fill-mode}, @code{adaptive-fill-regexp}, and | |
1307 | @code{adaptive-fill-first-line-regexp}.} buffer local and modifies them | |
6b61353c KH |
1308 | according to the language syntax and the comment line prefix. |
1309 | ||
1310 | @defopt c-comment-prefix-regexp | |
1311 | @vindex comment-prefix-regexp (c-) | |
1312 | This style variable contains the regexp used to recognize the | |
1313 | @dfn{comment line prefix}, which is the line decoration that starts | |
1314 | every line in a comment. The default is @samp{//+\\|\\**}, which | |
d7bd46ed | 1315 | matches C++ style line comments like |
d7bd46ed | 1316 | |
6b61353c | 1317 | @example |
d7bd46ed | 1318 | // blah blah |
d7bd46ed GM |
1319 | @end example |
1320 | ||
1321 | @noindent | |
1322 | with two or more slashes in front of them, and C style block comments | |
1323 | like | |
6b61353c | 1324 | |
d7bd46ed GM |
1325 | @example |
1326 | @group | |
d7bd46ed GM |
1327 | /* |
1328 | * blah blah | |
1329 | */ | |
d7bd46ed GM |
1330 | @end group |
1331 | @end example | |
1332 | ||
1333 | @noindent | |
1334 | with zero or more stars at the beginning of every line. If you change | |
6b61353c | 1335 | this variable, please make sure it still matches the comment starter |
d7bd46ed | 1336 | (i.e. @code{//}) of line comments @emph{and} the line prefix inside |
6b61353c KH |
1337 | block comments. |
1338 | ||
1339 | @findex c-setup-paragraph-variables | |
1340 | @findex setup-paragraph-variables (c-) | |
1341 | Also note that since @ccmode{} uses the value of | |
d7bd46ed | 1342 | @code{c-comment-prefix-regexp} to set up several other variables at mode |
6b61353c KH |
1343 | initialization, there won't have any effect if you change it inside a |
1344 | @ccmode{} buffer. You need to call the command | |
1345 | @code{c-setup-paragraph-variables} to update those other variables with | |
1346 | the new value. That's also the case if you modify this variable in a | |
1347 | mode hook, since @ccmode{} sets up all variables before calling them. | |
1348 | @end defopt | |
d7bd46ed GM |
1349 | |
1350 | @findex auto-fill-mode | |
6b61353c KH |
1351 | @cindex Auto Fill mode |
1352 | @cindex paragraph filling | |
d7bd46ed GM |
1353 | Line breaks are by default handled (almost) the same regardless whether |
1354 | they are made by auto fill mode (@pxref{Auto Fill,,, emacs, The Emacs | |
1355 | Editor}), paragraph filling (e.g. with @kbd{M-q}), or explicitly with | |
1356 | @kbd{M-j} or similar methods. In string literals, the new line gets the | |
1357 | same indentation as the previous nonempty line (may be changed with the | |
1358 | @code{string} syntactic symbol). In comments, @ccmode{} uses | |
1359 | @code{c-comment-prefix-regexp} to adapt the line prefix from the other | |
1360 | lines in the comment. | |
1361 | ||
1362 | @vindex adaptive-fill-mode | |
6b61353c | 1363 | @cindex Adaptive Fill mode |
d7bd46ed GM |
1364 | @ccmode{} uses adaptive fill mode (@pxref{Adaptive Fill,,, emacs, The |
1365 | Emacs Editor}) to make Emacs correctly keep the line prefix when filling | |
1366 | paragraphs. That also makes Emacs preserve the text indentation | |
1367 | @emph{inside} the comment line prefix. E.g. in the following comment, | |
6b61353c KH |
1368 | both paragraphs will be filled with the left margins of the texts kept |
1369 | intact: | |
1370 | ||
d7bd46ed GM |
1371 | @example |
1372 | @group | |
d7bd46ed GM |
1373 | /* Make a balanced b-tree of the nodes in the incoming |
1374 | * stream. But, to quote the famous words of Donald E. | |
1375 | * Knuth, | |
1376 | * | |
1377 | * Beware of bugs in the above code; I have only | |
1378 | * proved it correct, not tried it. | |
1379 | */ | |
d7bd46ed GM |
1380 | @end group |
1381 | @end example | |
1382 | ||
1383 | @findex c-setup-filladapt | |
1384 | @findex setup-filladapt (c-) | |
1385 | @findex filladapt-mode | |
1386 | @vindex filladapt-mode | |
1387 | @cindex Filladapt mode | |
1388 | It's also possible to use other adaptive filling packages, notably Kyle | |
1389 | E. Jones' Filladapt package@footnote{It's available from | |
1390 | @uref{http://www.wonderworks.com/}. As of version 2.12, it does however | |
1391 | lack a feature that makes it work suboptimally when | |
1392 | @code{c-comment-prefix-regexp} matches the empty string (which it does | |
1393 | by default). A patch for that is available from | |
6b61353c | 1394 | @uref{http://cc-mode.sourceforge.net/,, the CC Mode web site}.}, |
d7bd46ed GM |
1395 | which handles things like bulleted lists nicely. There's a convenience |
1396 | function @code{c-setup-filladapt} that tunes the relevant variables in | |
1397 | Filladapt for use in @ccmode{}. Call it from a mode hook, e.g. with | |
1398 | something like this in your @file{.emacs}: | |
d7bd46ed | 1399 | |
6b61353c | 1400 | @example |
d7bd46ed GM |
1401 | (defun my-c-mode-common-hook () |
1402 | (c-setup-filladapt) | |
1403 | (filladapt-mode 1)) | |
1404 | (add-hook 'c-mode-common-hook 'my-c-mode-common-hook) | |
d7bd46ed | 1405 | @end example |
6bf7aab6 | 1406 | |
6b61353c | 1407 | @defopt c-block-comment-prefix |
d7bd46ed | 1408 | @vindex block-comment-prefix (c-) |
6bf7aab6 DL |
1409 | @vindex c-comment-continuation-stars |
1410 | @vindex comment-continuation-stars (c-) | |
d7bd46ed GM |
1411 | Normally the comment line prefix inserted for a new line inside a |
1412 | comment is deduced from other lines in it. However there's one | |
6b61353c KH |
1413 | situation when there's no hint about what the prefix should look like, |
1414 | namely when a block comment is broken for the first time. This style | |
1415 | variable@footnote{In versions before 5.26, this variable was called | |
1416 | @code{c-comment-continuation-stars}. As a compatibility measure, | |
1417 | @ccmode{} still uses the value on that variable if it's set.} is used | |
1418 | then as the comment prefix. It defaults to @samp{* }, which makes a | |
1419 | comment | |
6bf7aab6 | 1420 | |
6b61353c | 1421 | @example |
d7bd46ed | 1422 | /* Got O(n^2) here, which is a Bad Thing. */ |
d7bd46ed | 1423 | @end example |
6bf7aab6 | 1424 | |
d7bd46ed GM |
1425 | @noindent |
1426 | break into | |
6b61353c | 1427 | |
d7bd46ed GM |
1428 | @example |
1429 | @group | |
d7bd46ed GM |
1430 | /* Got O(n^2) here, |
1431 | * which is a Bad Thing. */ | |
d7bd46ed GM |
1432 | @end group |
1433 | @end example | |
1434 | ||
6b61353c KH |
1435 | Note that it won't work to adjust the indentation by putting leading |
1436 | spaces in @code{c-block-comment-prefix}, since @ccmode{} still uses the | |
1437 | normal indentation engine to indent the line. Thus, the right way to | |
1438 | fix the indentation is by customizing the @code{c} syntactic symbol. It | |
1439 | defaults to @code{c-lineup-C-comments}, which handles the indentation of | |
1440 | most common comment styles, see @ref{Indentation Functions}. | |
1441 | @end defopt | |
d7bd46ed | 1442 | |
6b61353c | 1443 | @defopt c-ignore-auto-fill |
d7bd46ed GM |
1444 | @vindex ignore-auto-fill (c-) |
1445 | When auto fill mode is enabled, @ccmode{} can selectively ignore it | |
1446 | depending on the context the line break would occur in, e.g. to never | |
6b61353c KH |
1447 | break a line automatically inside a string literal. This variable |
1448 | takes a list of symbols for the different contexts where auto-filling | |
1449 | never should occur: | |
d7bd46ed | 1450 | |
6b61353c KH |
1451 | @table @code |
1452 | @item string | |
1453 | Inside a string or character literal. | |
1454 | @item c | |
1455 | Inside a C style block comment. | |
1456 | @item c++ | |
1457 | Inside a C++ style line comment. | |
1458 | @item cpp | |
1459 | Inside a preprocessor directive. | |
1460 | @item code | |
1461 | Anywhere else, i.e. in normal code. | |
1462 | @end table | |
d7bd46ed GM |
1463 | |
1464 | By default, @code{c-ignore-auto-fill} is set to @code{'(string cpp | |
1465 | code)}, which means that auto-filling only occurs in comments when | |
1466 | auto-fill mode is activated. In literals, it's often desirable to have | |
1467 | explicit control over newlines. In preprocessor directives, the | |
1468 | necessary @samp{\} escape character before the newline is not | |
1469 | automatically inserted, so an automatic line break would produce invalid | |
1470 | code. In normal code, line breaks are normally dictated by some logical | |
1471 | structure in the code rather than the last whitespace character, so | |
1472 | automatic line breaks there will produce poor results in the current | |
1473 | implementation. | |
6b61353c | 1474 | @end defopt |
d7bd46ed | 1475 | |
6b61353c | 1476 | The commands that do the actual work follow. |
d7bd46ed GM |
1477 | |
1478 | @table @asis | |
6b61353c | 1479 | @item @kbd{M-q} (@code{c-fill-paragraph}) |
d7bd46ed GM |
1480 | @kindex M-q |
1481 | @findex c-fill-paragraph | |
1482 | @findex fill-paragraph (c-) | |
1483 | @cindex Javadoc markup | |
cb7f2e96 | 1484 | @cindex Pike autodoc markup |
d7bd46ed GM |
1485 | This is the replacement for @code{fill-paragraph} in @ccmode{} |
1486 | buffers. It's used to fill multiline string literals and both block and | |
1487 | line style comments. In Java buffers, the Javadoc markup words are | |
cb7f2e96 GM |
1488 | recognized as paragraph starters. The line oriented Pike autodoc markup |
1489 | words are recognized in the same way in Pike mode. | |
d7bd46ed GM |
1490 | |
1491 | The function keeps the comment starters and enders of block comments as | |
1492 | they were before the filling. This means that a comment ender on the | |
1493 | same line as the paragraph being filled will be filled with the | |
1494 | paragraph, and one on a line by itself will stay as it is. The comment | |
1495 | starter is handled similarly@footnote{This means that the variables | |
1496 | @code{c-hanging-comment-starter-p} and @code{c-hanging-comment-ender-p}, | |
1497 | which controlled this behavior in earlier versions of @ccmode{}, are now | |
1498 | obsolete.}. | |
1499 | ||
6b61353c | 1500 | @item @kbd{M-j} (@code{c-indent-new-comment-line}) |
d7bd46ed GM |
1501 | @kindex M-j |
1502 | @findex c-indent-new-comment-line | |
1503 | @findex indent-new-comment-line (c-) | |
d7bd46ed GM |
1504 | This is the replacement for @code{indent-new-comment-line}. It breaks |
1505 | the line at point and indents the new line like the current one. | |
1506 | ||
1507 | @vindex comment-multi-line | |
1508 | If inside a comment and @code{comment-multi-line} is non-@code{nil}, the | |
1509 | indentation and line prefix are preserved. If inside a comment and | |
1510 | @code{comment-multi-line} is @code{nil}, a new comment of the same type | |
1511 | is started on the next line and indented as appropriate for comments. | |
1512 | ||
6b61353c KH |
1513 | Note that @ccmode{} sets @code{comment-multi-line} to @code{t} at |
1514 | startup. The reason is that @kbd{M-j} could otherwise produce sequences | |
1515 | of single line block comments for texts that should logically be treated | |
1516 | as one comment, and the rest of the paragraph handling code | |
1517 | (e.g. @kbd{M-q} and @kbd{M-a}) can't cope with that, which would lead to | |
1518 | inconsistent behavior. | |
1519 | ||
1520 | @item @kbd{M-x c-context-line-break} | |
d7bd46ed GM |
1521 | @findex c-context-line-break |
1522 | @findex context-line-break (c-) | |
d7bd46ed GM |
1523 | This is a function that works like @code{indent-new-comment-line} in |
1524 | comments and @code{newline-and-indent} elsewhere, thus combining those | |
1525 | two in a way that uses each one in the context it's best suited for. | |
6b61353c KH |
1526 | I.e. in comments the comment line prefix and indentation is kept for |
1527 | the new line, and in normal code it's indented according to context by | |
1528 | the indentation engine. | |
1529 | ||
1530 | In macros it acts like @code{newline-and-indent} but additionally | |
1531 | inserts and optionally aligns the line ending backslash so that the | |
1532 | macro remains unbroken. @xref{Macro Handling}, for details about the | |
1533 | backslash alignment. | |
d7bd46ed GM |
1534 | |
1535 | It's not bound to a key by default, but it's intended to be used on the | |
1536 | @kbd{RET} key. If you like the behavior of @code{newline-and-indent} on | |
6b61353c KH |
1537 | @kbd{RET}, you should consider switching to this function. |
1538 | ||
1539 | @item @kbd{M-x c-context-open-line} | |
1540 | @findex c-context-open-line | |
1541 | @findex context-open-line (c-) | |
1542 | This is to @kbd{C-o} (@kbd{M-x open-line}) as | |
1543 | @code{c-context-line-break} is to @kbd{RET}. I.e. it works just like | |
1544 | @code{c-context-line-break} but leaves the point before the inserted | |
1545 | line break. | |
d7bd46ed | 1546 | @end table |
6bf7aab6 | 1547 | |
d7bd46ed GM |
1548 | |
1549 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6b61353c | 1550 | @node Macro Handling, Font Locking, Text Filling and Line Breaking, Top |
d7bd46ed | 1551 | @comment node-name, next, previous, up |
6b61353c KH |
1552 | @chapter Macro Handling |
1553 | @cindex macros | |
1554 | @cindex preprocessor directives | |
6bf7aab6 DL |
1555 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
1556 | ||
6b61353c KH |
1557 | Preprocessor directives are handled as syntactic whitespace from other |
1558 | code, i.e. they can be interspersed anywhere without affecting the | |
1559 | syntactic analysis, just like comments. | |
6bf7aab6 | 1560 | |
6b61353c KH |
1561 | The code inside macro definitions is still analyzed syntactically so |
1562 | that you get relative indentation there just as you'd get if the same | |
1563 | code was outside a macro. However, since there is no hint about the | |
1564 | syntactic context, i.e. whether the macro expands to an expression, to some | |
1565 | statements, or perhaps to whole functions, the syntactic recognition can be | |
1566 | wrong. @ccmode{} manages to figure it out correctly most of the time, | |
1567 | though. @xref{Syntactic Symbols}, for details about the indentation. | |
6bf7aab6 | 1568 | |
6b61353c KH |
1569 | @defopt c-syntactic-indentation-in-macros |
1570 | @vindex syntactic-indentation-in-macros (c-) | |
1571 | Enable syntactic analysis inside macros, which is the default. If this | |
1572 | is @code{nil}, all lines inside macro definitions are analyzed as | |
1573 | @code{cpp-macro-cont}. | |
1574 | @end defopt | |
6bf7aab6 | 1575 | |
6b61353c KH |
1576 | @ccmode{} provides some tools to help keep the line continuation |
1577 | backslashes in macros neat and tidy: | |
1578 | ||
1579 | @table @asis | |
1580 | @item @kbd{C-c C-\} (@code{c-backslash-region}) | |
1581 | @kindex C-c C-\ | |
1582 | @findex c-backslash-region | |
1583 | @findex backslash-region (c-) | |
1584 | This function inserts and aligns or deletes the end-of-line backslashes | |
1585 | in the current region. | |
1586 | ||
1587 | With no prefix argument, it inserts any missing backslashes and aligns | |
1588 | them according to the @code{c-backslash-column} and | |
1589 | @code{c-backslash-max-column} variables. With a prefix argument, it | |
1590 | deletes any backslashes. | |
1591 | ||
1592 | The function does not modify blank lines at the start of the region. If | |
1593 | the region ends at the start of a line, it always deletes the backslash | |
1594 | (if any) at the end of the previous line. | |
1595 | @end table | |
1596 | ||
1597 | @defopt c-backslash-column | |
1598 | @vindex backslash-column (c-) | |
1599 | @defoptx c-backslash-max-column | |
1600 | @vindex backslash-max-column (c-) | |
1601 | These variables control the alignment columns for line continuation | |
1602 | backslashes in multiline macros. They are used by the functions that | |
1603 | automatically insert or align such backslashes, | |
1604 | e.g. @code{c-backslash-region} and @code{c-context-line-break}. | |
1605 | ||
1606 | @code{c-backslash-column} specifies the minimum column for the | |
1607 | backslashes. If any line in the macro exceeds it then the next tab | |
1608 | stop from that line is used as the alignment column for all the | |
1609 | backslashes, so that they remain in a single column. However, if some | |
1610 | lines exceed @code{c-backslash-max-column} then the backslashes in the | |
1611 | rest of the macro will be kept at that column, so that the | |
1612 | lines which are too long ``stick out'' instead. | |
1613 | @end defopt | |
1614 | ||
1615 | @defopt c-auto-align-backslashes | |
1616 | @vindex auto-align-backslashes (c-) | |
1617 | Align automatically inserted line continuation backslashes if | |
1618 | non-@code{nil}. When line continuation backslashes are inserted | |
1619 | automatically for line breaks in multiline macros, e.g. by | |
1620 | @code{c-context-line-break}, they are aligned with the other backslashes | |
1621 | in the same macro if this flag is set. Otherwise the inserted | |
1622 | backslashes are preceded by a single space. | |
1623 | @end defopt | |
1624 | ||
1625 | The recommended line breaking function, @code{c-context-line-break} | |
1626 | (@pxref{Text Filling and Line Breaking}), is especially nice if you edit | |
1627 | multiline macros frequently. When used inside a macro, it automatically | |
1628 | inserts and adjusts the mandatory backslash at the end of the line to | |
1629 | keep the macro together, and it leaves the point at the right | |
1630 | indentation column for the code. Thus you can write code inside macros | |
1631 | almost exactly as you can elsewhere, without having to bother with the | |
1632 | trailing backslashes. | |
1633 | ||
1634 | ||
1635 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1636 | @node Font Locking, Commands, Macro Handling, Top | |
1637 | @comment node-name, next, previous, up | |
1638 | @chapter Font Locking | |
1639 | @cindex font locking | |
1640 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1641 | ||
1642 | @strong{Note:} The font locking in AWK mode is currently not integrated | |
1643 | with the rest of @ccmode{}, so this section does not apply there. | |
1644 | @xref{AWK Mode Font Locking}, instead. | |
1645 | ||
1646 | @cindex Font Lock mode | |
1647 | ||
1648 | @ccmode{} provides font locking for its supported languages by supplying | |
1649 | patterns for use with Font Lock mode. This means that you get distinct | |
1650 | faces on the various syntactic parts such as comments, strings, keywords | |
1651 | and types, which is very helpful in telling them apart at a glance and | |
1652 | discovering syntactic errors. @xref{Font Lock,,, emacs, The Emacs | |
1653 | Editor}, for ways to enable font locking in @ccmode{} buffers. | |
1654 | ||
1655 | @menu | |
1656 | * Font Locking Preliminaries:: | |
1657 | * Faces:: | |
1658 | * Documentation Comments:: | |
1659 | @end menu | |
1660 | ||
1661 | ||
1662 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1663 | @node Font Locking Preliminaries, Faces, , Font Locking | |
1664 | @comment node-name, next, previous, up | |
1665 | @section Font Locking Preliminaries | |
1666 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1667 | ||
1668 | The font locking for most of the @ccmode{} languages were provided | |
1669 | directly by the Font Lock package prior to version 5.30 of @ccmode{}. | |
1670 | In the transition to @ccmode{} the patterns have been reworked | |
1671 | completely and are applied uniformly across all the languages except AWK | |
1672 | mode, just like the indentation rules (although each language still has | |
1673 | some pecularities of its own, of course). Since the languages | |
1674 | previously had completely separate font locking patterns, this means | |
1675 | that it's a bit different in most languages now. | |
1676 | ||
1677 | The main goal for the font locking in @ccmode{} is accuracy, to provide | |
1678 | a dependable aid in recognizing the various constructs. Some, like | |
1679 | strings and comments, are easy to recognize while others like | |
1680 | declarations and types can be very tricky. @ccmode{} can go to great | |
1681 | lengths to recognize declarations and casts correctly, especially when | |
1682 | the types aren't recognized by standard patterns. This is a fairly | |
1683 | demanding analysis which can be slow on older hardware, and it can | |
1684 | therefore be disabled by choosing a lower decoration level with the | |
1685 | variable @code{font-lock-maximum-decoration}. | |
1686 | ||
1687 | @vindex font-lock-maximum-decoration | |
1688 | ||
1689 | The decoration levels are used as follows: | |
1690 | ||
1691 | @enumerate | |
1692 | @comment 1 | |
1693 | @item | |
1694 | Minimal font locking: Fontify only comments, strings and preprocessor | |
1695 | directives (in the languages that use cpp). | |
1696 | ||
1697 | @comment 2 | |
1698 | @item | |
1699 | Fast normal font locking: In addition to level 1, fontify keywords, | |
1700 | simple types and declarations that are easy to recognize. The variables | |
1701 | @code{*-font-lock-extra-types} (where @samp{*} is the name of the | |
1702 | language) are used to recognize types (see below). Documentation | |
1703 | comments like Javadoc are fontified according to | |
1704 | @code{c-doc-comment-style} (@pxref{Documentation Comments}). | |
1705 | ||
1706 | Use this if you think the font locking is too slow. It's the closest | |
1707 | corresponding level to level 3 in the old font lock patterns. | |
1708 | ||
1709 | @comment 3 | |
1710 | @item | |
1711 | Accurate normal font locking: Like level 2 but uses a different approach | |
1712 | that can recognize types and declarations much more accurately. The | |
1713 | @code{*-font-lock-extra-types} variables are still used, but user | |
1714 | defined types are recognized correctly anyway in most cases. Therefore | |
1715 | those variables should be fairly restrictive and not contain patterns | |
1716 | that are uncertain. | |
1717 | ||
1718 | @cindex Lazy Lock mode | |
1719 | @cindex Just-in-time Lock mode | |
1720 | ||
1721 | This level is designed for fairly modern hardware and a font lock | |
1722 | support mode like Lazy Lock or Just-in-time Lock mode that only | |
1723 | fontifies the parts that are actually shown. | |
1724 | @end enumerate | |
1725 | ||
1726 | @cindex user defined types | |
1727 | @cindex types, user defined | |
1728 | ||
1729 | Since user defined types are hard to recognize you can provide | |
1730 | additional regexps to match those you use: | |
1731 | ||
1732 | @defopt c-font-lock-extra-types | |
1733 | @defoptx c++-font-lock-extra-types | |
1734 | @defoptx objc-font-lock-extra-types | |
1735 | @defoptx java-font-lock-extra-types | |
1736 | @defoptx idl-font-lock-extra-types | |
1737 | @defoptx pike-font-lock-extra-types | |
1738 | For each language there's a variable @code{*-font-lock-extra-types}, | |
1739 | where @samp{*} stands for the language in question. It contains a list | |
1740 | of regexps that matches identifiers that should be recognized as types, | |
1741 | e.g. @samp{\\sw+_t} to recognize all identifiers ending with @samp{_t} | |
1742 | as is customary in C code. Each regexp should not match more than a | |
1743 | single identifier. | |
1744 | ||
1745 | The default values contain regexps for many types in standard runtime | |
1746 | libraries that are otherwise difficult to recognize, and patterns for | |
1747 | standard type naming conventions like the @samp{_t} suffix in C and C++. | |
1748 | Java, Objective-C and Pike have as a convention to start class names | |
1749 | with capitals, so there are patterns for that in those languages. | |
1750 | ||
1751 | Despite the names of these variables, they are not only used for | |
1752 | fontification but in other places as well where @ccmode{} needs to | |
1753 | recognize types. | |
1754 | @end defopt | |
1755 | ||
1756 | ||
1757 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1758 | @node Faces, Documentation Comments, Font Locking Preliminaries, Font Locking | |
1759 | @comment node-name, next, previous, up | |
1760 | @section Faces | |
1761 | @cindex faces | |
1762 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1763 | ||
1764 | @ccmode{} attempts to use the standard faces for programming languages | |
1765 | in accordance with their intended purposes as far as possible. No extra | |
1766 | faces are currently provided, with the exception of a replacement face | |
1767 | @code{c-invalid-face} for emacsen that don't provide | |
1768 | @code{font-lock-warning-face}. | |
1769 | ||
1770 | @itemize @bullet | |
1771 | @item | |
1772 | @vindex font-lock-comment-face | |
1773 | Normal comments are fontified in @code{font-lock-comment-face}. | |
1774 | ||
1775 | @item | |
1776 | @vindex font-lock-doc-face | |
1777 | @vindex font-lock-doc-string-face | |
1778 | @vindex font-lock-comment-face | |
1779 | Comments that are recognized as documentation (@pxref{Documentation | |
1780 | Comments}) get @code{font-lock-doc-face} (Emacs) or | |
1781 | @code{font-lock-doc-string-face} (XEmacs) if those faces exist. If they | |
1782 | don't then @code{font-lock-comment-face} is used. | |
1783 | ||
1784 | @item | |
1785 | @vindex font-lock-string-face | |
1786 | String and character literals are fontified in | |
1787 | @code{font-lock-string-face}. | |
1788 | ||
1789 | @item | |
1790 | @vindex font-lock-keyword-face | |
1791 | Keywords are fontified with @code{font-lock-keyword-face}. | |
1792 | ||
1793 | @item | |
1794 | @vindex font-lock-function-name-face | |
1795 | @code{font-lock-function-name-face} is used for function names in | |
1796 | declarations and definitions, and classes in those contexts. It's also | |
1797 | used for preprocessor defines with arguments. | |
1798 | ||
1799 | @item | |
1800 | @vindex font-lock-variable-name-face | |
1801 | Variables in declarations and definitions, and other identifiers in such | |
1802 | variable contexts, get @code{font-lock-variable-name-face}. It's also | |
1803 | used for preprocessor defines without arguments. | |
1804 | ||
1805 | @item | |
1806 | @vindex font-lock-constant-face | |
1807 | @vindex font-lock-reference-face | |
1808 | Builtin constants are fontified in @code{font-lock-constant-face} if it | |
1809 | exists, @code{font-lock-reference-face} otherwise. As opposed to the | |
1810 | preceding two faces, this is used on the names in expressions, and it's | |
1811 | not used in declarations, even if there happen to be a @samp{const} in | |
1812 | them somewhere. | |
1813 | ||
1814 | @item | |
1815 | @vindex font-lock-type-face | |
1816 | @code{font-lock-type-face} is put on types (both predefined and user | |
1817 | defined) and classes in type contexts. | |
1818 | ||
1819 | @item | |
1820 | @vindex font-lock-constant-face | |
1821 | @vindex font-lock-reference-face | |
1822 | Label identifiers get @code{font-lock-constant-face} if it exists, | |
1823 | @code{font-lock-reference-face} otherwise. | |
1824 | ||
1825 | @item | |
1826 | Name qualifiers and identifiers for scope constructs are fontified like | |
1827 | labels. | |
1828 | ||
1829 | @item | |
1830 | Special markup inside documentation comments are also fontified like | |
1831 | labels. | |
1832 | ||
1833 | @item | |
1834 | @vindex font-lock-preprocessor-face | |
1835 | @vindex font-lock-builtin-face | |
1836 | @vindex font-lock-reference-face | |
1837 | Preprocessor directives get @code{font-lock-preprocessor-face} if it | |
1838 | exists (i.e. XEmacs). In Emacs they get @code{font-lock-builtin-face} | |
1839 | or @code{font-lock-reference-face}, for lack of a closer equivalent. | |
1840 | ||
1841 | @item | |
1842 | @vindex font-lock-warning-face | |
1843 | @vindex c-invalid-face | |
1844 | @vindex invalid-face (c-) | |
1845 | Some kinds of syntactic errors are fontified with | |
1846 | @code{font-lock-warning-face} in Emacs. In older XEmacs versions | |
1847 | there's no corresponding standard face, so there a special | |
1848 | @code{c-invalid-face} is used, which is defined to stand out sharply by | |
1849 | default. | |
1850 | ||
1851 | Note that it's not used for @samp{#error} or @samp{#warning} directives, | |
1852 | since those aren't syntactic errors in themselves. | |
1853 | @end itemize | |
1854 | ||
1855 | ||
1856 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1857 | @node Documentation Comments, , Faces, Font Locking | |
1858 | @comment node-name, next, previous, up | |
1859 | @section Documentation Comments | |
1860 | @cindex documentation comments | |
1861 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1862 | ||
1863 | There are various tools to supply documentation in the source as | |
1864 | specially structured comments, e.g. the standard Javadoc tool in Java. | |
1865 | @ccmode{} provides an extensible mechanism to fontify such comments and | |
1866 | the special markup inside them. | |
1867 | ||
1868 | @defopt c-doc-comment-style | |
1869 | @vindex doc-comment-style (c-) | |
1870 | This is a style variable that specifies which documentation comment | |
1871 | style to recognize, e.g. @code{javadoc} for Javadoc comments. | |
1872 | ||
1873 | The value may also be a list of styles, in which case all of them are | |
1874 | recognized simultaneously (presumably with markup cues that don't | |
1875 | conflict). | |
1876 | ||
1877 | The value may also be an association list to specify different comment | |
1878 | styles for different languages. The symbol for the major mode is then | |
1879 | looked up in the alist, and the value of that element is interpreted as | |
1880 | above if found. If it isn't found then the symbol `other' is looked up | |
1881 | and its value is used instead. | |
1882 | ||
1883 | Note that @ccmode{} uses this variable to set other variables that | |
1884 | handle fontification etc. That's done at mode initialization or when | |
1885 | you switch to a style which sets this variable. Thus, if you change it | |
1886 | in some other way, e.g. interactively in a CC Mode buffer, you will need | |
1887 | to do @kbd{M-x java-mode} (or whatever mode you're currently using) to | |
1888 | reinitialize. | |
1889 | ||
1890 | @findex c-setup-doc-comment-style | |
1891 | @findex setup-doc-comment-style (c-) | |
1892 | Note also that when @ccmode{} starts up, the other variables are | |
1893 | modified before the mode hooks are run. If you change this variable in | |
1894 | a mode hook, you have to call @code{c-setup-doc-comment-style} | |
1895 | afterwards to redo that work. | |
1896 | @end defopt | |
1897 | ||
1898 | @ccmode{} currently provides handing of the following doc comment | |
1899 | styles: | |
1900 | ||
1901 | @table @code | |
1902 | @item javadoc | |
1903 | @cindex Javadoc markup | |
1904 | Javadoc comments, the standard tool in Java. | |
1905 | ||
1906 | @item autodoc | |
1907 | @cindex Pike autodoc markup | |
1908 | For Pike autodoc markup, the standard in Pike. | |
1909 | @end table | |
1910 | ||
1911 | The above is by no means complete. If you'd like to see support for | |
1912 | other doc comment styles, please let us know (@pxref{Mailing Lists and | |
1913 | Submitting Bug Reports}). | |
1914 | ||
1915 | You can also write your own doc comment fontification support to use | |
1916 | with @code{c-doc-comment-style}: Supply a variable or function | |
1917 | @code{*-font-lock-keywords} where @samp{*} is the name you want to use | |
1918 | in @code{c-doc-comment-style}. If it's a variable, it's prepended to | |
1919 | @code{font-lock-keywords}. If it's a function, it's called at mode | |
1920 | initialization and the result is prepended. For an example, see | |
1921 | @code{javadoc-font-lock-keywords} in @file{cc-fonts.el}. | |
1922 | ||
1923 | If you add support for another doc comment style, please consider | |
1924 | contributing it --- send a note to @email{bug-cc-mode@@gnu.org}. | |
1925 | ||
1926 | ||
1927 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1928 | @node Commands, Customizing Indentation, Font Locking, Top | |
1929 | @comment node-name, next, previous, up | |
1930 | @chapter Commands | |
1931 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1932 | ||
1933 | @menu | |
1934 | * Indentation Commands:: | |
1935 | * Movement Commands:: | |
1936 | * Other Commands:: | |
1937 | @end menu | |
1938 | ||
1939 | See also @ref{Text Filling and Line Breaking} and @ref{Macro Handling}, | |
1940 | for commands concerning those bits. | |
1941 | ||
1942 | ||
1943 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
d7bd46ed GM |
1944 | @node Indentation Commands, Movement Commands, , Commands |
1945 | @comment node-name, next, previous,up | |
6b61353c | 1946 | @section Indentation Commands |
d7bd46ed | 1947 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
6bf7aab6 | 1948 | |
6b61353c KH |
1949 | The following list of commands reindent C constructs. Note that when |
1950 | you change your coding style, either interactively or through some other | |
1951 | means, your file does @emph{not} automatically get reindented. You | |
1952 | will need to execute one of the following commands to see the effects of | |
d7bd46ed GM |
1953 | your changes. |
1954 | ||
1955 | @cindex GNU indent program | |
1956 | Also, variables like @code{c-hanging-*} and @code{c-cleanup-list} | |
1957 | only affect how on-the-fly code is formatted. Changing the | |
6b61353c | 1958 | ``hanginess'' of a brace and then reindenting, will not move the brace |
d7bd46ed | 1959 | to a different line. For this, you're better off getting an external |
6b61353c | 1960 | program like GNU @code{indent}, which will rearrange brace location, |
d7bd46ed GM |
1961 | among other things. |
1962 | ||
6b61353c | 1963 | Reindenting large sections of code can take a long time. When |
d7bd46ed | 1964 | @ccmode{} reindents a region of code, it is essentially equivalent to |
6b61353c | 1965 | hitting @kbd{TAB} on every line of the region. |
d7bd46ed GM |
1966 | |
1967 | These commands are useful when indenting code: | |
6bf7aab6 | 1968 | |
d7bd46ed | 1969 | @table @asis |
6b61353c | 1970 | @item @kbd{TAB} (@code{c-indent-command}) |
d7bd46ed | 1971 | @kindex TAB |
6bf7aab6 DL |
1972 | @findex c-indent-command |
1973 | @findex indent-command (c-) | |
d7bd46ed GM |
1974 | Indents the current line. The actual behavior is controlled by several |
1975 | variables, described below. See @code{c-tab-always-indent}, | |
1976 | @code{c-insert-tab-function}, and @code{indent-tabs-mode}. With a | |
1977 | numeric argument, this command rigidly indents the region, preserving | |
1978 | the relative indentation among the lines. | |
6bf7aab6 | 1979 | |
6b61353c | 1980 | @item @kbd{C-M-q} (@code{c-indent-exp}) |
718fb8a1 | 1981 | @kindex C-M-q |
6bf7aab6 DL |
1982 | @findex c-indent-exp |
1983 | @findex indent-exp (c-) | |
d7bd46ed GM |
1984 | Indent an entire balanced brace or parenthesis expression. Note that |
1985 | point must be on the opening brace or parenthesis of the expression you | |
1986 | want to indent. | |
6bf7aab6 | 1987 | |
6b61353c | 1988 | @item @kbd{C-c C-q} (@code{c-indent-defun}) |
6bf7aab6 DL |
1989 | @kindex C-c C-q |
1990 | @findex c-indent-defun | |
1991 | @findex indent-defun (c-) | |
6b61353c KH |
1992 | Indents the entire top-level function, class or macro definition |
1993 | encompassing point. It leaves point unchanged. This function can't be | |
1994 | used to reindent a nested brace construct, such as a nested class or | |
1995 | function, or a Java method. The top-level construct being reindented | |
1996 | must be complete, i.e. it must have both a beginning brace and an ending | |
1997 | brace. | |
6bf7aab6 | 1998 | |
6b61353c | 1999 | @item @kbd{C-M-\} (@code{indent-region}) |
718fb8a1 | 2000 | @kindex C-M-\ |
6bf7aab6 | 2001 | @findex indent-region |
d7bd46ed | 2002 | Indents an arbitrary region of code. This is a standard Emacs command, |
6b61353c | 2003 | tailored for C code in a @ccmode{} buffer. Note, of course, that point |
d7bd46ed | 2004 | and mark must delineate the region you want to indent. |
6bf7aab6 | 2005 | |
6b61353c KH |
2006 | @item @kbd{M-;} (@code{indent-for-comment}) |
2007 | @kindex M-; | |
2008 | @findex indent-for-comment | |
2009 | Insert a comment at the end of the current line, if none is there already. | |
2010 | Then reindent the comment according to the variables | |
2011 | @code{c-indent-comment-alist}, @code{c-indent-comments-syntactically-p} | |
2012 | and @code{comment-column}. Then position the point after the comment | |
2013 | starter. This is a standard Emacs command, but @ccmode{} enhances it a | |
2014 | bit with two variables: | |
2015 | ||
2016 | @defopt c-indent-comment-alist | |
2017 | @vindex indent-comment-alist (c-) | |
2018 | @vindex comment-column | |
2019 | This style variable allows you to control which column @kbd{M-;} | |
2020 | indents the comment to, depending on the preceding code and the | |
2021 | indentation of a similar comment on the preceding line, if there is | |
2022 | any. It is an association list that maps different types of lines to | |
2023 | actions describing how they should be handled. If a certain line type | |
2024 | isn't present on the list then the line is indented to the column | |
2025 | specified by @code{comment-column}. See the documentation string for | |
2026 | @code{c-indent-comment-alist} for a full description of the available | |
2027 | line types and actions (use @kbd{C-h v c-indent-comment-alist}). | |
2028 | @end defopt | |
2029 | ||
2030 | @defopt c-indent-comments-syntactically-p | |
2031 | @vindex indent-comments-syntactically-p (c-) | |
2032 | Normally, when this variable is @code{nil}, @kbd{M-;} will indent | |
2033 | comment-only lines according to @code{c-indent-comment-alist}, just as | |
2034 | it does with lines where other code precede the comments. However, if | |
2035 | you want it to act just like @kbd{TAB} for comment-only lines you can | |
2036 | get that by setting @code{c-indent-comments-syntactically-p} to | |
2037 | non-@code{nil}. | |
2038 | ||
2039 | If @code{c-indent-comments-syntactically-p} is non-@code{nil} then | |
2040 | @code{c-indent-comment-alist} won't be consulted at all for comment-only | |
2041 | lines. | |
2042 | @end defopt | |
2043 | ||
2044 | @item @kbd{C-M-h} (@code{c-mark-function}) | |
718fb8a1 | 2045 | @kindex C-M-h |
6bf7aab6 DL |
2046 | @findex c-mark-function |
2047 | @findex mark-function (c-) | |
d7bd46ed GM |
2048 | While not strictly an indentation command, this is useful for marking |
2049 | the current top-level function or class definition as the current | |
2050 | region. As with @code{c-indent-defun}, this command operates on | |
2051 | top-level constructs, and can't be used to mark say, a Java method. | |
d7bd46ed GM |
2052 | @end table |
2053 | ||
2054 | These variables are also useful when indenting code: | |
2055 | ||
6b61353c | 2056 | @defopt c-tab-always-indent |
d7bd46ed GM |
2057 | @vindex tab-always-indent (c-) |
2058 | @kindex TAB | |
2059 | @cindex literal | |
6b61353c KH |
2060 | This variable controls how @kbd{TAB} (@code{c-indent-command}) operates. |
2061 | When it is @code{t}, @kbd{TAB} always indents the current line. When it | |
2062 | is @code{nil}, the line is indented only if point is at the left margin, | |
2063 | or on or before the first non-whitespace character on the line, | |
2064 | otherwise some whitespace is inserted. If this variable is the symbol | |
2065 | @code{other}, then some whitespace is inserted only within strings and | |
2066 | comments (literals), and inside preprocessor directives, but the line is | |
2067 | always reindented. | |
2068 | @end defopt | |
2069 | ||
2070 | @defopt c-insert-tab-function | |
d7bd46ed GM |
2071 | @vindex insert-tab-function (c-) |
2072 | @findex tab-to-tab-stop | |
d7bd46ed GM |
2073 | When ``some whitespace'' is inserted as described above, what actually |
2074 | happens is that the function stored in @code{c-insert-tab-function} is | |
2075 | called. Normally, this just inserts a real tab character, or the | |
2076 | equivalent number of spaces, depending on @code{indent-tabs-mode}. | |
2077 | Some people, however, set @code{c-insert-tab-function} to | |
2078 | @code{tab-to-tab-stop} so as to get hard tab stops when indenting. | |
6b61353c | 2079 | @end defopt |
d7bd46ed | 2080 | |
6b61353c KH |
2081 | @defopt indent-tabs-mode |
2082 | This is a standard Emacs variable that controls how line indentation | |
2083 | is composed. When it's non-@code{nil}, tabs can be used in a line's | |
2084 | indentation, otherwise only spaces can be used. | |
2085 | @end defopt | |
d7bd46ed | 2086 | |
6b61353c | 2087 | @defopt c-progress-interval |
d7bd46ed | 2088 | @vindex progress-interval (c-) |
177c0ea7 | 2089 | When indenting large regions of code, this variable controls how often a |
d7bd46ed | 2090 | progress message is displayed. Set this variable to @code{nil} to |
6b61353c KH |
2091 | inhibit the progress messages, or set it to an integer which is how |
2092 | often (in seconds) progress messages are to be displayed. | |
2093 | @end defopt | |
d7bd46ed GM |
2094 | |
2095 | ||
2096 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
2097 | @node Movement Commands, Other Commands, Indentation Commands, Commands | |
2098 | @comment node-name, next, previous, up | |
6b61353c KH |
2099 | @section Movement Commands |
2100 | @cindex movement | |
6bf7aab6 DL |
2101 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
2102 | ||
6b61353c | 2103 | @ccmode{} contains some useful commands for moving around in C |
6bf7aab6 DL |
2104 | code. |
2105 | ||
d7bd46ed | 2106 | @table @asis |
6b61353c | 2107 | @item @kbd{M-x c-beginning-of-defun} |
6bf7aab6 DL |
2108 | @findex c-beginning-of-defun |
2109 | @findex beginning-of-defun (c-) | |
2110 | @findex beginning-of-defun | |
6b61353c | 2111 | Move point back to the least-enclosing brace. This function is |
6bf7aab6 DL |
2112 | analogous to the Emacs built-in command @code{beginning-of-defun}, |
2113 | except it eliminates the constraint that the top-level opening brace | |
2114 | must be in column zero. See @code{beginning-of-defun} for more | |
2115 | information. | |
2116 | ||
2117 | Depending on the coding style being used, you might prefer | |
2118 | @code{c-beginning-of-defun} to @code{beginning-of-defun}. If so, | |
2119 | consider binding @kbd{C-M-a} to the former instead. For backwards | |
2120 | compatibility reasons, the default binding remains in effect. | |
2121 | ||
6b61353c KH |
2122 | In AWK mode, a defun doesn't necessarily have braces at all. AWK Mode |
2123 | therefore has its own version of this function which is bound by | |
2124 | default to @kbd{C-M-a}. You can thus chose freely which function to | |
2125 | bind to @kbd{C-M-a} for the other modes without worrying about AWK | |
2126 | buffers. @xref{AWK Mode Defuns}. | |
2127 | ||
2128 | @item @kbd{M-x c-end-of-defun} | |
6bf7aab6 DL |
2129 | @findex c-end-of-defun |
2130 | @findex end-of-defun (c-) | |
2131 | @findex end-of-defun | |
6bf7aab6 DL |
2132 | Moves point to the end of the current top-level definition. This |
2133 | function is analogous to the Emacs built-in command @code{end-of-defun}, | |
2134 | except it eliminates the constraint that the top-level opening brace of | |
6b61353c | 2135 | the defun must be in column zero. See @code{end-of-defun} for more |
6bf7aab6 DL |
2136 | information. |
2137 | ||
2138 | Depending on the coding style being used, you might prefer | |
2139 | @code{c-end-of-defun} to @code{end-of-defun}. If so, | |
2140 | consider binding @kbd{C-M-e} to the former instead. For backwards | |
2141 | compatibility reasons, the default binding remains in effect. | |
2142 | ||
6b61353c KH |
2143 | In AWK Mode, a defun doesn't necessarily have braces at all. AWK Mode |
2144 | therefore has its own version of this function which is bound by | |
2145 | default to @kbd{C-M-e}. You can thus chose freely which function to | |
2146 | bind to @kbd{C-M-e} for the other modes without worrying about AWK | |
2147 | buffers. @ref{AWK Mode Defuns}. | |
2148 | ||
2149 | @item @kbd{C-c C-u} (@code{c-up-conditional}) | |
6bf7aab6 DL |
2150 | @kindex C-c C-u |
2151 | @findex c-up-conditional | |
2152 | @findex up-conditional (c-) | |
6bf7aab6 DL |
2153 | Move point back to the containing preprocessor conditional, leaving the |
2154 | mark behind. A prefix argument acts as a repeat count. With a negative | |
2155 | argument, move point forward to the end of the containing | |
d7bd46ed GM |
2156 | preprocessor conditional. |
2157 | ||
2158 | @samp{#elif} is treated like @samp{#else} followed by @samp{#if}, so the | |
2159 | function stops at them when going backward, but not when going forward. | |
2160 | ||
6b61353c | 2161 | @item @kbd{M-x c-up-conditional-with-else} |
d7bd46ed GM |
2162 | @findex c-up-conditional-with-else |
2163 | @findex up-conditional-with-else (c-) | |
d7bd46ed GM |
2164 | A variety of @code{c-up-conditional} that also stops at @samp{#else} |
2165 | lines. Normally those lines are ignored. | |
2166 | ||
6b61353c | 2167 | @item @kbd{M-x c-down-conditional} |
d7bd46ed GM |
2168 | @findex c-down-conditional |
2169 | @findex down-conditional (c-) | |
d7bd46ed GM |
2170 | Move point forward into the next nested preprocessor conditional, |
2171 | leaving the mark behind. A prefix argument acts as a repeat count. | |
2172 | With a negative argument, move point backward into the previous | |
2173 | nested preprocessor conditional. | |
2174 | ||
2175 | @samp{#elif} is treated like @samp{#else} followed by @samp{#if}, so the | |
2176 | function stops at them when going forward, but not when going backward. | |
2177 | ||
6b61353c | 2178 | @item @kbd{M-x c-down-conditional-with-else} |
d7bd46ed GM |
2179 | @findex c-down-conditional-with-else |
2180 | @findex down-conditional-with-else (c-) | |
d7bd46ed GM |
2181 | A variety of @code{c-down-conditional} that also stops at @samp{#else} |
2182 | lines. Normally those lines are ignored. | |
6bf7aab6 | 2183 | |
6b61353c | 2184 | @item @kbd{C-c C-p} (@code{c-backward-conditional}) |
6bf7aab6 DL |
2185 | @kindex C-c C-p |
2186 | @findex c-backward-conditional | |
2187 | @findex backward-conditional (c-) | |
6bf7aab6 DL |
2188 | Move point back over a preprocessor conditional, leaving the mark |
2189 | behind. A prefix argument acts as a repeat count. With a negative | |
2190 | argument, move forward. | |
2191 | ||
6b61353c | 2192 | @item @kbd{C-c C-n} (@code{c-forward-conditional}) |
6bf7aab6 DL |
2193 | @kindex C-c C-n |
2194 | @findex c-forward-conditional | |
2195 | @findex forward-conditional (c-) | |
6bf7aab6 DL |
2196 | Move point forward across a preprocessor conditional, leaving the mark |
2197 | behind. A prefix argument acts as a repeat count. With a negative | |
2198 | argument, move backward. | |
2199 | ||
6b61353c | 2200 | @item @kbd{M-a} (@code{c-beginning-of-statement}) |
d7bd46ed | 2201 | @kindex M-a |
6bf7aab6 DL |
2202 | @findex c-beginning-of-statement |
2203 | @findex beginning-of-statement (c-) | |
6bf7aab6 | 2204 | Move point to the beginning of the innermost C statement. If point is |
cb7f2e96 GM |
2205 | already at the beginning of a statement, move to the beginning of the |
2206 | closest preceding statement, even if that means moving into a block (you | |
718fb8a1 | 2207 | can use @kbd{C-M-b} to move over a balanced block). With prefix |
6bf7aab6 DL |
2208 | argument @var{n}, move back @var{n} @minus{} 1 statements. |
2209 | ||
cb7f2e96 GM |
2210 | If point is within or next to a comment or a string which spans more |
2211 | than one line, this command moves by sentences instead of statements. | |
6bf7aab6 DL |
2212 | |
2213 | When called from a program, this function takes three optional | |
cb7f2e96 GM |
2214 | arguments: the repetition count, a buffer position limit which is the |
2215 | farthest back to search for the syntactic context, and a flag saying | |
2216 | whether to do sentence motion in or near comments and multiline strings. | |
6bf7aab6 | 2217 | |
6b61353c | 2218 | @item @kbd{M-e} (@code{c-end-of-statement}) |
d7bd46ed | 2219 | @kindex M-e |
6bf7aab6 DL |
2220 | @findex c-end-of-statement |
2221 | @findex end-of-statement (c-) | |
6bf7aab6 DL |
2222 | Move point to the end of the innermost C statement. If point is at the |
2223 | end of a statement, move to the end of the next statement, even if it's | |
718fb8a1 | 2224 | inside a nested block (use @kbd{C-M-f} to move to the other side of the |
6bf7aab6 DL |
2225 | block). With prefix argument @var{n}, move forward @var{n} @minus{} 1 |
2226 | statements. | |
2227 | ||
cb7f2e96 GM |
2228 | If point is within or next to a comment or a string which spans more |
2229 | than one line, this command moves by sentences instead of statements. | |
6bf7aab6 DL |
2230 | |
2231 | When called from a program, this function takes three optional | |
cb7f2e96 GM |
2232 | arguments: the repetition count, a buffer position limit which is the |
2233 | farthest back to search for the syntactic context, and a flag saying | |
2234 | whether to do sentence motion in or near comments and multiline strings. | |
6bf7aab6 | 2235 | |
6b61353c | 2236 | @item @kbd{M-x c-forward-into-nomenclature} |
6bf7aab6 DL |
2237 | @findex c-forward-into-nomenclature |
2238 | @findex forward-into-nomenclature (c-) | |
6bf7aab6 DL |
2239 | A popular programming style, especially for object-oriented languages |
2240 | such as C++ is to write symbols in a mixed case format, where the first | |
2241 | letter of each word is capitalized, and not separated by underscores. | |
2242 | E.g. @samp{SymbolsWithMixedCaseAndNoUnderlines}. | |
2243 | ||
2244 | This command moves point forward to next capitalized word. With prefix | |
2245 | argument @var{n}, move @var{n} times. | |
2246 | ||
6b61353c | 2247 | @item @kbd{M-x c-backward-into-nomenclature} |
6bf7aab6 DL |
2248 | @findex c-backward-into-nomenclature |
2249 | @findex backward-into-nomenclature (c-) | |
6bf7aab6 DL |
2250 | Move point backward to beginning of the next capitalized |
2251 | word. With prefix argument @var{n}, move @var{n} times. If | |
2252 | @var{n} is negative, move forward. | |
d7bd46ed GM |
2253 | @end table |
2254 | ||
2255 | ||
2256 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
2257 | @node Other Commands, , Movement Commands, Commands | |
2258 | @comment node-name, next, previous, up | |
6b61353c | 2259 | @section Other Commands |
d7bd46ed GM |
2260 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
2261 | ||
6b61353c | 2262 | Here are the various other commands that didn't fit anywhere else: |
d7bd46ed GM |
2263 | |
2264 | @table @asis | |
6b61353c | 2265 | @item @kbd{C-c :} (@code{c-scope-operator}) |
6bf7aab6 DL |
2266 | @kindex C-c : |
2267 | @findex c-scope-operator | |
2268 | @findex scope-operator (c-) | |
6bf7aab6 DL |
2269 | In C++, it is also sometimes desirable to insert the double-colon scope |
2270 | operator without performing the electric behavior of colon insertion. | |
2271 | @kbd{C-c :} does just this. | |
6bf7aab6 DL |
2272 | @end table |
2273 | ||
d7bd46ed GM |
2274 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
2275 | @node Customizing Indentation, Syntactic Symbols, Commands, Top | |
2276 | @comment node-name, next, previous, up | |
6b61353c KH |
2277 | @chapter Customizing Indentation |
2278 | @cindex customization, indentation | |
2279 | @cindex indentation | |
6bf7aab6 DL |
2280 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
2281 | ||
6b61353c KH |
2282 | The context sensitive indentation is mainly controlled by the variable |
2283 | @code{c-offsets-alist}: | |
2284 | ||
2285 | @defopt c-offsets-alist | |
6bf7aab6 | 2286 | @vindex offsets-alist (c-) |
6b61353c KH |
2287 | This special style variable contains the mappings between syntactic |
2288 | symbols and the offsets to apply for those symbols. It's set at mode | |
2289 | initialization from a @emph{style} you may specify. Styles are | |
d7bd46ed | 2290 | groupings of syntactic symbol offsets and other style variable values. |
6b61353c | 2291 | Most likely, you'll find that one of the predefined styles will suit |
d7bd46ed GM |
2292 | your needs. @xref{Styles}, for an explanation of how to set up named |
2293 | styles. | |
2294 | ||
2295 | Only syntactic symbols not already bound on @code{c-offsets-alist} will | |
2296 | be set from styles. This means that any association you set on it, be | |
2297 | it before or after mode initialization, will not be changed. The | |
2298 | @code{c-offsets-alist} variable may therefore be used from e.g. the | |
2299 | Customization interface@footnote{Available in Emacs 20 and later, and | |
2300 | XEmacs 19.15 and later.} to easily change indentation offsets without | |
2301 | having to bother about styles. Initially @code{c-offsets-alist} is | |
2302 | empty, so that all syntactic symbols are set by the style system. | |
2303 | ||
6b61353c KH |
2304 | The offset associated with any particular syntactic symbol can be an |
2305 | integer, a function or lambda expression, a variable name, a vector, a | |
2306 | list, or one of the following special symbols: @code{+}, @code{-}, | |
2307 | @code{++}, @code{--}, @code{*}, or @code{/}. The meaning of these | |
2308 | values are described in detail below. | |
2309 | @end defopt | |
d7bd46ed | 2310 | |
6b61353c KH |
2311 | The special symbols describe an offset in multiples of the value of |
2312 | @code{c-basic-offset}: | |
2313 | ||
2314 | @defopt c-basic-offset | |
d7bd46ed | 2315 | @vindex basic-offset (c-) |
6b61353c KH |
2316 | Style variable that holds the basic offset between indentation levels. |
2317 | @end defopt | |
6bf7aab6 | 2318 | |
6b61353c KH |
2319 | By defining a style's indentation in terms of @code{c-basic-offset}, |
2320 | you can change the amount of whitespace given to an indentation level | |
2321 | while maintaining the same basic shape of your code. Here are the | |
2322 | values that the special symbols correspond to: | |
6bf7aab6 | 2323 | |
6b61353c | 2324 | @table @code |
6bf7aab6 DL |
2325 | @item + |
2326 | @code{c-basic-offset} times 1 | |
2327 | @item - | |
2328 | @code{c-basic-offset} times -1 | |
2329 | @item ++ | |
2330 | @code{c-basic-offset} times 2 | |
2331 | @item -- | |
2332 | @code{c-basic-offset} times -2 | |
2333 | @item * | |
2334 | @code{c-basic-offset} times 0.5 | |
2335 | @item / | |
2336 | @code{c-basic-offset} times -0.5 | |
6bf7aab6 DL |
2337 | @end table |
2338 | ||
d7bd46ed GM |
2339 | @cindex indentation functions |
2340 | ||
2341 | When a function is used as offset, it's called an @dfn{indentation | |
2342 | function}. Such functions are useful when more context than just the | |
2343 | syntactic symbol is needed to get the desired indentation. | |
2344 | @xref{Indentation Functions}, and @ref{Custom Indentation Functions}, | |
2345 | for details about them. | |
2346 | ||
cb7f2e96 | 2347 | If the offset is a vector, its first element sets the absolute |
6b61353c KH |
2348 | indentation column, which will override any previous relative |
2349 | indentation. It won't override additional relative indentation for | |
2350 | nested constructs, though. | |
cb7f2e96 | 2351 | |
d7bd46ed GM |
2352 | @vindex c-strict-syntax-p |
2353 | @vindex strict-syntax-p (c-) | |
2354 | The offset can also be a list, in which case it is evaluated recursively | |
2355 | using the semantics described above. The first element of the list that | |
2356 | returns a non-@code{nil} value succeeds and the evaluation stops. If | |
2357 | none of the list elements return a non-@code{nil} value, then an offset | |
2358 | of 0 (zero) is used@footnote{There is however a variable | |
2359 | @code{c-strict-syntax-p} that, when set to non-@code{nil}, will cause an | |
6b61353c | 2360 | error to be signalled in that case. It's now considered obsolete since |
d7bd46ed GM |
2361 | it doesn't work well with some of the alignment functions that now |
2362 | returns @code{nil} instead of zero to be more usable in lists. You | |
2363 | should therefore leave @code{c-strict-syntax-p} set to @code{nil}.}. | |
2364 | ||
6bf7aab6 DL |
2365 | So, for example, because most of the default offsets are defined in |
2366 | terms of @code{+}, @code{-}, and @code{0}, if you like the general | |
2367 | indentation style, but you use 4 spaces instead of 2 spaces per level, | |
2368 | you can probably achieve your style just by changing | |
d7bd46ed GM |
2369 | @code{c-basic-offset} like so@footnote{You can try this interactively in |
2370 | a C buffer by typing the text that appears in italics.}: | |
6bf7aab6 | 2371 | |
6b61353c | 2372 | @example |
d7bd46ed GM |
2373 | @emph{M-x set-variable RET} |
2374 | Set variable: @emph{c-basic-offset RET} | |
2375 | Set c-basic-offset to value: @emph{4 RET} | |
6bf7aab6 DL |
2376 | @end example |
2377 | ||
2378 | @noindent | |
2379 | This would change | |
6b61353c | 2380 | |
6bf7aab6 DL |
2381 | @example |
2382 | @group | |
6bf7aab6 DL |
2383 | int add( int val, int incr, int doit ) |
2384 | @{ | |
2385 | if( doit ) | |
2386 | @{ | |
2387 | return( val + incr ); | |
2388 | @} | |
2389 | return( val ); | |
2390 | @} | |
6bf7aab6 DL |
2391 | @end group |
2392 | @end example | |
6b61353c | 2393 | |
6bf7aab6 DL |
2394 | @noindent |
2395 | to | |
6b61353c | 2396 | |
6bf7aab6 DL |
2397 | @example |
2398 | @group | |
6bf7aab6 DL |
2399 | int add( int val, int incr, int doit ) |
2400 | @{ | |
2401 | if( doit ) | |
2402 | @{ | |
2403 | return( val + incr ); | |
2404 | @} | |
2405 | return( val ); | |
2406 | @} | |
6bf7aab6 DL |
2407 | @end group |
2408 | @end example | |
2409 | ||
6bf7aab6 | 2410 | To change indentation styles more radically, you will want to change the |
d7bd46ed GM |
2411 | offsets associated with other syntactic symbols. First, I'll show you |
2412 | how to do that interactively, then I'll describe how to make changes to | |
2413 | your @file{.emacs} file so that your changes are more permanent. | |
6bf7aab6 DL |
2414 | |
2415 | @menu | |
2416 | * Interactive Customization:: | |
2417 | * Permanent Customization:: | |
d7bd46ed | 2418 | * Hooks:: |
6bf7aab6 DL |
2419 | * Styles:: |
2420 | * Advanced Customizations:: | |
2421 | @end menu | |
2422 | ||
6bf7aab6 | 2423 | |
d7bd46ed GM |
2424 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
2425 | @node Interactive Customization, Permanent Customization, , Customizing Indentation | |
2426 | @comment node-name, next, previous, up | |
6b61353c KH |
2427 | @section Interactive Customization |
2428 | @cindex customization, interactive | |
d7bd46ed | 2429 | @cindex interactive customization |
6bf7aab6 DL |
2430 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
2431 | ||
2432 | As an example of how to customize indentation, let's change the | |
6b61353c | 2433 | style of this example@footnote{In this and subsequent examples, the |
6bf7aab6 | 2434 | original code is formatted using the @samp{gnu} style unless otherwise |
d7bd46ed | 2435 | indicated. @xref{Styles}.}: |
6b61353c | 2436 | |
6bf7aab6 DL |
2437 | @example |
2438 | @group | |
6b61353c KH |
2439 | 1: int add( int val, int incr, int doit ) |
2440 | 2: @{ | |
2441 | 3: if( doit ) | |
2442 | 4: @{ | |
2443 | 5: return( val + incr ); | |
2444 | 6: @} | |
2445 | 7: return( val ); | |
2446 | 8: @} | |
6bf7aab6 DL |
2447 | @end group |
2448 | @end example | |
6b61353c | 2449 | |
6bf7aab6 DL |
2450 | @noindent |
2451 | to: | |
6b61353c | 2452 | |
6bf7aab6 DL |
2453 | @example |
2454 | @group | |
6b61353c KH |
2455 | 1: int add( int val, int incr, int doit ) |
2456 | 2: @{ | |
2457 | 3: if( doit ) | |
2458 | 4: @{ | |
2459 | 5: return( val + incr ); | |
2460 | 6: @} | |
2461 | 7: return( val ); | |
2462 | 8: @} | |
6bf7aab6 DL |
2463 | @end group |
2464 | @end example | |
2465 | ||
2466 | In other words, we want to change the indentation of braces that open a | |
2467 | block following a condition so that the braces line up under the | |
2468 | conditional, instead of being indented. Notice that the construct we | |
2469 | want to change starts on line 4. To change the indentation of a line, | |
2470 | we need to see which syntactic components affect the offset calculations | |
2471 | for that line. Hitting @kbd{C-c C-s} on line 4 yields: | |
6bf7aab6 | 2472 | |
6b61353c KH |
2473 | @example |
2474 | ((substatement-open 44)) | |
6bf7aab6 DL |
2475 | @end example |
2476 | ||
6bf7aab6 DL |
2477 | @noindent |
2478 | so we know that to change the offset of the open brace, we need to | |
2479 | change the indentation for the @code{substatement-open} syntactic | |
6b61353c KH |
2480 | symbol. |
2481 | ||
2482 | To do this interactively, just hit @kbd{C-c C-o}. This prompts | |
d7bd46ed GM |
2483 | you for the syntactic symbol to change, providing a reasonable default. |
2484 | In this case, the default is @code{substatement-open}, which is just the | |
2485 | syntactic symbol we want to change! | |
6bf7aab6 DL |
2486 | |
2487 | After you hit return, @ccmode{} will then prompt you for the new | |
2488 | offset value, with the old value as the default. The default in this | |
2489 | case is @samp{+}, but we want no extra indentation so enter | |
2490 | @samp{0} and @kbd{RET}. This will associate the offset 0 with the | |
d7bd46ed | 2491 | syntactic symbol @code{substatement-open}. |
6bf7aab6 | 2492 | |
6bf7aab6 DL |
2493 | To check your changes quickly, just hit @kbd{C-c C-q} |
2494 | (@code{c-indent-defun}) to reindent the entire function. The example | |
2495 | should now look like: | |
6b61353c | 2496 | |
6bf7aab6 DL |
2497 | @example |
2498 | @group | |
6b61353c KH |
2499 | 1: int add( int val, int incr, int doit ) |
2500 | 2: @{ | |
2501 | 3: if( doit ) | |
2502 | 4: @{ | |
2503 | 5: return( val + incr ); | |
2504 | 6: @} | |
2505 | 7: return( val ); | |
2506 | 8: @} | |
6bf7aab6 DL |
2507 | @end group |
2508 | @end example | |
2509 | ||
2510 | Notice how just changing the open brace offset on line 4 is all we | |
2511 | needed to do. Since the other affected lines are indented relative to | |
2512 | line 4, they are automatically indented the way you'd expect. For more | |
2513 | complicated examples, this may not always work. The general approach to | |
2514 | take is to always start adjusting offsets for lines higher up in the | |
6b61353c | 2515 | file, then reindent and see if any following lines need further |
6bf7aab6 DL |
2516 | adjustments. |
2517 | ||
6b61353c KH |
2518 | @deffn Command c-set-offset symbol offset |
2519 | @findex set-offset (c-) | |
2520 | @kindex C-c C-o | |
2521 | This is the command bound to @kbd{C-c C-o}. It provides a convenient | |
2522 | way to set offsets on @code{c-offsets-alist} both interactively (see | |
2523 | the example above) and from your mode hook. | |
2524 | ||
2525 | It takes two arguments when used programmatically: @var{symbol} is the | |
2526 | syntactic element symbol to change and @var{offset} is the new offset | |
2527 | for that syntactic element. | |
2528 | @end deffn | |
2529 | ||
d7bd46ed GM |
2530 | |
2531 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
2532 | @node Permanent Customization, Hooks, Interactive Customization, Customizing Indentation | |
2533 | @comment node-name, next, previous, up | |
6b61353c KH |
2534 | @section Permanent Customization |
2535 | @cindex customization, permanent | |
d7bd46ed | 2536 | @cindex permanent customization |
6bf7aab6 | 2537 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
6bf7aab6 | 2538 | |
d7bd46ed GM |
2539 | To make your changes permanent, you need to add some lisp code to your |
2540 | @file{.emacs} file. @ccmode{} supports many different ways to be | |
2541 | configured, from the straightforward way by setting variables globally | |
2542 | in @file{.emacs} or in the Customization interface, to the complex and | |
2543 | precisely controlled way by using styles and hook functions. | |
2544 | ||
2545 | The simplest way of customizing @ccmode{} permanently is to set the | |
2546 | variables in your @file{.emacs} with @code{setq} and similar commands. | |
6b61353c KH |
2547 | So to make a permanent setting of @code{substatement-open} to 0, add |
2548 | this to the @file{.emacs} file: | |
2549 | ||
d7bd46ed GM |
2550 | @example |
2551 | @group | |
6b61353c KH |
2552 | (setq c-offsets-alist |
2553 | '((substatement-open . 0))) | |
d7bd46ed GM |
2554 | @end group |
2555 | @end example | |
2556 | ||
6b61353c KH |
2557 | When @ccmode{} initializes a buffer, it will fill out |
2558 | @code{c-offsets-alist} with the remaining syntactic symbols according to | |
2559 | the style system. | |
d7bd46ed GM |
2560 | |
2561 | You can also use the more user friendly Customization interface, but | |
2562 | this manual does not cover how that works. | |
2563 | ||
2564 | Variables set like this at the top level in @file{.emacs} take effect in | |
2565 | all @ccmode{} buffers, regardless of language. The indentation style | |
6b61353c | 2566 | related variables, e.g. @code{c-offsets-alist}, that you don't set this |
f214c025 GM |
2567 | way get their value from the style system (@pxref{Styles}), and they |
2568 | therefore depend on the setting of @code{c-default-style}. Note that if | |
2569 | you use Customize, this means that the greyed-out default values | |
2570 | presented there might not be the ones you actually get, since the actual | |
2571 | values depend on the style, which may very well be different for | |
2572 | different languages. | |
d7bd46ed GM |
2573 | |
2574 | If you want to make more advanced configurations, e.g. language-specific | |
6b61353c | 2575 | customization, setting global variables isn't enough. For that you can |
d7bd46ed GM |
2576 | use the language hooks, see @ref{Hooks}, and/or the style system, see |
2577 | @ref{Styles}. | |
2578 | ||
6b61353c | 2579 | @defopt c-style-variables-are-local-p |
d7bd46ed | 2580 | @vindex style-variables-are-local-p (c-) |
6b61353c KH |
2581 | By default, all style variables are buffer local, so that different |
2582 | buffers can have different style settings. If you only use one style | |
2583 | in all the files you edit you might want to share them between buffers | |
2584 | so that a change take effect in all buffers. That's done by setting | |
2585 | this variable to @code{nil}. The value takes effect when @ccmode{} is | |
2586 | activated in a buffer for the first time in the Emacs session, so you | |
2587 | typically set it in your @file{.emacs} file and then restart Emacs. | |
2588 | @end defopt | |
d7bd46ed GM |
2589 | |
2590 | ||
2591 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
2592 | @node Hooks, Styles, Permanent Customization, Customizing Indentation | |
2593 | @comment node-name, next, previous, up | |
6b61353c KH |
2594 | @section Hooks |
2595 | @cindex mode hooks | |
6bf7aab6 DL |
2596 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
2597 | ||
d7bd46ed GM |
2598 | @ccmode{} provides several hooks that you can use to customize the mode |
2599 | according to your coding style. Each language mode has its own hook, | |
2600 | adhering to standard Emacs major mode conventions. There is also one | |
2601 | general hook and one package initialization hook: | |
6bf7aab6 | 2602 | |
6b61353c KH |
2603 | @defvar c-initialization-hook |
2604 | @vindex initialization-hook (c-) | |
2605 | Hook run only once per Emacs session, when @ccmode{} is initialized. | |
2606 | @end defvar | |
6bf7aab6 | 2607 | |
6b61353c KH |
2608 | @defvar c-mode-common-hook |
2609 | @vindex mode-common-hook (c-) | |
2610 | Common hook across all languages. It's run immediately before the | |
2611 | language specific hook. | |
2612 | @end defvar | |
2613 | ||
2614 | @defvar c-mode-hook | |
2615 | @defvarx c++-mode-hook | |
2616 | @defvarx objc-mode-hook | |
2617 | @defvarx java-mode-hook | |
2618 | @defvarx idl-mode-hook | |
2619 | @defvarx pike-mode-hook | |
2620 | @defvarx awk-mode-hook | |
2621 | The language specific mode hooks. The appropriate one is run as the | |
2622 | last thing when you enter that language mode. | |
2623 | @end defvar | |
cb7f2e96 GM |
2624 | |
2625 | Note that all the language-specific mode setup that CC Mode does is done | |
2626 | prior to both @code{c-mode-common-hook} and the language specific hook. | |
2627 | That includes installing the indentation style, which can be mode | |
2628 | specific (and also is by default for Java mode). Thus, any style | |
2629 | settings done in @code{c-mode-common-hook} will override whatever | |
2630 | language-specific style is chosen by @code{c-default-style}. | |
6bf7aab6 DL |
2631 | |
2632 | Here's a simplified example of what you can add to your @file{.emacs} | |
d7bd46ed GM |
2633 | file to do things whenever any @ccmode{} language is edited. See the |
2634 | Emacs manuals for more information on customizing Emacs via hooks. | |
2635 | @xref{Sample .emacs File}, for a more complete sample @file{.emacs} | |
2636 | file. | |
6bf7aab6 | 2637 | |
6b61353c | 2638 | @example |
6bf7aab6 DL |
2639 | (defun my-c-mode-common-hook () |
2640 | ;; my customizations for all of c-mode and related modes | |
d7bd46ed | 2641 | (no-case-fold-search) |
6bf7aab6 DL |
2642 | ) |
2643 | (add-hook 'c-mode-common-hook 'my-c-mode-common-hook) | |
6bf7aab6 DL |
2644 | @end example |
2645 | ||
6bf7aab6 DL |
2646 | |
2647 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
d7bd46ed GM |
2648 | @node Styles, Advanced Customizations, Hooks, Customizing Indentation |
2649 | @comment node-name, next, previous, up | |
6b61353c | 2650 | @section Styles |
d7bd46ed | 2651 | @cindex styles |
6bf7aab6 DL |
2652 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
2653 | ||
2654 | Most people only need to edit code formatted in just a few well-defined | |
2655 | and consistent styles. For example, their organization might impose a | |
2656 | ``blessed'' style that all its programmers must conform to. Similarly, | |
d7bd46ed GM |
2657 | people who work on GNU software will have to use the GNU coding style. |
2658 | Some shops are more lenient, allowing a variety of coding styles, and as | |
2659 | programmers come and go, there could be a number of styles in use. For | |
2660 | this reason, @ccmode{} makes it convenient for you to set up logical | |
2661 | groupings of customizations called @dfn{styles}, associate a single name | |
2662 | for any particular style, and pretty easily start editing new or | |
2663 | existing code using these styles. | |
2664 | ||
2665 | @cindex style variables | |
2666 | The variables that the style system affect are called @dfn{style | |
2667 | variables}. They are handled specially in several ways: | |
2668 | ||
2669 | @itemize @bullet | |
2670 | @item | |
6b61353c KH |
2671 | Style variables are by default buffer local variables. However, they |
2672 | can instead be made global by setting | |
2673 | @code{c-style-variables-are-local-p} to @code{nil} before @ccmode{} is | |
2674 | initialized. | |
d7bd46ed | 2675 | |
6b61353c | 2676 | @item |
d7bd46ed GM |
2677 | @vindex c-old-style-variable-behavior |
2678 | @vindex old-style-variable-behavior (c-) | |
d7bd46ed GM |
2679 | The default value of any style variable (with two exceptions --- see |
2680 | below) is the special symbol @code{set-from-style}. Variables that are | |
2681 | still set to that symbol when a @ccmode{} buffer is initialized will be | |
2682 | set according to the current style, otherwise they will keep their | |
2683 | current value@footnote{This is a big change from versions of @ccmode{} | |
2684 | earlier than 5.26, where such settings would get overridden by the style | |
2685 | system unless special precautions were taken. That was changed since it | |
2686 | was counterintuitive and confusing, especially to novice users. If your | |
2687 | configuration depends on the old overriding behavior, you can set the | |
2688 | variable @code{c-old-style-variable-behavior} to non-@code{nil}.}. | |
2689 | ||
2690 | Note that when we talk about the ``default value'' for a style variable, | |
2691 | we don't mean the @code{set-from-style} symbol that all style variables | |
2692 | are set to initially, but instead the value it will get at mode | |
2693 | initialization when neither a style nor a global setting has set its | |
2694 | value. | |
2695 | ||
2696 | The style variable @code{c-offsets-alist} is handled a little | |
2697 | differently from the other style variables. It's an association list, | |
2698 | and is thus by default set to the empty list, @code{nil}. When the | |
2699 | style system is initialized, any syntactic symbols already on it are | |
2700 | kept --- only the missing ones are filled in from the chosen style. | |
2701 | ||
2702 | The style variable @code{c-special-indent-hook} is also handled in a | |
2703 | special way. Styles may only add more functions on this hook, so the | |
2704 | global settings on it are always preserved@footnote{This did not change | |
2705 | in version 5.26.}. | |
2706 | ||
2707 | @item | |
2708 | The global settings of style variables get captured in the special | |
2709 | @code{user} style, which is used as the base for all the other styles. | |
2710 | @xref{Built-in Styles}, for details. | |
d7bd46ed GM |
2711 | @end itemize |
2712 | ||
2713 | The style variables are: | |
2714 | @code{c-basic-offset}, | |
2715 | @code{c-comment-only-line-offset}, | |
2716 | @code{c-block-comment-prefix}, | |
2717 | @code{c-comment-prefix-regexp}, | |
2718 | @code{c-cleanup-list}, | |
2719 | @code{c-hanging-braces-alist}, | |
2720 | @code{c-hanging-colons-alist}, | |
2721 | @code{c-hanging-semi&comma-criteria}, | |
2722 | @code{c-backslash-column}, | |
6b61353c | 2723 | @code{c-backslash-max-column}, |
d7bd46ed GM |
2724 | @code{c-special-indent-hook}, |
2725 | @code{c-label-minimum-indentation}, and | |
2726 | @code{c-offsets-alist}. | |
6bf7aab6 DL |
2727 | |
2728 | @menu | |
2729 | * Built-in Styles:: | |
6b61353c | 2730 | * Choosing a Style:: |
6bf7aab6 DL |
2731 | * Adding Styles:: |
2732 | * File Styles:: | |
2733 | @end menu | |
2734 | ||
2735 | ||
2736 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6b61353c | 2737 | @node Built-in Styles, Choosing a Style, , Styles |
d7bd46ed GM |
2738 | @comment node-name, next, previous, up |
2739 | @subsection Built-in Styles | |
6b61353c | 2740 | @cindex styles, built-in |
6bf7aab6 DL |
2741 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
2742 | ||
2743 | If you're lucky, one of @ccmode{}'s built-in styles might be just | |
2744 | what you're looking for. These include: | |
2745 | ||
6b61353c KH |
2746 | @table @code |
2747 | @item gnu | |
6bf7aab6 | 2748 | @cindex GNU style |
6b61353c | 2749 | Coding style blessed by the Free Software Foundation |
d7bd46ed | 2750 | for C code in GNU programs. |
6bf7aab6 | 2751 | |
6b61353c | 2752 | @item k&r |
6bf7aab6 | 2753 | @cindex K&R style |
6b61353c | 2754 | The classic Kernighan and Ritchie style for C code. |
6bf7aab6 | 2755 | |
6b61353c | 2756 | @item bsd |
6bf7aab6 | 2757 | @cindex BSD style |
6b61353c | 2758 | Also known as ``Allman style'' after Eric Allman. |
6bf7aab6 | 2759 | |
6b61353c KH |
2760 | @item whitesmith |
2761 | @cindex Whitesmith style | |
2762 | Popularized by the examples that came with Whitesmiths C, an early | |
2763 | commercial C compiler. | |
6bf7aab6 | 2764 | |
6b61353c | 2765 | @item stroustrup |
6bf7aab6 | 2766 | @cindex Stroustrup style |
6b61353c | 2767 | The classic Stroustrup style for C++ code. |
6bf7aab6 | 2768 | |
6b61353c | 2769 | @item ellemtel |
6bf7aab6 | 2770 | @cindex Ellemtel style |
6b61353c KH |
2771 | Popular C++ coding standards as defined by ``Programming in C++, Rules |
2772 | and Recommendations,'' Erik Nyquist and Mats Henricson, | |
2773 | Ellemtel@footnote{This document is available at | |
d7bd46ed GM |
2774 | @uref{http://www.doc.ic.ac.uk/lab/cplus/c++.rules/} among other |
2775 | places.}. | |
6bf7aab6 | 2776 | |
6b61353c | 2777 | @item linux |
6bf7aab6 | 2778 | @cindex Linux style |
6b61353c | 2779 | C coding standard for Linux (the kernel). |
6bf7aab6 | 2780 | |
6b61353c | 2781 | @item python |
6bf7aab6 | 2782 | @cindex Python style |
6b61353c KH |
2783 | C coding standard for Python extension modules@footnote{Python is a |
2784 | high level scripting language with a C/C++ foreign function interface. | |
2785 | For more information, see @uref{http://www.python.org/}.}. | |
6bf7aab6 | 2786 | |
6b61353c | 2787 | @item java |
6bf7aab6 | 2788 | @cindex Java style |
6b61353c | 2789 | The style for editing Java code. Note that the default |
cb7f2e96 GM |
2790 | value for @code{c-default-style} installs this style when you enter |
2791 | @code{java-mode}. | |
6bf7aab6 | 2792 | |
6b61353c | 2793 | @item user |
6bf7aab6 | 2794 | @cindex User style |
6b61353c | 2795 | This is a special style for several reasons. First, the |
d7bd46ed GM |
2796 | @ccmode{} customizations you do by using either the Customization |
2797 | interface, or by writing @code{setq}'s at the top level of your | |
2798 | @file{.emacs} file, will be captured in the @code{user} style. Also, | |
2799 | all other styles implicitly inherit their settings from @code{user} | |
2800 | style. This means that for any styles you add via @code{c-add-style} | |
2801 | (@pxref{Adding Styles}) you need only define the differences between | |
2802 | your new style and @code{user} style. | |
6b61353c | 2803 | @end table |
d7bd46ed | 2804 | |
d7bd46ed | 2805 | |
6b61353c KH |
2806 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
2807 | @node Choosing a Style, Adding Styles, Built-in Styles, Styles | |
2808 | @comment node-name, next, previous, up | |
2809 | @subsection Choosing a Style | |
2810 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
2811 | ||
2812 | Use @kbd{C-c .} to choose a style interactively: | |
2813 | ||
2814 | @deffn Command c-set-style style-name | |
2815 | @findex set-style (c-) | |
2816 | @kindex C-c . | |
2817 | Switch to the specified style in the current buffer. Use | |
2818 | interactively like this: | |
2819 | ||
2820 | @example | |
2821 | @kbd{C-c . @var{style-name} RET} | |
2822 | @end example | |
2823 | ||
2824 | Note that all style names are case insensitive, even the ones you | |
2825 | define. | |
2826 | ||
2827 | Setting a style in this way does @emph{not} automatically reindent your | |
2828 | file. For commands that you can use to view the effect of your changes, | |
2829 | see @ref{Commands}. | |
2830 | @end deffn | |
2831 | ||
2832 | The default style in all newly created buffers is @code{gnu}, except | |
2833 | in Java mode where it's @code{java}. Although the @code{user} style | |
2834 | is not the default style, any style variable settings you do with the | |
2835 | Customization interface or on the top level in your @file{.emacs} file | |
2836 | will by default override the style system, so you don't need to set | |
2837 | @code{c-default-style} to @code{user} to see the effect of such | |
2838 | settings. | |
2839 | ||
2840 | @defopt c-default-style | |
2841 | @vindex default-style (c-) | |
2842 | This variable specifies which style to install by default in new | |
2843 | buffers. It takes either a style name string, or an association list | |
2844 | of major mode symbols to style names: | |
2845 | ||
2846 | @enumerate | |
2847 | @item | |
2848 | When @code{c-default-style} is a string, it must be an existing style | |
2849 | name. This style is then used for all modes. | |
6bf7aab6 | 2850 | |
d7bd46ed | 2851 | @item |
6b61353c KH |
2852 | When @code{c-default-style} is an association list, the mode language |
2853 | is looked up to find a style name string. | |
d7bd46ed GM |
2854 | |
2855 | @item | |
6b61353c KH |
2856 | If @code{c-default-style} is an association list where the mode |
2857 | language mode isn't found then the special symbol @samp{other} is | |
2858 | looked up. If it's found then the associated style is used. | |
d7bd46ed GM |
2859 | |
2860 | @item | |
6b61353c | 2861 | If @samp{other} is not found then the @samp{gnu} style is used. |
d7bd46ed GM |
2862 | |
2863 | @item | |
6b61353c | 2864 | In all cases, the style described in @code{c-default-style} is installed |
d7bd46ed | 2865 | @emph{before} the language hooks are run, so you can always override |
6b61353c | 2866 | this setting by including an explicit call to @code{c-set-style} in your |
d7bd46ed | 2867 | language mode hook, or in @code{c-mode-common-hook}. |
d7bd46ed | 2868 | @end enumerate |
6b61353c | 2869 | @end defopt |
6bf7aab6 | 2870 | |
6b61353c | 2871 | @defvar c-indentation-style |
6bf7aab6 | 2872 | @vindex indentation-style (c-) |
6b61353c KH |
2873 | This variable always contains the buffer's current style name, as a |
2874 | string. | |
2875 | @end defvar | |
6bf7aab6 DL |
2876 | |
2877 | ||
2878 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6b61353c | 2879 | @node Adding Styles, File Styles, Choosing a Style, Styles |
d7bd46ed GM |
2880 | @comment node-name, next, previous, up |
2881 | @subsection Adding Styles | |
6bf7aab6 DL |
2882 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
2883 | ||
6bf7aab6 DL |
2884 | If none of the built-in styles is appropriate, you'll probably want to |
2885 | add a new @dfn{style definition}. Styles are kept in the | |
6b61353c KH |
2886 | @code{c-style-alist} variable, but you should never modify this |
2887 | variable directly. Instead, @ccmode{} provides the function | |
6bf7aab6 | 2888 | @code{c-add-style} that you can use to easily add new styles or change |
6b61353c KH |
2889 | existing styles: |
2890 | ||
2891 | @defun c-add-style stylename description &optional set-p | |
2892 | @findex add-style (c-) | |
2893 | Add or update a style. If @var{stylename} is not already in | |
2894 | @code{c-style-alist} then a new style according to @var{description} | |
2895 | is added, otherwise the existing style is changed. If the optional | |
2896 | @var{set-p} is non-@code{nil} then the new style is applied to the | |
2897 | current buffer as well. | |
6bf7aab6 DL |
2898 | |
2899 | @comment TBD: The next paragraph is bogus. I really need to better | |
2900 | @comment document adding styles, including setting up inherited styles. | |
2901 | ||
2902 | The sample @file{.emacs} file provides a concrete example of how a new | |
2903 | style can be added and automatically set. @xref{Sample .emacs File}. | |
6b61353c KH |
2904 | @end defun |
2905 | ||
2906 | @defvar c-style-alist | |
2907 | @vindex style-alist (c-) | |
2908 | This is the variable that holds the definitions for the styles. It | |
2909 | should not be changed directly; use @code{c-add-style} instead. | |
2910 | @end defvar | |
6bf7aab6 | 2911 | |
6bf7aab6 | 2912 | |
d7bd46ed GM |
2913 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
2914 | @node File Styles, , Adding Styles, Styles | |
2915 | @comment node-name, next, previous, up | |
2916 | @subsection File Styles | |
6b61353c | 2917 | @cindex styles, file local |
6bf7aab6 DL |
2918 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
2919 | ||
6b61353c | 2920 | @cindex file local variables |
6bf7aab6 | 2921 | |
6b61353c KH |
2922 | The Emacs manual describes how you can customize certain variables on |
2923 | a per-file basis by including a @dfn{file local variable} block at the | |
2924 | end of the file. So far, you've only seen a functional interface to | |
2925 | @ccmode{} customization, which can't be used there. @ccmode{} | |
2926 | provides two variables allow customization of the indentation style on | |
2927 | a per-file basis: | |
6bf7aab6 | 2928 | |
6b61353c | 2929 | @defvar c-file-style |
6bf7aab6 | 2930 | @vindex file-style (c-) |
6b61353c KH |
2931 | This variable can be set to a style name string. When the file is |
2932 | visited, @ccmode{} will automatically set the file's style to this | |
2933 | one using @code{c-set-style}. | |
2934 | @end defvar | |
6bf7aab6 | 2935 | |
6b61353c KH |
2936 | @defvar c-file-offsets |
2937 | @vindex file-offsets (c-) | |
2938 | This variable takes an association list similar to what is allowed in | |
2939 | @code{c-offsets-alist}. When the file is visited, @ccmode{} will | |
2940 | automatically institute these offsets using @code{c-set-offset}. | |
2941 | @end defvar | |
6bf7aab6 DL |
2942 | |
2943 | Note that file style settings (i.e. @code{c-file-style}) are applied | |
2944 | before file offset settings (i.e. @code{c-file-offsets}). Also, if | |
2945 | either of these are set in a file's local variable section, all the | |
2946 | style variable values are made local to that buffer. | |
2947 | ||
2948 | ||
2949 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
d7bd46ed GM |
2950 | @node Advanced Customizations, , Styles, Customizing Indentation |
2951 | @comment node-name, next, previous, up | |
6b61353c | 2952 | @section Advanced Customizations |
6bf7aab6 DL |
2953 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
2954 | ||
6b61353c KH |
2955 | For most users, @ccmode{} will support their coding styles with very |
2956 | little need for more advanced customizations. Usually, one of the | |
2957 | standard styles (@pxref{Built-in Styles}) will do the trick. At most, | |
2958 | perhaps one of the syntactic symbol offsets will need to be tweaked | |
2959 | slightly, or maybe @code{c-basic-offset} will need to be changed. | |
2960 | However, some styles require a more flexible framework for | |
2961 | customization, and one of the real strengths of @ccmode{} is that the | |
2962 | syntactic analysis model provides just such a framework. This allows | |
6bf7aab6 DL |
2963 | you to implement custom indentation calculations for situations not |
2964 | handled by the mode directly. | |
2965 | ||
6bf7aab6 DL |
2966 | @menu |
2967 | * Custom Indentation Functions:: | |
2968 | * Custom Brace and Colon Hanging:: | |
6b61353c | 2969 | * Customizing Semicolons and Commas:: |
6bf7aab6 DL |
2970 | * Other Special Indentations:: |
2971 | @end menu | |
2972 | ||
2973 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
d7bd46ed GM |
2974 | @node Custom Indentation Functions, Custom Brace and Colon Hanging, , Advanced Customizations |
2975 | @comment node-name, next, previous, up | |
2976 | @subsection Custom Indentation Functions | |
6b61353c | 2977 | @cindex customization, indentation functions |
6bf7aab6 DL |
2978 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
2979 | ||
d7bd46ed GM |
2980 | The most flexible way to customize @ccmode{} is by writing custom |
2981 | indentation functions, and associating them with specific syntactic | |
2982 | symbols (@pxref{Syntactic Symbols}). @ccmode{} itself uses indentation | |
2983 | functions to provide more sophisticated indentation, for example when | |
2984 | lining up C++ stream operator blocks: | |
6b61353c | 2985 | |
6bf7aab6 DL |
2986 | @example |
2987 | @group | |
6b61353c KH |
2988 | 1: void main(int argc, char**) |
2989 | 2: @{ | |
2990 | 3: cout << "There were " | |
2991 | 4: << argc | |
2992 | 5: << "arguments passed to the program" | |
2993 | 6: << endl; | |
2994 | 7: @} | |
6bf7aab6 DL |
2995 | @end group |
2996 | @end example | |
2997 | ||
2998 | In this example, lines 4 through 6 are assigned the @code{stream-op} | |
2999 | syntactic symbol. Here, @code{stream-op} has an offset of @code{+}, and | |
3000 | with a @code{c-basic-offset} of 2, you can see that lines 4 through 6 | |
3001 | are simply indented two spaces to the right of line 3. But perhaps we'd | |
3002 | like @ccmode{} to be a little more intelligent so that it aligns | |
3003 | all the @samp{<<} symbols in lines 3 through 6. To do this, we have | |
6b61353c KH |
3004 | to write a custom indentation function which finds the column of the first |
3005 | stream operator on the first line of the statement. Here is sample | |
6bf7aab6 | 3006 | lisp code implementing this: |
6bf7aab6 | 3007 | |
6b61353c | 3008 | @example |
6bf7aab6 | 3009 | (defun c-lineup-streamop (langelem) |
6bf7aab6 | 3010 | (save-excursion |
6b61353c KH |
3011 | (goto-char (cdr langelem)) |
3012 | (re-search-forward "<<\\|>>" (c-point 'eol) 'move) | |
3013 | (goto-char (match-beginning 0)) | |
3014 | (vector (current-column)))) | |
6bf7aab6 | 3015 | @end example |
6b61353c | 3016 | |
d7bd46ed | 3017 | Indentation functions take a single argument, which is a syntactic |
6b61353c KH |
3018 | component cons cell (@pxref{Syntactic Analysis}). The function can |
3019 | return an integer which is added to the running total indentation for | |
3020 | the line, or a vector containing an integer which is an absolute | |
3021 | column to align to. Usually an absolute column is wanted when | |
3022 | aligning to existing text, as in this example. | |
d7bd46ed GM |
3023 | |
3024 | The function should return @code{nil} if it's used in a situation where | |
6b61353c | 3025 | it doesn't want to make any decision. If the function is used in a list |
d7bd46ed GM |
3026 | expression (@pxref{Customizing Indentation}), that will cause @ccmode{} |
3027 | to go on and check the next entry in the list. | |
6bf7aab6 | 3028 | |
6bf7aab6 DL |
3029 | Now, to associate the function @code{c-lineup-streamop} with the |
3030 | @code{stream-op} syntactic symbol, we can add something like the | |
3031 | following to our @code{c++-mode-hook}@footnote{It probably makes more | |
3032 | sense to add this to @code{c++-mode-hook} than @code{c-mode-common-hook} | |
d7bd46ed | 3033 | since stream operators are only relevant for C++.}: |
6bf7aab6 | 3034 | |
6b61353c | 3035 | @example |
6bf7aab6 | 3036 | (c-set-offset 'stream-op 'c-lineup-streamop) |
6bf7aab6 DL |
3037 | @end example |
3038 | ||
6b61353c | 3039 | Now the function looks like this after reindenting (using @kbd{C-c |
6bf7aab6 | 3040 | C-q}): |
6b61353c | 3041 | |
6bf7aab6 DL |
3042 | @example |
3043 | @group | |
6b61353c KH |
3044 | 1: void main(int argc, char**) |
3045 | 2: @{ | |
3046 | 3: cout << "There were " | |
3047 | 4: << argc | |
3048 | 5: << " arguments passed to the program" | |
3049 | 6: << endl; | |
3050 | 7: @} | |
6bf7aab6 DL |
3051 | @end group |
3052 | @end example | |
3053 | ||
6bf7aab6 DL |
3054 | Custom indentation functions can be as simple or as complex as you like, |
3055 | and any syntactic symbol that appears in @code{c-offsets-alist} can have | |
d7bd46ed | 3056 | a custom indentation function associated with it. |
6bf7aab6 | 3057 | |
d7bd46ed GM |
3058 | @ccmode{} comes with an extensive set of predefined indentation |
3059 | functions, not all of which are used by the default styles. So there's | |
3060 | a good chance the function you want already exists. @xref{Indentation | |
3061 | Functions}, for a list of them. If you have written an indentation | |
3062 | function that you think is generally useful, you're very welcome to | |
3063 | contribute it; please contact @email{bug-cc-mode@@gnu.org}. | |
6bf7aab6 | 3064 | |
6bf7aab6 DL |
3065 | |
3066 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6b61353c | 3067 | @node Custom Brace and Colon Hanging, Customizing Semicolons and Commas, Custom Indentation Functions, Advanced Customizations |
d7bd46ed GM |
3068 | @comment node-name, next, previous, up |
3069 | @subsection Custom Brace and Colon Hanging | |
6bf7aab6 DL |
3070 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
3071 | ||
3072 | @vindex c-hanging-braces-alist | |
3073 | @vindex hanging-braces-alist (c-) | |
3074 | Syntactic symbols aren't the only place where you can customize | |
3075 | @ccmode{} with the lisp equivalent of callback functions. Brace | |
3076 | ``hanginess'' can also be determined by custom functions associated with | |
d7bd46ed | 3077 | syntactic symbols on the @code{c-hanging-braces-alist} style variable. |
6b61353c | 3078 | Remember that @var{action}'s are typically a list containing some |
d7bd46ed | 3079 | combination of the symbols @code{before} and @code{after} |
6b61353c | 3080 | (@pxref{Hanging Braces}). However, an @var{action} can also be a |
d7bd46ed GM |
3081 | function which gets called when a brace matching that syntactic symbol |
3082 | is entered. | |
6bf7aab6 | 3083 | |
6b61353c KH |
3084 | @cindex customization, brace hanging |
3085 | These @var{action} functions are called with two arguments: the | |
6bf7aab6 | 3086 | syntactic symbol for the brace, and the buffer position at which the |
6b61353c | 3087 | brace was inserted. The @var{action} function is expected to return a |
d7bd46ed GM |
3088 | list containing some combination of @code{before} and @code{after}, |
3089 | including neither of them (i.e. @code{nil}). This return value has the | |
3090 | normal brace hanging semantics. | |
6bf7aab6 DL |
3091 | |
3092 | As an example, @ccmode{} itself uses this feature to dynamically | |
3093 | determine the hanginess of braces which close ``do-while'' | |
3094 | constructs: | |
6bf7aab6 | 3095 | |
6b61353c | 3096 | @example |
6bf7aab6 DL |
3097 | void do_list( int count, char** atleast_one_string ) |
3098 | @{ | |
3099 | int i=0; | |
3100 | do @{ | |
3101 | handle_string( atleast_one_string[i] ); | |
3102 | i++; | |
3103 | @} while( i < count ); | |
3104 | @} | |
6bf7aab6 DL |
3105 | @end example |
3106 | ||
6bf7aab6 DL |
3107 | @ccmode{} assigns the @code{block-close} syntactic symbol to the |
3108 | brace that closes the @code{do} construct, and normally we'd like the | |
3109 | line that follows a @code{block-close} brace to begin on a separate | |
3110 | line. However, with ``do-while'' constructs, we want the | |
3111 | @code{while} clause to follow the closing brace. To do this, we | |
6b61353c | 3112 | associate the @code{block-close} symbol with the @var{action} function |
6bf7aab6 | 3113 | @code{c-snug-do-while}: |
6bf7aab6 | 3114 | |
6b61353c | 3115 | @example |
6bf7aab6 | 3116 | (defun c-snug-do-while (syntax pos) |
6b61353c | 3117 | "Dynamically calculate brace hanginess for do-while statements." |
6bf7aab6 DL |
3118 | (save-excursion |
3119 | (let (langelem) | |
3120 | (if (and (eq syntax 'block-close) | |
3121 | (setq langelem (assq 'block-close c-syntactic-context)) | |
3122 | (progn (goto-char (cdr langelem)) | |
3123 | (if (= (following-char) ?@{) | |
3124 | (forward-sexp -1)) | |
3125 | (looking-at "\\<do\\>[^_]"))) | |
3126 | '(before) | |
3127 | '(before after))))) | |
6bf7aab6 DL |
3128 | @end example |
3129 | ||
6b61353c KH |
3130 | @findex c-snug-do-while |
3131 | @findex snug-do-while (c-) | |
6bf7aab6 DL |
3132 | This function simply looks to see if the brace closes a ``do-while'' |
3133 | clause and if so, returns the list @samp{(before)} indicating | |
3134 | that a newline should be inserted before the brace, but not after it. | |
3135 | In all other cases, it returns the list @samp{(before after)} so | |
3136 | that the brace appears on a line by itself. | |
3137 | ||
6b61353c | 3138 | @defvar c-syntactic-context |
6bf7aab6 | 3139 | @vindex syntactic-context (c-) |
6b61353c KH |
3140 | During the call to the indentation or brace hanging @var{action} |
3141 | function, this variable is bound to the full syntactic analysis list. | |
3142 | @end defvar | |
6bf7aab6 | 3143 | |
6b61353c KH |
3144 | @cindex customization, colon hanging |
3145 | @vindex c-hanging-colons-alist | |
3146 | @vindex hanging-colons-alist (c-) | |
6bf7aab6 | 3147 | Note that for symmetry, colon hanginess should be customizable by |
6b61353c KH |
3148 | allowing function symbols as @var{action}s on the |
3149 | @code{c-hanging-colons-alist} style variable. Since no use has actually | |
d7bd46ed | 3150 | been found for this feature, it isn't currently implemented! |
6bf7aab6 | 3151 | |
6bf7aab6 | 3152 | |
d7bd46ed | 3153 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
6b61353c | 3154 | @node Customizing Semicolons and Commas, Other Special Indentations, Custom Brace and Colon Hanging, Advanced Customizations |
d7bd46ed | 3155 | @comment node-name, next, previous, up |
6b61353c KH |
3156 | @subsection Customizing Semicolons and Commas |
3157 | @cindex customization, semicolon newlines | |
3158 | @cindex customization, comma newlines | |
6bf7aab6 DL |
3159 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
3160 | ||
6b61353c KH |
3161 | You can also customize the insertion of newlines after semicolons and |
3162 | commas when the auto-newline minor mode is enabled (@pxref{Minor | |
3163 | Modes}). | |
6bf7aab6 | 3164 | |
6b61353c KH |
3165 | @defopt c-hanging-semi&comma-criteria |
3166 | @vindex hanging-semi&comma-criteria (c-) | |
3167 | This style variable takes a list of hooks that get called when a | |
3168 | semicolon or comma is inserted. The hooks are called in order without | |
3169 | arguments, and are expected to return one of the following values: | |
6bf7aab6 | 3170 | |
6b61353c KH |
3171 | @table @code |
3172 | @item t | |
3173 | A newline is inserted, and no more functions from the list are called. | |
3174 | @item stop | |
3175 | No more functions from the list are called, but no newline is | |
3176 | inserted. | |
3177 | @item nil | |
3178 | No determination is made, and the next function in the list is called. | |
3179 | @end table | |
6bf7aab6 DL |
3180 | |
3181 | If every function in the list is called without a determination being | |
3182 | made, then no newline is added. The default value for this variable is a | |
3183 | list containing a single function which inserts newlines only after | |
6b61353c | 3184 | semicolons which do not appear inside parenthesis lists (i.e. those |
6bf7aab6 | 3185 | that separate @code{for}-clause statements). |
6b61353c | 3186 | @end defopt |
6bf7aab6 | 3187 | |
6b61353c | 3188 | @defun c-semi&comma-no-newlines-before-nonblanks |
6bf7aab6 | 3189 | @findex semi&comma-no-newlines-before-nonblanks (c-) |
6b61353c KH |
3190 | This is an example of a criteria function, provided by @ccmode{}. It |
3191 | prevents newlines from being inserted after semicolons when there is a | |
3192 | non-blank following line. Otherwise, it makes no determination. To | |
3193 | use, add this function to the front of the | |
3194 | @code{c-hanging-semi&comma-criteria} list. | |
6bf7aab6 DL |
3195 | |
3196 | @example | |
6bf7aab6 DL |
3197 | (defun c-semi&comma-no-newlines-before-nonblanks () |
3198 | (save-excursion | |
3199 | (if (and (eq last-command-char ?\;) | |
3200 | (zerop (forward-line 1)) | |
3201 | (not (looking-at "^[ \t]*$"))) | |
3202 | 'stop | |
3203 | nil))) | |
6bf7aab6 | 3204 | @end example |
6b61353c | 3205 | @end defun |
6bf7aab6 | 3206 | |
6b61353c | 3207 | @defun c-semi&comma-inside-parenlist |
6bf7aab6 | 3208 | @findex semi&comma-inside-parenlist (c-) |
6b61353c | 3209 | @defunx c-semi&comma-no-newlines-for-oneline-inliners |
6bf7aab6 | 3210 | @findex semi&comma-no-newlines-for-oneline-inliners (c-) |
d7bd46ed GM |
3211 | The function @code{c-semi&comma-inside-parenlist} is what prevents |
3212 | newlines from being inserted inside the parenthesis list of @code{for} | |
3213 | statements. In addition to | |
6bf7aab6 DL |
3214 | @code{c-semi&comma-no-newlines-before-nonblanks} described above, |
3215 | @ccmode{} also comes with the criteria function | |
3216 | @code{c-semi&comma-no-newlines-for-oneline-inliners}, which suppresses | |
3217 | newlines after semicolons inside one-line inline method definitions | |
6b61353c KH |
3218 | (e.g. in C++ or Java). |
3219 | @end defun | |
6bf7aab6 | 3220 | |
6bf7aab6 | 3221 | |
d7bd46ed | 3222 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
6b61353c | 3223 | @node Other Special Indentations, , Customizing Semicolons and Commas, Advanced Customizations |
d7bd46ed GM |
3224 | @comment node-name, next, previous, up |
3225 | @subsection Other Special Indentations | |
6bf7aab6 DL |
3226 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
3227 | ||
6b61353c KH |
3228 | Here are the remaining odds and ends regarding indentation: |
3229 | ||
3230 | @defopt c-label-minimum-indentation | |
6bf7aab6 | 3231 | @vindex label-minimum-indentation (c-) |
d7bd46ed | 3232 | In @samp{gnu} style (@pxref{Built-in Styles}), a minimum indentation |
6bf7aab6 | 3233 | is imposed on lines inside top-level constructs. This minimum |
6b61353c | 3234 | indentation is controlled by this style variable. The default value |
6bf7aab6 | 3235 | is 1. |
6b61353c | 3236 | @end defopt |
6bf7aab6 | 3237 | |
6b61353c | 3238 | @defopt c-special-indent-hook |
6bf7aab6 | 3239 | @vindex special-indent-hook (c-) |
6b61353c KH |
3240 | This style variable is a standard hook variable that is called after |
3241 | every line is indented by @ccmode{}. You can use it to do any special | |
3242 | indentation or line adjustments your style dictates, such as adding | |
3243 | extra indentation to constructors or destructor declarations in a | |
3244 | class definition, etc. Note that you should not change point or mark | |
3245 | inside your @code{c-special-indent-hook} functions, i.e. you'll | |
3246 | probably want to wrap your function in a @code{save-excursion}. | |
3247 | ||
3248 | Setting @code{c-special-indent-hook} in your style definition is | |
3249 | handled slightly differently than other variables. In your style | |
3250 | definition, you should set the value for @code{c-special-indent-hook} | |
3251 | to a function or list of functions, which will be appended to | |
3252 | @code{c-special-indent-hook} using @code{add-hook}. That way, the | |
3253 | current setting for the buffer local value of | |
6bf7aab6 | 3254 | @code{c-special-indent-hook} won't be overridden. |
6b61353c | 3255 | @end defopt |
d7bd46ed | 3256 | |
6bf7aab6 | 3257 | |
d7bd46ed GM |
3258 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
3259 | @node Syntactic Symbols, Indentation Functions, Customizing Indentation, Top | |
3260 | @comment node-name, next, previous, up | |
6b61353c | 3261 | @chapter Syntactic Symbols |
6bf7aab6 DL |
3262 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
3263 | ||
6b61353c | 3264 | @cindex syntactic symbols, brief list |
6bf7aab6 DL |
3265 | @vindex c-offsets-alist |
3266 | @vindex offsets-alist (c-) | |
6bf7aab6 | 3267 | Here is a complete list of the recognized syntactic symbols as described |
d7bd46ed GM |
3268 | in the @code{c-offsets-alist} style variable, along with a brief |
3269 | description. More detailed descriptions follow. | |
6bf7aab6 | 3270 | |
d7bd46ed GM |
3271 | @table @code |
3272 | @item string | |
6b61353c | 3273 | Inside a multiline string. |
d7bd46ed | 3274 | @item c |
6b61353c | 3275 | Inside a multiline C style block comment. |
d7bd46ed GM |
3276 | @item defun-open |
3277 | Brace that opens a top-level function definition. | |
3278 | @item defun-close | |
3279 | Brace that closes a top-level function definition. | |
3280 | @item defun-block-intro | |
3281 | The first line in a top-level defun. | |
3282 | @item class-open | |
3283 | Brace that opens a class definition. | |
3284 | @item class-close | |
3285 | Brace that closes a class definition. | |
3286 | @item inline-open | |
3287 | Brace that opens an in-class inline method. | |
3288 | @item inline-close | |
3289 | Brace that closes an in-class inline method. | |
3290 | @item func-decl-cont | |
3291 | The region between a function definition's argument list and the | |
3292 | function opening brace (excluding K&R argument declarations). In C, you | |
3293 | cannot put anything but whitespace and comments in this region, however | |
3294 | in C++ and Java, @code{throws} declarations and other things can appear | |
3295 | here. | |
3296 | @item knr-argdecl-intro | |
3297 | First line of a K&R C argument declaration. | |
3298 | @item knr-argdecl | |
3299 | Subsequent lines in a K&R C argument declaration. | |
3300 | @item topmost-intro | |
3301 | The first line in a ``topmost'' definition. | |
3302 | @item topmost-intro-cont | |
6b61353c KH |
3303 | Topmost definition continuation lines. This is only used in the parts |
3304 | that aren't covered by other symbols such as @code{func-decl-cont} and | |
3305 | @code{knr-argdecl}. | |
d7bd46ed GM |
3306 | @item member-init-intro |
3307 | First line in a member initialization list. | |
3308 | @item member-init-cont | |
3309 | Subsequent member initialization list lines. | |
3310 | @item inher-intro | |
3311 | First line of a multiple inheritance list. | |
3312 | @item inher-cont | |
3313 | Subsequent multiple inheritance lines. | |
3314 | @item block-open | |
3315 | Statement block open brace. | |
3316 | @item block-close | |
3317 | Statement block close brace. | |
3318 | @item brace-list-open | |
3319 | Open brace of an enum or static array list. | |
3320 | @item brace-list-close | |
3321 | Close brace of an enum or static array list. | |
3322 | @item brace-list-intro | |
3323 | First line in an enum or static array list. | |
3324 | @item brace-list-entry | |
3325 | Subsequent lines in an enum or static array list. | |
3326 | @item brace-entry-open | |
3327 | Subsequent lines in an enum or static array list where the line begins | |
3328 | with an open brace. | |
3329 | @item statement | |
3330 | A statement. | |
3331 | @item statement-cont | |
3332 | A continuation of a statement. | |
3333 | @item statement-block-intro | |
3334 | The first line in a new statement block. | |
3335 | @item statement-case-intro | |
3336 | The first line in a case block. | |
3337 | @item statement-case-open | |
3338 | The first line in a case block that starts with a brace. | |
3339 | @item substatement | |
3340 | The first line after a conditional or loop construct. | |
3341 | @item substatement-open | |
3342 | The brace that opens a substatement block. | |
6b61353c KH |
3343 | @item substatement-label |
3344 | The first line after a conditional or loop construct if it's a label. | |
d7bd46ed | 3345 | @item case-label |
6b61353c | 3346 | A label in a @code{switch} block. |
d7bd46ed GM |
3347 | @item access-label |
3348 | C++ access control label. | |
3349 | @item label | |
6b61353c | 3350 | Any other label. |
d7bd46ed GM |
3351 | @item do-while-closure |
3352 | The @code{while} line that ends a @code{do}-@code{while} construct. | |
3353 | @item else-clause | |
3354 | The @code{else} line of an @code{if}-@code{else} construct. | |
3355 | @item catch-clause | |
3356 | The @code{catch} or @code{finally} (in Java) line of a | |
3357 | @code{try}-@code{catch} construct. | |
3358 | @item comment-intro | |
3359 | A line containing only a comment introduction. | |
3360 | @item arglist-intro | |
3361 | The first line in an argument list. | |
3362 | @item arglist-cont | |
3363 | Subsequent argument list lines when no arguments follow on the same line | |
6b1f5814 | 3364 | as the arglist opening paren. |
d7bd46ed GM |
3365 | @item arglist-cont-nonempty |
3366 | Subsequent argument list lines when at least one argument follows on the | |
3367 | same line as the arglist opening paren. | |
3368 | @item arglist-close | |
3369 | The solo close paren of an argument list. | |
3370 | @item stream-op | |
3371 | Lines continuing a stream operator (C++ only). | |
3372 | @item inclass | |
3373 | The line is nested inside a class definition. | |
3374 | @item cpp-macro | |
6b61353c KH |
3375 | The start of a preprocessor macro definition. |
3376 | @item cpp-define-intro | |
3377 | The first line inside a multiline preproprocessor macro if | |
3378 | @code{c-syntactic-indentation-in-macros} is set. | |
d7bd46ed | 3379 | @item cpp-macro-cont |
6b61353c KH |
3380 | All lines inside multiline preprocessor macros if |
3381 | @code{c-syntactic-indentation-in-macros} is @code{nil}. | |
d7bd46ed GM |
3382 | @item friend |
3383 | A C++ friend declaration. | |
3384 | @item objc-method-intro | |
6b61353c | 3385 | The first line of an Objective-C method definition. |
d7bd46ed | 3386 | @item objc-method-args-cont |
6b61353c | 3387 | Lines continuing an Objective-C method definition. |
d7bd46ed GM |
3388 | @item objc-method-call-cont |
3389 | Lines continuing an Objective-C method call. | |
3390 | @item extern-lang-open | |
6b61353c | 3391 | Brace that opens an @code{extern} block (e.g. @code{extern "C" @{...@}}). |
d7bd46ed | 3392 | @item extern-lang-close |
6b61353c | 3393 | Brace that closes an @code{extern} block. |
d7bd46ed | 3394 | @item inextern-lang |
6b61353c KH |
3395 | Analogous to @code{inclass} syntactic symbol, but used inside |
3396 | @code{extern} blocks. | |
d7bd46ed | 3397 | @item namespace-open |
6b61353c KH |
3398 | @itemx namespace-close |
3399 | @itemx innamespace | |
3400 | These are analogous to the three @code{extern-lang} symbols above, but | |
3401 | are returned for C++ namespace blocks. | |
3402 | @item module-open | |
3403 | @itemx module-close | |
3404 | @itemx inmodule | |
3405 | Analogous to the above, but for CORBA IDL @code{module} blocks. | |
3406 | @item composition-open | |
3407 | @itemx composition-close | |
3408 | @itemx incomposition | |
3409 | Analogous to the above, but for CORBA CIDL @code{composition} blocks. | |
d7bd46ed GM |
3410 | @item template-args-cont |
3411 | C++ template argument list continuations. | |
3412 | @item inlambda | |
3413 | Analogous to @code{inclass} syntactic symbol, but used inside lambda | |
3414 | (i.e. anonymous) functions. Only used in Pike mode. | |
3415 | @item lambda-intro-cont | |
3416 | Lines continuing the header of a lambda function, i.e. between the | |
3417 | @code{lambda} keyword and the function body. Only used in Pike mode. | |
3418 | @item inexpr-statement | |
3419 | A statement block inside an expression. The gcc C extension of this is | |
3420 | recognized. It's also used for the special functions that takes a | |
3421 | statement block as an argument in Pike. | |
3422 | @item inexpr-class | |
3423 | A class definition inside an expression. This is used for anonymous | |
3424 | classes in Java. It's also used for anonymous array initializers in | |
3425 | Java. | |
3426 | @end table | |
6bf7aab6 | 3427 | |
6b61353c KH |
3428 | @ssindex -open symbols |
3429 | @ssindex -close symbols | |
6bf7aab6 DL |
3430 | Most syntactic symbol names follow a general naming convention. When a |
3431 | line begins with an open or close brace, the syntactic symbol will | |
3432 | contain the suffix @code{-open} or @code{-close} respectively. | |
3433 | ||
6b61353c KH |
3434 | @ssindex -intro symbols |
3435 | @ssindex -cont symbols | |
3436 | @ssindex -block-intro symbols | |
6bf7aab6 DL |
3437 | Usually, a distinction is made between the first line that introduces a |
3438 | construct and lines that continue a construct, and the syntactic symbols | |
3439 | that represent these lines will contain the suffix @code{-intro} or | |
3440 | @code{-cont} respectively. As a sub-classification of this scheme, a | |
3441 | line which is the first of a particular brace block construct will | |
3442 | contain the suffix @code{-block-intro}. | |
3443 | ||
6bf7aab6 DL |
3444 | Let's look at some examples to understand how this works. Remember that |
3445 | you can check the syntax of any line by using @kbd{C-c C-s}. | |
6bf7aab6 | 3446 | |
6b61353c KH |
3447 | @example |
3448 | 1: void | |
3449 | 2: swap( int& a, int& b ) | |
3450 | 3: @{ | |
3451 | 4: int tmp = a; | |
3452 | 5: a = b; | |
3453 | 6: b = tmp; | |
3454 | 7: int ignored = | |
3455 | 8: a + b; | |
3456 | 9: @} | |
6bf7aab6 DL |
3457 | @end example |
3458 | ||
6b61353c KH |
3459 | @ssindex topmost-intro |
3460 | @ssindex topmost-intro-cont | |
3461 | @ssindex defun-open | |
3462 | @ssindex defun-close | |
3463 | @ssindex defun-block-intro | |
6bf7aab6 DL |
3464 | Line 1 shows a @code{topmost-intro} since it is the first line that |
3465 | introduces a top-level construct. Line 2 is a continuation of the | |
3466 | top-level construct introduction so it has the syntax | |
3467 | @code{topmost-intro-cont}. Line 3 shows a @code{defun-open} since it is | |
d7bd46ed GM |
3468 | the brace that opens a top-level function definition. Line 9 is the |
3469 | corresponding | |
6bf7aab6 DL |
3470 | @code{defun-close} since it contains the brace that closes the top-level |
3471 | function definition. Line 4 is a @code{defun-block-intro}, i.e. it is | |
3472 | the first line of a brace-block, enclosed in a | |
3473 | top-level function definition. | |
3474 | ||
6b61353c KH |
3475 | @ssindex statement |
3476 | @ssindex statement-cont | |
6bf7aab6 DL |
3477 | Lines 5, 6, and 7 are all given @code{statement} syntax since there |
3478 | isn't much special about them. Note however that line 8 is given | |
3479 | @code{statement-cont} syntax since it continues the statement begun | |
3480 | on the previous line. | |
3481 | ||
3482 | Here's another example, which illustrates some C++ class syntactic | |
3483 | symbols: | |
6bf7aab6 | 3484 | |
6b61353c KH |
3485 | @example |
3486 | 1: class Bass | |
3487 | 2: : public Guitar, | |
3488 | 3: public Amplifiable | |
3489 | 4: @{ | |
3490 | 5: public: | |
3491 | 6: Bass() | |
3492 | 7: : eString( new BassString( 0.105 )), | |
3493 | 8: aString( new BassString( 0.085 )), | |
3494 | 9: dString( new BassString( 0.065 )), | |
3495 | 10: gString( new BassString( 0.045 )) | |
3496 | 11: @{ | |
3497 | 12: eString.tune( 'E' ); | |
3498 | 13: aString.tune( 'A' ); | |
3499 | 14: dString.tune( 'D' ); | |
3500 | 15: gString.tune( 'G' ); | |
3501 | 16: @} | |
3502 | 17: friend class Luthier; | |
3503 | 18: @}; | |
6bf7aab6 DL |
3504 | @end example |
3505 | ||
6b61353c KH |
3506 | @ssindex class-open |
3507 | @ssindex class-close | |
6bf7aab6 DL |
3508 | As in the previous example, line 1 has the @code{topmost-intro} syntax. |
3509 | Here however, the brace that opens a C++ class definition on line 4 is | |
3510 | assigned the @code{class-open} syntax. Note that in C++, classes, | |
3511 | structs, and unions are essentially equivalent syntactically (and are | |
3512 | very similar semantically), so replacing the @code{class} keyword in the | |
3513 | example above with @code{struct} or @code{union} would still result in a | |
3514 | syntax of @code{class-open} for line 4 @footnote{This is the case even | |
3515 | for C and Objective-C. For consistency, structs in all supported | |
3516 | languages are syntactically equivalent to classes. Note however that | |
3517 | the keyword @code{class} is meaningless in C and Objective-C.}. | |
3518 | Similarly, line 18 is assigned @code{class-close} syntax. | |
3519 | ||
6b61353c KH |
3520 | @ssindex inher-intro |
3521 | @ssindex inher-cont | |
6bf7aab6 DL |
3522 | Line 2 introduces the inheritance list for the class so it is assigned |
3523 | the @code{inher-intro} syntax, and line 3, which continues the | |
3524 | inheritance list is given @code{inher-cont} syntax. | |
3525 | ||
6b61353c KH |
3526 | @ssindex access-label |
3527 | @ssindex inclass | |
6bf7aab6 DL |
3528 | Hitting @kbd{C-c C-s} on line 5 shows the following analysis: |
3529 | ||
3530 | @example | |
6b61353c | 3531 | ((inclass 58) (access-label 58)) |
6bf7aab6 DL |
3532 | @end example |
3533 | ||
3534 | @noindent | |
3535 | The primary syntactic symbol for this line is @code{access-label} as | |
3536 | this a label keyword that specifies access protection in C++. However, | |
3537 | because this line is also a top-level construct inside a class | |
3538 | definition, the analysis actually shows two syntactic symbols. The | |
3539 | other syntactic symbol assigned to this line is @code{inclass}. | |
3540 | Similarly, line 6 is given both @code{inclass} and @code{topmost-intro} | |
3541 | syntax: | |
3542 | ||
3543 | @example | |
6b61353c | 3544 | ((inclass 58) (topmost-intro 60)) |
6bf7aab6 DL |
3545 | @end example |
3546 | ||
6b61353c KH |
3547 | @ssindex member-init-intro |
3548 | @ssindex member-init-cont | |
6bf7aab6 DL |
3549 | Line 7 introduces a C++ member initialization list and as such is given |
3550 | @code{member-init-intro} syntax. Note that in this case it is | |
3551 | @emph{not} assigned @code{inclass} since this is not considered a | |
3552 | top-level construct. Lines 8 through 10 are all assigned | |
3553 | @code{member-init-cont} since they continue the member initialization | |
3554 | list started on line 7. | |
3555 | ||
3556 | @cindex in-class inline methods | |
6b61353c KH |
3557 | @ssindex inline-open |
3558 | @ssindex inline-close | |
6bf7aab6 DL |
3559 | Line 11's analysis is a bit more complicated: |
3560 | ||
3561 | @example | |
6b61353c | 3562 | ((inclass 58) (inline-open)) |
6bf7aab6 DL |
3563 | @end example |
3564 | ||
3565 | This line is assigned a syntax of both @code{inline-open} and | |
3566 | @code{inclass} because it opens an @dfn{in-class} C++ inline method | |
3567 | definition. This is distinct from, but related to, the C++ notion of an | |
3568 | inline function in that its definition occurs inside an enclosing class | |
3569 | definition, which in C++ implies that the function should be inlined. | |
6b61353c | 3570 | However, if the definition of the @code{Bass} constructor appeared |
6bf7aab6 DL |
3571 | outside the class definition, the construct would be given the |
3572 | @code{defun-open} syntax, even if the keyword @code{inline} appeared | |
3573 | before the method name, as in: | |
6bf7aab6 | 3574 | |
6b61353c KH |
3575 | @example |
3576 | 1: class Bass | |
3577 | 2: : public Guitar, | |
3578 | 3: public Amplifiable | |
3579 | 4: @{ | |
3580 | 5: public: | |
3581 | 6: Bass(); | |
3582 | 7: @}; | |
3583 | 8: | |
3584 | 9: inline | |
3585 | 10: Bass::Bass() | |
3586 | 11: : eString( new BassString( 0.105 )), | |
3587 | 12: aString( new BassString( 0.085 )), | |
3588 | 13: dString( new BassString( 0.065 )), | |
3589 | 14: gString( new BassString( 0.045 )) | |
3590 | 15: @{ | |
3591 | 16: eString.tune( 'E' ); | |
3592 | 17: aString.tune( 'A' ); | |
3593 | 18: dString.tune( 'D' ); | |
3594 | 19: gString.tune( 'G' ); | |
3595 | 20: @} | |
6bf7aab6 DL |
3596 | @end example |
3597 | ||
6b61353c | 3598 | @ssindex friend |
6bf7aab6 DL |
3599 | Returning to the previous example, line 16 is given @code{inline-close} |
3600 | syntax, while line 12 is given @code{defun-block-open} syntax, and lines | |
3601 | 13 through 15 are all given @code{statement} syntax. Line 17 is | |
3602 | interesting in that its syntactic analysis list contains three | |
3603 | elements: | |
3604 | ||
3605 | @example | |
6b61353c | 3606 | ((inclass 58) (topmost-intro 380) (friend)) |
6bf7aab6 DL |
3607 | @end example |
3608 | ||
3609 | The @code{friend} syntactic symbol is a modifier that typically does not | |
3610 | have a relative buffer position. | |
3611 | ||
3612 | Template definitions introduce yet another syntactic symbol: | |
3613 | ||
3614 | @example | |
6b61353c KH |
3615 | 1: ThingManager <int, |
3616 | 2: Framework::Callback *, | |
3617 | 3: Mutex> framework_callbacks; | |
6bf7aab6 DL |
3618 | @end example |
3619 | ||
3620 | Here, line 1 is analyzed as a @code{topmost-intro}, but lines 2 and 3 | |
3621 | are both analyzed as @code{template-args-cont} lines. | |
3622 | ||
3623 | Here is another (totally contrived) example which illustrates how syntax | |
3624 | is assigned to various conditional constructs: | |
6bf7aab6 | 3625 | |
6b61353c KH |
3626 | @example |
3627 | 1: void spam( int index ) | |
3628 | 2: @{ | |
3629 | 3: for( int i=0; i<index; i++ ) | |
3630 | 4: @{ | |
3631 | 5: if( i == 10 ) | |
3632 | 6: do_something_special(); | |
3633 | 7: else | |
3634 | 8: silly_label: | |
3635 | 9: do_something( i ); | |
3636 | 10: @} | |
3637 | 11: do @{ | |
3638 | 12: another_thing( i-- ); | |
3639 | 13: @} | |
3640 | 14: while( i > 0 ); | |
3641 | 15: @} | |
6bf7aab6 DL |
3642 | @end example |
3643 | ||
6bf7aab6 DL |
3644 | Only the lines that illustrate new syntactic symbols will be discussed. |
3645 | ||
6b61353c KH |
3646 | @ssindex substatement-open |
3647 | @ssindex substatement-block-intro | |
3648 | @ssindex block-close | |
6bf7aab6 DL |
3649 | Line 4 has a brace which opens a conditional's substatement block. It |
3650 | is thus assigned @code{substatement-open} syntax, and since line 5 is | |
3651 | the first line in the substatement block, it is assigned | |
6b61353c KH |
3652 | @code{substatement-block-intro} syntax. Line 10 contains the brace that |
3653 | closes the inner substatement block, and is therefore given the syntax | |
3654 | @code{block-close}. Line 13 is treated the same way. | |
3655 | ||
3656 | @ssindex substatement | |
3657 | Lines 6 and 9 are also substatements of conditionals, but since they | |
3658 | don't start blocks they are given @code{substatement} syntax | |
3659 | instead of @code{substatement-open}. | |
3660 | ||
3661 | @ssindex substatement-label | |
3662 | Line 8 contains a label, which is normally given @code{label} syntax. | |
3663 | This one is however a bit special since it's between a conditional and | |
3664 | its substatement. It's analyzed as @code{substatement-label} to let you | |
3665 | handle this rather odd case differently from normal labels. | |
3666 | ||
3667 | @ssindex else-clause | |
3668 | @ssindex catch-clause | |
3669 | Line 7 start with an @code{else} that matches the @code{if} statement on | |
3670 | line 5. It is therefore given the @code{else-clause} syntax and is | |
3671 | anchored on the matching @code{if}. The @code{try}-@code{catch} | |
3672 | constructs in C++ and Java are treated this way too, except that | |
3673 | @code{catch} and (in Java) @code{finally}, are marked with | |
3674 | @code{catch-clause}. | |
3675 | ||
3676 | @ssindex do-while-closure | |
3677 | The @code{while} construct on line 14 that closes a @code{do} | |
3678 | conditional is given the special syntax @code{do-while-closure} if it | |
3679 | appears on a line by itself. Note that if the @code{while} appeared on | |
3680 | the same line as the preceding close brace, that line would still have | |
3681 | @code{block-close} syntax. | |
6bf7aab6 DL |
3682 | |
3683 | Switch statements have their own set of syntactic symbols. Here's an | |
3684 | example: | |
6bf7aab6 | 3685 | |
6b61353c KH |
3686 | @example |
3687 | 1: void spam( enum Ingredient i ) | |
3688 | 2: @{ | |
3689 | 3: switch( i ) @{ | |
3690 | 4: case Ham: | |
3691 | 5: be_a_pig(); | |
3692 | 6: break; | |
3693 | 7: case Salt: | |
3694 | 8: drink_some_water(); | |
3695 | 9: break; | |
3696 | 10: default: | |
3697 | 11: @{ | |
3698 | 12: what_is_it(); | |
3699 | 13: break; | |
3700 | 14: @} | |
3701 | 15: @} | |
3702 | 14: @} | |
6bf7aab6 DL |
3703 | @end example |
3704 | ||
6b61353c KH |
3705 | @ssindex case-label |
3706 | @ssindex statement-case-intro | |
3707 | @ssindex statement-case-open | |
6bf7aab6 DL |
3708 | Here, lines 4, 7, and 10 are all assigned @code{case-label} syntax, |
3709 | while lines 5 and 8 are assigned @code{statement-case-intro}. Line 11 | |
3710 | is treated slightly differently since it contains a brace that opens a | |
3711 | block --- it is given @code{statement-case-open} syntax. | |
3712 | ||
3713 | @cindex brace lists | |
3714 | There are a set of syntactic symbols that are used to recognize | |
3715 | constructs inside of brace lists. A brace list is defined as an | |
3716 | @code{enum} or aggregate initializer list, such as might statically | |
d7bd46ed GM |
3717 | initialize an array of structs. The three special aggregate constructs |
3718 | in Pike, @code{(@{ @})}, @code{([ ])} and @code{(< >)}, are treated as | |
3719 | brace lists too. An example: | |
6bf7aab6 | 3720 | |
6b61353c KH |
3721 | @example |
3722 | 1: static char* ingredients[] = | |
3723 | 2: @{ | |
3724 | 3: "Ham", | |
3725 | 4: "Salt", | |
3726 | 5: NULL | |
3727 | 6: @}; | |
6bf7aab6 DL |
3728 | @end example |
3729 | ||
6b61353c KH |
3730 | @ssindex brace-list-open |
3731 | @ssindex brace-list-intro | |
3732 | @ssindex brace-list-close | |
3733 | @ssindex brace-list-entry | |
6bf7aab6 DL |
3734 | Following convention, line 2 in this example is assigned |
3735 | @code{brace-list-open} syntax, and line 3 is assigned | |
3736 | @code{brace-list-intro} syntax. Likewise, line 6 is assigned | |
3737 | @code{brace-list-close} syntax. Lines 4 and 5 however, are assigned | |
3738 | @code{brace-list-entry} syntax, as would all subsequent lines in this | |
3739 | initializer list. | |
3740 | ||
6b61353c | 3741 | @ssindex brace-entry-open |
d7bd46ed GM |
3742 | Your static initializer might be initializing nested structures, for |
3743 | example: | |
d7bd46ed | 3744 | |
6b61353c KH |
3745 | @example |
3746 | 1: struct intpairs[] = | |
3747 | 2: @{ | |
3748 | 3: @{ 1, 2 @}, | |
3749 | 4: @{ | |
3750 | 5: 3, | |
3751 | 6: 4 | |
3752 | 7: @} | |
3753 | 8: @{ 1, | |
3754 | 9: 2 @}, | |
3755 | 10: @{ 3, 4 @} | |
3756 | 11: @}; | |
d7bd46ed GM |
3757 | @end example |
3758 | ||
3759 | Here, you've already seen the analysis of lines 1, 2, 3, and 11. On | |
3760 | line 4, things get interesting; this line is assigned | |
3761 | @code{brace-entry-open} syntactic symbol because it's a bracelist entry | |
3762 | line that starts with an open brace. Lines 5 and 6 (and line 9) are | |
3763 | pretty standard, and line 7 is a @code{brace-list-close} as you'd | |
3764 | expect. Once again, line 8 is assigned as @code{brace-entry-open} as is | |
3765 | line 10. | |
3766 | ||
6bf7aab6 DL |
3767 | External language definition blocks also have their own syntactic |
3768 | symbols. In this example: | |
6bf7aab6 | 3769 | |
6b61353c KH |
3770 | @example |
3771 | 1: extern "C" | |
3772 | 2: @{ | |
3773 | 3: int thing_one( int ); | |
3774 | 4: int thing_two( double ); | |
3775 | 5: @} | |
6bf7aab6 DL |
3776 | @end example |
3777 | ||
6b61353c KH |
3778 | @ssindex extern-lang-open |
3779 | @ssindex extern-lang-close | |
3780 | @ssindex inextern-lang | |
3781 | @ssindex inclass | |
6bf7aab6 DL |
3782 | @noindent |
3783 | line 2 is given the @code{extern-lang-open} syntax, while line 5 is given | |
3784 | the @code{extern-lang-close} syntax. The analysis for line 3 yields: | |
6bf7aab6 | 3785 | |
6bf7aab6 | 3786 | @example |
6b61353c | 3787 | ((inextern-lang) (topmost-intro 14)) |
6bf7aab6 DL |
3788 | @end example |
3789 | ||
6bf7aab6 | 3790 | @noindent |
6b61353c KH |
3791 | where @code{inextern-lang} is a modifier similar in purpose to |
3792 | @code{inclass}. | |
3793 | ||
3794 | There are various other top level blocks like @code{extern}, and they | |
3795 | are all treated in the same way except that the symbols are named after | |
3796 | the keyword that introduces the block. E.g. C++ namespace blocks get | |
3797 | the three symbols @code{namespace-open}, @code{namespace-close} and | |
3798 | @code{innamespace}. The currently recognized top level blocks are: | |
3799 | ||
3800 | @table @asis | |
3801 | @item @code{extern-lang-open}, @code{extern-lang-close}, @code{inextern-lang} | |
3802 | @code{extern} blocks in C and C++.@footnote{These should logically be | |
3803 | named @code{extern-open}, @code{extern-close} and @code{inextern}, but | |
3804 | that isn't the case for historical reasons.} | |
3805 | ||
3806 | @item @code{namespace-open}, @code{namespace-close}, @code{innamespace} | |
3807 | @ssindex namespace-open | |
3808 | @ssindex namespace-close | |
3809 | @ssindex innamespace | |
3810 | @code{namespace} blocks in C++. | |
3811 | ||
3812 | @item @code{module-open}, @code{module-close}, @code{inmodule} | |
3813 | @ssindex module-open | |
3814 | @ssindex module-close | |
3815 | @ssindex inmodule | |
3816 | @code{module} blocks in CORBA IDL. | |
3817 | ||
3818 | @item @code{composition-open}, @code{composition-close}, @code{incomposition} | |
3819 | @ssindex composition-open | |
3820 | @ssindex composition-close | |
3821 | @ssindex incomposition | |
3822 | @code{composition} blocks in CORBA CIDL. | |
3823 | @end table | |
6bf7aab6 DL |
3824 | |
3825 | A number of syntactic symbols are associated with parenthesis lists, | |
3826 | a.k.a argument lists, as found in function declarations and function | |
3827 | calls. This example illustrates these: | |
6bf7aab6 | 3828 | |
6b61353c KH |
3829 | @example |
3830 | 1: void a_function( int line1, | |
3831 | 2: int line2 ); | |
3832 | 3: | |
3833 | 4: void a_longer_function( | |
3834 | 5: int line1, | |
3835 | 6: int line2 | |
3836 | 7: ); | |
3837 | 8: | |
3838 | 9: void call_them( int line1, int line2 ) | |
3839 | 10: @{ | |
3840 | 11: a_function( | |
3841 | 12: line1, | |
3842 | 13: line2 | |
3843 | 14: ); | |
3844 | 15: | |
3845 | 16: a_longer_function( line1, | |
3846 | 17: line2 ); | |
3847 | 18: @} | |
6bf7aab6 DL |
3848 | @end example |
3849 | ||
6b61353c KH |
3850 | @ssindex arglist-intro |
3851 | @ssindex arglist-close | |
6bf7aab6 DL |
3852 | Lines 5 and 12 are assigned @code{arglist-intro} syntax since they are |
3853 | the first line following the open parenthesis, and lines 7 and 14 are | |
3854 | assigned @code{arglist-close} syntax since they contain the parenthesis | |
3855 | that closes the argument list. | |
3856 | ||
6b61353c KH |
3857 | @ssindex arglist-cont-nonempty |
3858 | @ssindex arglist-cont | |
6bf7aab6 DL |
3859 | Lines that continue argument lists can be assigned one of two syntactic |
3860 | symbols. For example, Lines 2 and 17 | |
3861 | are assigned @code{arglist-cont-nonempty} syntax. What this means | |
3862 | is that they continue an argument list, but that the line containing the | |
3863 | parenthesis that opens the list is @emph{not empty} following the open | |
3864 | parenthesis. Contrast this against lines 6 and 13 which are assigned | |
3865 | @code{arglist-cont} syntax. This is because the parenthesis that opens | |
3866 | their argument lists is the last character on that line. | |
3867 | ||
3868 | Note that there is no @code{arglist-open} syntax. This is because any | |
3869 | parenthesis that opens an argument list, appearing on a separate line, | |
3870 | is assigned the @code{statement-cont} syntax instead. | |
3871 | ||
3872 | A few miscellaneous syntactic symbols that haven't been previously | |
3873 | covered are illustrated by this C++ example: | |
6bf7aab6 | 3874 | |
6b61353c KH |
3875 | @example |
3876 | 1: void Bass::play( int volume ) | |
3877 | 2: const | |
3878 | 3: @{ | |
3879 | 4: /* this line starts a multiline | |
3880 | 5: * comment. This line should get `c' syntax */ | |
3881 | 6: | |
3882 | 7: char* a_multiline_string = "This line starts a multiline \ | |
3883 | 8: string. This line should get `string' syntax."; | |
3884 | 9: | |
3885 | 10: note: | |
3886 | 11: @{ | |
3887 | 12: #ifdef LOCK | |
3888 | 13: Lock acquire(); | |
3889 | 14: #endif // LOCK | |
3890 | 15: slap_pop(); | |
3891 | 16: cout << "I played " | |
3892 | 17: << "a note\n"; | |
3893 | 18: @} | |
3894 | 19: @} | |
6bf7aab6 DL |
3895 | @end example |
3896 | ||
6bf7aab6 DL |
3897 | The lines to note in this example include: |
3898 | ||
3899 | @itemize @bullet | |
6bf7aab6 | 3900 | @item |
6b61353c | 3901 | @ssindex func-decl-cont |
f214c025 | 3902 | Line 2 is assigned the @code{func-decl-cont} syntax. |
6bf7aab6 | 3903 | |
6bf7aab6 | 3904 | @item |
6b61353c | 3905 | @ssindex comment-intro |
f214c025 GM |
3906 | Line 4 is assigned both @code{defun-block-intro} @emph{and} |
3907 | @code{comment-intro} syntax. | |
6bf7aab6 | 3908 | |
6bf7aab6 | 3909 | @item |
6b61353c | 3910 | @ssindex c |
f214c025 | 3911 | Line 5 is assigned @code{c} syntax. |
6bf7aab6 DL |
3912 | |
3913 | @item | |
3914 | @cindex syntactic whitespace | |
f214c025 | 3915 | Line 6 which, even though it contains nothing but whitespace, is |
6bf7aab6 DL |
3916 | assigned @code{defun-block-intro}. Note that the appearance of the |
3917 | comment on lines 4 and 5 do not cause line 6 to be assigned | |
3918 | @code{statement} syntax because comments are considered to be | |
3919 | @dfn{syntactic whitespace}, which are ignored when analyzing | |
f214c025 | 3920 | code. |
6bf7aab6 | 3921 | |
6bf7aab6 | 3922 | @item |
6b61353c | 3923 | @ssindex string |
f214c025 | 3924 | Line 8 is assigned @code{string} syntax. |
6bf7aab6 | 3925 | |
6bf7aab6 | 3926 | @item |
6b61353c | 3927 | @ssindex label |
f214c025 | 3928 | Line 10 is assigned @code{label} syntax. |
6bf7aab6 | 3929 | |
6bf7aab6 | 3930 | @item |
6b61353c | 3931 | @ssindex block-open |
f214c025 | 3932 | Line 11 is assigned @code{block-open} syntax. |
6bf7aab6 | 3933 | |
6bf7aab6 | 3934 | @item |
6b61353c | 3935 | @ssindex cpp-macro |
f214c025 GM |
3936 | Lines 12 and 14 are assigned @code{cpp-macro} syntax in addition to the |
3937 | normal syntactic symbols (@code{statement-block-intro} and | |
3938 | @code{statement}, respectively). Normally @code{cpp-macro} is | |
3939 | configured to cancel out the normal syntactic context to make all | |
3940 | preprocessor directives stick to the first column, but that's easily | |
3941 | changed if you want preprocessor directives to be indented like the rest | |
3942 | of the code. | |
6bf7aab6 | 3943 | |
6bf7aab6 | 3944 | @item |
6b61353c | 3945 | @ssindex stream-op |
f214c025 | 3946 | Line 17 is assigned @code{stream-op} syntax. |
6bf7aab6 DL |
3947 | @end itemize |
3948 | ||
6b61353c | 3949 | @cindex multiline macros |
6bf7aab6 | 3950 | @cindex syntactic whitespace |
6b61353c KH |
3951 | @ssindex cpp-define-intro |
3952 | Multiline preprocessor macro definitions are normally handled just like | |
3953 | other code, i.e. the lines inside them are indented according to the | |
3954 | syntactic analysis of the preceding lines inside the macro. The first | |
3955 | line inside a macro definition (i.e. the line after the starting line of | |
3956 | the cpp directive itself) gets @code{cpp-define-intro}. In this example: | |
6bf7aab6 | 3957 | |
6b61353c KH |
3958 | @example |
3959 | 1: #define LIST_LOOP(cons, listp) \ | |
3960 | 2: for (cons = listp; !NILP (cons); cons = XCDR (cons)) \ | |
3961 | 3: if (!CONSP (cons)) \ | |
3962 | 4: signal_error ("Invalid list format", listp); \ | |
3963 | 5: else | |
6bf7aab6 | 3964 | @end example |
6b61353c | 3965 | |
6bf7aab6 | 3966 | @noindent |
6b61353c KH |
3967 | line 1 is given the syntactic symbol @code{cpp-macro}. The first line |
3968 | of a cpp directive is always given that symbol. Line 2 is given | |
3969 | @code{cpp-define-intro}, so that you can give the macro body as a whole | |
3970 | some extra indentation. Lines 3 through 5 are then analyzed as normal | |
3971 | code, i.e. @code{substatement} on lines 3 and 4, and @code{else-clause} | |
3972 | on line 5. | |
3973 | ||
3974 | The syntactic analysis inside macros can be turned off with | |
3975 | @code{c-syntactic-indentation-in-macros}. In that case, lines 2 through | |
3976 | 5 would all be given @code{cpp-macro-cont} with a relative buffer | |
3977 | position pointing to the @code{#} which starts the cpp | |
3978 | directive@footnote{This is how @ccmode{} 5.28 and earlier analyzed | |
3979 | macros.}. | |
3980 | ||
3981 | @xref{Macro Handling}, for more info about the treatment of macros. | |
6bf7aab6 DL |
3982 | |
3983 | In Objective-C buffers, there are three additional syntactic symbols | |
3984 | assigned to various message calling constructs. Here's an example | |
3985 | illustrating these: | |
6bf7aab6 | 3986 | |
6b61353c KH |
3987 | @example |
3988 | 1: - (void)setDelegate:anObject | |
3989 | 2: withStuff:stuff | |
3990 | 3: @{ | |
3991 | 4: [delegate masterWillRebind:self | |
3992 | 5: toDelegate:anObject | |
3993 | 6: withExtraStuff:stuff]; | |
3994 | 7: @} | |
6bf7aab6 DL |
3995 | @end example |
3996 | ||
6b61353c KH |
3997 | @ssindex objc-method-intro |
3998 | @ssindex objc-method-args-cont | |
3999 | @ssindex objc-method-call-cont | |
6bf7aab6 DL |
4000 | Here, line 1 is assigned @code{objc-method-intro} syntax, and line 2 is |
4001 | assigned @code{objc-method-args-cont} syntax. Lines 5 and 6 are both | |
4002 | assigned @code{objc-method-call-cont} syntax. | |
4003 | ||
d7bd46ed GM |
4004 | Java has a concept of anonymous classes, which may look something like |
4005 | this: | |
d7bd46ed | 4006 | |
6b61353c KH |
4007 | @example |
4008 | 1: public void watch(Observable o) @{ | |
4009 | 2: o.addObserver(new Observer() @{ | |
4010 | 3: public void update(Observable o, Object arg) @{ | |
4011 | 4: history.addElement(arg); | |
4012 | 5: @} | |
4013 | 6: @}); | |
4014 | 7: @} | |
d7bd46ed GM |
4015 | @end example |
4016 | ||
6b61353c | 4017 | @ssindex inexpr-class |
d7bd46ed GM |
4018 | The brace following the @code{new} operator opens the anonymous class. |
4019 | Lines 3 and 6 are assigned the @code{inexpr-class} syntax, besides the | |
4020 | @code{inclass} symbol used in normal classes. Thus, the class will be | |
4021 | indented just like a normal class, with the added indentation given to | |
4022 | @code{inexpr-class}. | |
4023 | ||
4024 | There are a few occasions where a statement block may be used inside an | |
4025 | expression. One is in C code using the gcc extension for this, e.g: | |
d7bd46ed | 4026 | |
6b61353c KH |
4027 | @example |
4028 | 1: int res = (@{ | |
4029 | 2: int y = foo (); int z; | |
4030 | 3: if (y > 0) z = y; else z = - y; | |
4031 | 4: z; | |
4032 | 5: @}); | |
d7bd46ed GM |
4033 | @end example |
4034 | ||
6b61353c | 4035 | @ssindex inexpr-statement |
d7bd46ed GM |
4036 | Lines 2 and 5 get the @code{inexpr-statement} syntax, besides the |
4037 | symbols they'd get in a normal block. Therefore, the indentation put on | |
4038 | @code{inexpr-statement} is added to the normal statement block | |
4039 | indentation. | |
4040 | ||
4041 | In Pike code, there are a few other situations where blocks occur inside | |
4042 | statements, as illustrated here: | |
d7bd46ed | 4043 | |
6b61353c KH |
4044 | @example |
4045 | 1: array itgob() | |
4046 | 2: @{ | |
4047 | 3: string s = map (backtrace()[-2][3..], | |
4048 | 4: lambda | |
4049 | 5: (mixed arg) | |
4050 | 6: @{ | |
4051 | 7: return sprintf ("%t", arg); | |
4052 | 8: @}) * ", " + "\n"; | |
4053 | 9: return catch @{ | |
4054 | 10: write (s + "\n"); | |
4055 | 11: @}; | |
4056 | 12: @} | |
d7bd46ed GM |
4057 | @end example |
4058 | ||
6b61353c KH |
4059 | @ssindex inlambda |
4060 | @ssindex lambda-intro-cont | |
d7bd46ed GM |
4061 | Lines 4 through 8 contain a lambda function, which @ccmode{} recognizes |
4062 | by the @code{lambda} keyword. If the function argument list is put | |
4063 | on a line of its own, as in line 5, it gets the @code{lambda-intro-cont} | |
4064 | syntax. The function body is handled as an inline method body, with the | |
4065 | addition of the @code{inlambda} syntactic symbol. This means that line | |
4066 | 6 gets @code{inlambda} and @code{inline-open}, and line 8 gets | |
4067 | @code{inline-close}@footnote{You might wonder why it doesn't get | |
4068 | @code{inlambda} too. It's because the closing brace is relative to the | |
4069 | opening brace, which stands on its own line in this example. If the | |
4070 | opening brace was hanging on the previous line, then the closing brace | |
4071 | would get the @code{inlambda} syntax too to be indented correctly.}. | |
4072 | ||
6b61353c | 4073 | @ssindex inexpr-statement |
d7bd46ed GM |
4074 | On line 9, @code{catch} is a special function taking a statement block |
4075 | as its argument. The block is handled as an in-expression statement | |
4076 | with the @code{inexpr-statement} syntax, just like the gcc extended C | |
4077 | example above. The other similar special function, @code{gauge}, is | |
4078 | handled like this too. | |
4079 | ||
6b61353c KH |
4080 | @ssindex knr-argdecl-intro |
4081 | @ssindex knr-argdecl | |
6bf7aab6 DL |
4082 | Two other syntactic symbols can appear in old style, non-prototyped C |
4083 | code @footnote{a.k.a. K&R C, or Kernighan & Ritchie C}: | |
6bf7aab6 | 4084 | |
6b61353c KH |
4085 | @example |
4086 | 1: int add_three_integers(a, b, c) | |
4087 | 2: int a; | |
4088 | 3: int b; | |
4089 | 4: int c; | |
4090 | 5: @{ | |
4091 | 6: return a + b + c; | |
4092 | 7: @} | |
6bf7aab6 DL |
4093 | @end example |
4094 | ||
4095 | Here, line 2 is the first line in an argument declaration list and so is | |
4096 | given the @code{knr-argdecl-intro} syntactic symbol. Subsequent lines | |
4097 | (i.e. lines 3 and 4 in this example), are given @code{knr-argdecl} | |
4098 | syntax. | |
4099 | ||
d7bd46ed | 4100 | |
6bf7aab6 | 4101 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
6b61353c | 4102 | @node Indentation Functions, AWK Mode, Syntactic Symbols, Top |
d7bd46ed | 4103 | @comment node-name, next, previous, up |
6b61353c | 4104 | @chapter Indentation Functions |
d7bd46ed GM |
4105 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
4106 | ||
6b61353c KH |
4107 | @cindex indentation function |
4108 | @cindex line-up function | |
4109 | Often there are cases when a simple offset setting on a syntactic | |
4110 | symbol isn't enough to get the desired indentation. Therefore, it's | |
4111 | also possible to use an @dfn{indentation function} (a.k.a. @dfn{line-up | |
4112 | function}) for a syntactic symbol. | |
d7bd46ed GM |
4113 | |
4114 | @ccmode{} comes with many predefined indentation functions for common | |
4115 | situations. If none of these does what you want, you can write your | |
4116 | own, see @ref{Custom Indentation Functions}. If you do, it's probably a | |
4117 | good idea to start working from one of these predefined functions, they | |
4118 | can be found in the file @file{cc-align.el}. | |
4119 | ||
4120 | For every function below there is a ``works with'' list that indicates | |
4121 | which syntactic symbols the function is intended to be used with. | |
4122 | ||
4123 | @macro workswith | |
cb7f2e96 | 4124 | @emph{Works with:@ } |
d7bd46ed GM |
4125 | @end macro |
4126 | @ifinfo | |
4127 | @unmacro workswith | |
4128 | @macro workswith | |
4129 | Works with: | |
4130 | @end macro | |
4131 | @end ifinfo | |
4132 | ||
6b61353c KH |
4133 | @macro sssTBasicOffset |
4134 | <--> @i{c-basic-offset}@c | |
4135 | @end macro | |
d7bd46ed | 4136 | |
6b61353c KH |
4137 | @macro sssTsssTBasicOffset |
4138 | <--><--> @i{c-basic-offset}@c | |
4139 | @end macro | |
d7bd46ed | 4140 | |
6b61353c KH |
4141 | @macro hereFn{func} |
4142 | <- @i{\func\}@c | |
4143 | @end macro | |
d7bd46ed | 4144 | |
6b61353c KH |
4145 | @c The TeX backend seems to insert extra spaces around the argument. :P |
4146 | @iftex | |
4147 | @unmacro hereFn | |
4148 | @macro hereFn{func} | |
4149 | <-@i{\func\}@c | |
4150 | @end macro | |
4151 | @end iftex | |
d7bd46ed | 4152 | |
6b61353c | 4153 | @comment ------------------------------------------------------------ |
d7bd46ed | 4154 | |
6b61353c KH |
4155 | @defun c-indent-one-line-block |
4156 | @findex indent-one-line-block (c-) | |
4157 | Indent a one line block @code{c-basic-offset} extra. E.g: | |
d7bd46ed | 4158 | |
d7bd46ed GM |
4159 | @example |
4160 | @group | |
6b61353c KH |
4161 | if (n > 0) |
4162 | @{m+=n; n=0;@} @hereFn{c-indent-one-line-block} | |
4163 | @sssTBasicOffset{} | |
d7bd46ed GM |
4164 | @end group |
4165 | @end example | |
6b61353c | 4166 | |
d7bd46ed GM |
4167 | @noindent |
4168 | and | |
6b61353c | 4169 | |
d7bd46ed GM |
4170 | @example |
4171 | @group | |
6b61353c KH |
4172 | if (n > 0) |
4173 | @{ @hereFn{c-indent-one-line-block} | |
4174 | m+=n; n=0; | |
4175 | @} | |
d7bd46ed GM |
4176 | @end group |
4177 | @end example | |
4178 | ||
6b61353c KH |
4179 | The block may be surrounded by any kind of parenthesis characters. |
4180 | @code{nil} is returned if the line doesn't start with a one line block, | |
4181 | which makes the function usable in list expressions. | |
d7bd46ed | 4182 | |
6b61353c KH |
4183 | @workswith Almost all syntactic symbols, but most useful on the |
4184 | @code{-open} symbols. | |
4185 | @end defun | |
d7bd46ed | 4186 | |
6b61353c KH |
4187 | @comment ------------------------------------------------------------ |
4188 | ||
4189 | @defun c-indent-multi-line-block | |
4190 | @findex indent-multi-line-block (c-) | |
4191 | Indent a multiline block @code{c-basic-offset} extra. E.g: | |
d7bd46ed | 4192 | |
f214c025 GM |
4193 | @example |
4194 | @group | |
6b61353c KH |
4195 | int *foo[] = @{ |
4196 | NULL, | |
4197 | @{17@}, @hereFn{c-indent-multi-line-block} | |
f214c025 GM |
4198 | @end group |
4199 | @end example | |
6b61353c | 4200 | |
f214c025 GM |
4201 | @noindent |
4202 | and | |
6b61353c | 4203 | |
f214c025 GM |
4204 | @example |
4205 | @group | |
6b61353c KH |
4206 | int *foo[] = @{ |
4207 | NULL, | |
4208 | @{ @hereFn{c-indent-multi-line-block} | |
4209 | 17 | |
4210 | @}, | |
4211 | @sssTBasicOffset{} | |
4212 | @end group | |
4213 | @end example | |
f214c025 | 4214 | |
6b61353c KH |
4215 | The block may be surrounded by any kind of parenthesis characters. |
4216 | @code{nil} is returned if the line doesn't start with a multiline | |
4217 | block, which makes the function usable in list expressions. | |
4218 | ||
4219 | @workswith Almost all syntactic symbols, but most useful on the | |
4220 | @code{-open} symbols. | |
4221 | @end defun | |
f214c025 | 4222 | |
6b61353c KH |
4223 | @comment ------------------------------------------------------------ |
4224 | ||
4225 | @defun c-lineup-argcont | |
4226 | @findex lineup-argcont (c-) | |
4227 | Line up a continued argument. E.g: | |
4228 | ||
4229 | @example | |
4230 | @group | |
4231 | foo (xyz, aaa + bbb + ccc | |
4232 | + ddd + eee + fff); @hereFn{c-lineup-argcont} | |
f214c025 GM |
4233 | @end group |
4234 | @end example | |
6b61353c KH |
4235 | |
4236 | Only continuation lines like this are touched, @code{nil} is returned on | |
4237 | lines which are the start of an argument. | |
4238 | ||
4239 | Within a gcc @code{asm} block, @code{:} is recognised as an argument | |
4240 | separator, but of course only between operand specifications, not in the | |
4241 | expressions for the operands. | |
4242 | ||
4243 | @workswith @code{arglist-cont}, @code{arglist-cont-nonempty}. | |
4244 | @end defun | |
4245 | ||
4246 | @comment ------------------------------------------------------------ | |
4247 | ||
4248 | @defun c-lineup-arglist | |
4249 | @findex lineup-arglist (c-) | |
4250 | Line up the current argument line under the first argument. | |
4251 | ||
4252 | As a special case, if an argument on the same line as the open | |
4253 | parenthesis starts with a brace block opener, the indentation is | |
4254 | @code{c-basic-offset} only. This is intended as a ``DWIM'' measure in | |
4255 | cases like macros that contains statement blocks, e.g: | |
4256 | ||
f214c025 GM |
4257 | @example |
4258 | @group | |
6b61353c KH |
4259 | A_VERY_LONG_MACRO_NAME (@{ |
4260 | some (code, with + long, lines * in[it]); | |
4261 | @}); | |
4262 | @sssTBasicOffset{} | |
4263 | @end group | |
4264 | @end example | |
f214c025 | 4265 | |
6b61353c KH |
4266 | This is motivated partly because it's more in line with how code |
4267 | blocks are handled, and partly since it approximates the behavior of | |
4268 | earlier CC Mode versions, which due to inaccurate analysis tended to | |
4269 | indent such cases this way. | |
4270 | ||
4271 | @workswith @code{arglist-cont-nonempty}, @code{arglist-close}. | |
4272 | @end defun | |
4273 | ||
4274 | @comment ------------------------------------------------------------ | |
4275 | ||
4276 | @defun c-lineup-arglist-intro-after-paren | |
4277 | @findex lineup-arglist-intro-after-paren (c-) | |
4278 | Line up a line to just after the open paren of the surrounding paren or | |
4279 | brace block. | |
4280 | ||
4281 | @workswith @code{defun-block-intro}, @code{brace-list-intro}, | |
4282 | @code{statement-block-intro}, @code{statement-case-intro}, | |
4283 | @code{arglist-intro}. | |
4284 | @end defun | |
4285 | ||
4286 | @comment ------------------------------------------------------------ | |
4287 | ||
4288 | @defun c-lineup-arglist-close-under-paren | |
4289 | @findex lineup-arglist-close-under-paren (c-) | |
4290 | Set your @code{arglist-close} syntactic symbol to this line-up function | |
4291 | so that parentheses that close argument lists will line up under the | |
4292 | parenthesis that opened the argument list. It can also be used with | |
4293 | @code{arglist-cont} and @code{arglist-cont-nonempty} to line up all | |
4294 | lines inside a parenthesis under the open paren. | |
4295 | ||
4296 | As a special case, if a brace block is opened at the same line as the | |
4297 | open parenthesis of the argument list, the indentation is | |
4298 | @code{c-basic-offset} only. See @code{c-lineup-arglist} for further | |
4299 | discussion of this ``DWIM'' measure. | |
4300 | ||
4301 | @workswith Almost all symbols, but are typically most useful on | |
4302 | @code{arglist-close}, @code{brace-list-close}, @code{arglist-cont} and | |
4303 | @code{arglist-cont-nonempty}. | |
4304 | @end defun | |
4305 | ||
4306 | @comment ------------------------------------------------------------ | |
4307 | ||
4308 | @defun c-lineup-arglist-operators | |
4309 | @findex lineup-arglist-operators (c-) | |
4310 | Line up lines starting with an infix operator under the open paren. | |
4311 | Return @code{nil} on lines that don't start with an operator, to leave | |
4312 | those cases to other lineup functions. Example: | |
f214c025 | 4313 | |
6b61353c KH |
4314 | @example |
4315 | @group | |
4316 | if ( x < 10 | |
4317 | || at_limit (x, @hereFn{c-lineup-arglist-operators} | |
4318 | list) @hereFn{c-lineup-arglist-operators@r{ returns nil}} | |
4319 | ) | |
f214c025 GM |
4320 | @end group |
4321 | @end example | |
4322 | ||
6b61353c KH |
4323 | Since this function doesn't do anything for lines without an infix |
4324 | operator you typically want to use it together with some other lineup | |
4325 | settings, e.g. as follows (the @code{arglist-close} setting is just a | |
4326 | suggestion to get a consistent style): | |
d7bd46ed | 4327 | |
d7bd46ed | 4328 | @example |
6b61353c KH |
4329 | (c-set-offset 'arglist-cont |
4330 | '(c-lineup-arglist-operators 0)) | |
4331 | (c-set-offset 'arglist-cont-nonempty | |
4332 | '(c-lineup-arglist-operators c-lineup-arglist)) | |
4333 | (c-set-offset 'arglist-close | |
4334 | '(c-lineup-arglist-close-under-paren)) | |
4335 | @end example | |
d7bd46ed | 4336 | |
6b61353c KH |
4337 | @workswith @code{arglist-cont}, @code{arglist-cont-nonempty}. |
4338 | @end defun | |
4339 | ||
4340 | @comment ------------------------------------------------------------ | |
d7bd46ed | 4341 | |
6b61353c KH |
4342 | @defun c-lineup-C-comments |
4343 | @findex lineup-C-comments (c-) | |
4344 | Line up C block comment continuation lines. Various heuristics are used | |
4345 | to handle most of the common comment styles. Some examples: | |
d7bd46ed | 4346 | |
6b61353c KH |
4347 | @example |
4348 | @group | |
4349 | /* /** /* | |
4350 | * text * text text | |
4351 | */ */ */ | |
d7bd46ed GM |
4352 | @end group |
4353 | @end example | |
6b61353c | 4354 | |
d7bd46ed GM |
4355 | @example |
4356 | @group | |
6b61353c KH |
4357 | /* text /* /** |
4358 | text ** text ** text | |
4359 | */ */ */ | |
4360 | @end group | |
4361 | @end example | |
d7bd46ed | 4362 | |
6b61353c KH |
4363 | @example |
4364 | @group | |
4365 | /************************************************** | |
4366 | * text | |
4367 | *************************************************/ | |
4368 | @end group | |
4369 | @end example | |
d7bd46ed | 4370 | |
6b61353c KH |
4371 | @vindex comment-start-skip |
4372 | @example | |
4373 | @group | |
4374 | /************************************************** | |
4375 | Free form text comments: | |
4376 | In comments with a long delimiter line at the | |
4377 | start, the indentation is kept unchanged for lines | |
4378 | that start with an empty comment line prefix. The | |
4379 | delimiter line is whatever matches the | |
4380 | @code{comment-start-skip} regexp. | |
4381 | **************************************************/ | |
d7bd46ed GM |
4382 | @end group |
4383 | @end example | |
4384 | ||
6b61353c KH |
4385 | The style variable @code{c-comment-prefix-regexp} is used to recognize |
4386 | the comment line prefix, e.g. the @samp{*} that usually starts every | |
4387 | line inside a comment. | |
4388 | ||
4389 | @workswith The @code{c} syntactic symbol. | |
4390 | @end defun | |
4391 | ||
4392 | @comment ------------------------------------------------------------ | |
4393 | ||
4394 | @defun c-lineup-cascaded-calls | |
4395 | @findex lineup-cascaded-calls (c-) | |
4396 | Line up ``cascaded calls'' under each other. If the line begins with | |
4397 | @code{->} or @code{.} and the preceding line ends with one or more | |
4398 | function calls preceded by the same token, then the arrow is lined up | |
4399 | with the first of those tokens. E.g: | |
d7bd46ed | 4400 | |
d7bd46ed GM |
4401 | @example |
4402 | @group | |
6b61353c KH |
4403 | r = proc->add(17)->add(18) |
4404 | ->add(19) + @hereFn{c-lineup-cascaded-calls} | |
4405 | offset; @hereFn{c-lineup-cascaded-calls@r{ (inactive)}} | |
4406 | @end group | |
4407 | @end example | |
d7bd46ed | 4408 | |
6b61353c KH |
4409 | In any other situation @code{nil} is returned to allow use in list |
4410 | expressions. | |
4411 | ||
4412 | @workswith @code{topmost-intro-cont}, @code{statement-cont}, | |
4413 | @code{arglist-cont}, @code{arglist-cont-nonempty}. | |
4414 | @end defun | |
d7bd46ed | 4415 | |
6b61353c KH |
4416 | @comment ------------------------------------------------------------ |
4417 | ||
4418 | @defun c-lineup-close-paren | |
4419 | @findex lineup-close-paren (c-) | |
4420 | Line up the closing paren under its corresponding open paren if the | |
4421 | open paren is followed by code. If the open paren ends its line, no | |
4422 | indentation is added. E.g: | |
d7bd46ed | 4423 | |
6b61353c KH |
4424 | @example |
4425 | @group | |
4426 | main (int, | |
4427 | char ** | |
4428 | ) @hereFn{c-lineup-close-paren} | |
d7bd46ed GM |
4429 | @end group |
4430 | @end example | |
6b61353c | 4431 | |
d7bd46ed GM |
4432 | @noindent |
4433 | and | |
6b61353c | 4434 | |
d7bd46ed GM |
4435 | @example |
4436 | @group | |
6b61353c KH |
4437 | main ( |
4438 | int, char ** | |
4439 | ) @hereFn{c-lineup-close-paren} | |
4440 | @end group | |
4441 | @end example | |
d7bd46ed | 4442 | |
6b61353c KH |
4443 | As a special case, if a brace block is opened at the same line as the |
4444 | open parenthesis of the argument list, the indentation is | |
4445 | @code{c-basic-offset} instead of the open paren column. See | |
4446 | @code{c-lineup-arglist} for further discussion of this ``DWIM'' measure. | |
4447 | ||
4448 | @workswith All @code{*-close} symbols. | |
4449 | @end defun | |
4450 | ||
4451 | @comment ------------------------------------------------------------ | |
4452 | ||
4453 | @defun c-lineup-comment | |
4454 | @findex lineup-comment (c-) | |
4455 | Line up a comment-only line according to the style variable | |
4456 | @code{c-comment-only-line-offset}. If the comment is lined up with a | |
4457 | comment starter on the previous line, that alignment is preserved. | |
4458 | ||
4459 | @defopt c-comment-only-line-offset | |
4460 | @vindex comment-only-line-offset (c-) | |
4461 | This style variable specifies the extra offset for the line. It can | |
4462 | contain an integer or a cons cell of the form | |
4463 | ||
4464 | @example | |
4465 | (@r{@var{non-anchored-offset}} . @r{@var{anchored-offset}}) | |
4466 | @end example | |
4467 | ||
4468 | @noindent | |
4469 | where @var{non-anchored-offset} is the amount of offset given to | |
4470 | non-column-zero anchored lines, and @var{anchored-offset} is the amount | |
4471 | of offset to give column-zero anchored lines. Just an integer as value | |
4472 | is equivalent to @code{(@r{@var{value}} . -1000)}. | |
4473 | @end defopt | |
d7bd46ed | 4474 | |
6b61353c KH |
4475 | @workswith @code{comment-intro}. |
4476 | @end defun | |
4477 | ||
4478 | @comment ------------------------------------------------------------ | |
4479 | ||
4480 | @defun c-lineup-cpp-define | |
4481 | @findex lineup-cpp-define (c-) | |
4482 | Line up macro continuation lines according to the indentation of the | |
4483 | construct preceding the macro. E.g: | |
4484 | ||
4485 | @example | |
4486 | @group | |
4487 | const char msg[] = @hereFn{@r{The beginning of the preceding construct.}} | |
4488 | \"Some text.\"; | |
4489 | ||
4490 | #define X(A, B) \ | |
4491 | do @{ \ @hereFn{c-lineup-cpp-define} | |
4492 | printf (A, B); \ | |
4493 | @} while (0) | |
d7bd46ed GM |
4494 | @end group |
4495 | @end example | |
4496 | ||
6b61353c KH |
4497 | @noindent |
4498 | and: | |
d7bd46ed | 4499 | |
d7bd46ed GM |
4500 | @example |
4501 | @group | |
6b61353c KH |
4502 | int dribble() @{ |
4503 | if (!running) @hereFn{@r{The beginning of the preceding construct.}} | |
4504 | error(\"Not running!\"); | |
4505 | ||
4506 | #define X(A, B) \ | |
4507 | do @{ \ @hereFn{c-lineup-cpp-define} | |
4508 | printf (A, B); \ | |
4509 | @} while (0) | |
4510 | @end group | |
4511 | @end example | |
d7bd46ed | 4512 | |
6b61353c KH |
4513 | If @code{c-syntactic-indentation-in-macros} is non-@code{nil}, the |
4514 | function returns the relative indentation to the macro start line to | |
4515 | allow accumulation with other offsets. E.g. in the following cases, | |
4516 | @code{cpp-define-intro} is combined with the | |
4517 | @code{statement-block-intro} that comes from the @samp{do @{} that hangs | |
4518 | on the @samp{#define} line: | |
177c0ea7 | 4519 | |
6b61353c KH |
4520 | @example |
4521 | @group | |
4522 | const char msg[] = | |
4523 | \"Some text.\"; | |
d7bd46ed | 4524 | |
6b61353c KH |
4525 | #define X(A, B) do @{ \ |
4526 | printf (A, B); \ @hereFn{c-lineup-cpp-define} | |
4527 | this->refs++; \ | |
4528 | @} while (0) @hereFn{c-lineup-cpp-define} | |
d7bd46ed GM |
4529 | @end group |
4530 | @end example | |
6b61353c | 4531 | |
d7bd46ed | 4532 | @noindent |
6b61353c KH |
4533 | and: |
4534 | ||
d7bd46ed GM |
4535 | @example |
4536 | @group | |
6b61353c KH |
4537 | int dribble() @{ |
4538 | if (!running) | |
4539 | error(\"Not running!\"); | |
4540 | ||
4541 | #define X(A, B) do @{ \ | |
4542 | printf (A, B); \ @hereFn{c-lineup-cpp-define} | |
4543 | this->refs++; \ | |
4544 | @} while (0) @hereFn{c-lineup-cpp-define} | |
4545 | @end group | |
4546 | @end example | |
d7bd46ed | 4547 | |
6b61353c KH |
4548 | The relative indentation returned by @code{c-lineup-cpp-define} is zero |
4549 | and two, respectively, on the two lines in each of these examples. They | |
4550 | are then added to the two column indentation that | |
4551 | @code{statement-block-intro} gives in both cases here. | |
4552 | ||
4553 | If the relative indentation is zero, then @code{nil} is returned | |
4554 | instead. That is useful in a list expression to specify the default | |
4555 | indentation on the top level. | |
4556 | ||
4557 | If @code{c-syntactic-indentation-in-macros} is @code{nil} then this | |
4558 | function keeps the current indentation, except for empty lines (ignoring | |
4559 | the ending backslash) where it takes the indentation from the closest | |
4560 | preceding nonempty line in the macro. If there's no such line in the | |
4561 | macro then the indentation is taken from the construct preceding it, as | |
4562 | described above. | |
4563 | ||
4564 | @workswith @code{cpp-define-intro}. | |
4565 | @end defun | |
4566 | ||
4567 | @comment ------------------------------------------------------------ | |
4568 | ||
4569 | @defun c-lineup-dont-change | |
4570 | @findex lineup-dont-change (c-) | |
4571 | This lineup function makes the line stay at whatever indentation it | |
4572 | already has; think of it as an identity function for lineups. | |
4573 | ||
4574 | @workswith Any syntactic symbol. | |
4575 | @end defun | |
4576 | ||
4577 | @comment ------------------------------------------------------------ | |
4578 | ||
4579 | @defun c-lineup-gcc-asm-reg | |
4580 | @findex lineup-gcc-asm-reg (c-) | |
4581 | Line up a gcc asm register under one on a previous line. | |
d7bd46ed | 4582 | |
6b61353c KH |
4583 | @example |
4584 | @group | |
4585 | asm ("foo %1, %0\n" | |
4586 | "bar %0, %1" | |
4587 | : "=r" (w), | |
4588 | "=r" (x) | |
4589 | : "0" (y), | |
4590 | "1" (z)); | |
d7bd46ed GM |
4591 | @end group |
4592 | @end example | |
4593 | ||
6b61353c KH |
4594 | The @samp{x} line is aligned to the text after the @samp{:} on the |
4595 | @samp{w} line, and similarly @samp{z} under @samp{y}. | |
d7bd46ed | 4596 | |
6b61353c KH |
4597 | This is done only in an @samp{asm} or @samp{__asm__} block, and only to |
4598 | those lines mentioned. Anywhere else @code{nil} is returned. The usual | |
4599 | arrangement is to have this routine as an extra feature at the start of | |
4600 | arglist lineups, e.g. | |
d7bd46ed | 4601 | |
d7bd46ed | 4602 | @example |
6b61353c KH |
4603 | (c-lineup-gcc-asm-reg c-lineup-arglist) |
4604 | @end example | |
d7bd46ed | 4605 | |
6b61353c KH |
4606 | @workswith @code{arglist-cont}, @code{arglist-cont-nonempty}. |
4607 | @end defun | |
4608 | ||
4609 | @comment ------------------------------------------------------------ | |
4610 | ||
4611 | @defun c-lineup-inexpr-block | |
4612 | @findex lineup-inexpr-block (c-) | |
4613 | This can be used with the in-expression block symbols to indent the | |
4614 | whole block to the column where the construct is started. E.g. for Java | |
4615 | anonymous classes, this lines up the class under the @samp{new} keyword, | |
4616 | and in Pike it lines up the lambda function body under the @samp{lambda} | |
4617 | keyword. Returns @code{nil} if the block isn't part of such a | |
4618 | construct. | |
4619 | ||
4620 | @workswith @code{inlambda}, @code{inexpr-statement}, | |
4621 | @code{inexpr-class}. | |
4622 | @end defun | |
4623 | ||
4624 | @comment ------------------------------------------------------------ | |
d7bd46ed | 4625 | |
6b61353c KH |
4626 | @defun c-lineup-java-inher |
4627 | @findex lineup-java-inher (c-) | |
4628 | Line up Java implements and extends declarations. If class names | |
4629 | follow on the same line as the @samp{implements}/@samp{extends} | |
4630 | keyword, they are lined up under each other. Otherwise, they are | |
4631 | indented by adding @code{c-basic-offset} to the column of the keyword. | |
4632 | E.g: | |
4633 | ||
4634 | @example | |
4635 | @group | |
4636 | class Foo | |
4637 | extends | |
4638 | Bar @hereFn{c-lineup-java-inher} | |
4639 | @sssTBasicOffset{} | |
d7bd46ed GM |
4640 | @end group |
4641 | @end example | |
6b61353c | 4642 | |
d7bd46ed GM |
4643 | @noindent |
4644 | and | |
6b61353c | 4645 | |
d7bd46ed GM |
4646 | @example |
4647 | @group | |
6b61353c KH |
4648 | class Foo |
4649 | extends Cyphr, | |
4650 | Bar @hereFn{c-lineup-java-inher} | |
4651 | @end group | |
4652 | @end example | |
d7bd46ed | 4653 | |
6b61353c KH |
4654 | @workswith @code{inher-cont}. |
4655 | @end defun | |
d7bd46ed | 4656 | |
6b61353c | 4657 | @comment ------------------------------------------------------------ |
d7bd46ed | 4658 | |
6b61353c KH |
4659 | @defun c-lineup-java-throws |
4660 | @findex lineup-java-throws (c-) | |
4661 | Line up Java throws declarations. If exception names follow on the | |
4662 | same line as the throws keyword, they are lined up under each other. | |
4663 | Otherwise, they are indented by adding @code{c-basic-offset} to the | |
4664 | column of the @samp{throws} keyword. The @samp{throws} keyword itself | |
4665 | is also indented by @code{c-basic-offset} from the function declaration | |
4666 | start if it doesn't hang. E.g: | |
4667 | ||
4668 | @example | |
4669 | @group | |
4670 | int foo() | |
4671 | throws @hereFn{c-lineup-java-throws} | |
4672 | Bar @hereFn{c-lineup-java-throws} | |
4673 | @sssTsssTBasicOffset{} | |
d7bd46ed GM |
4674 | @end group |
4675 | @end example | |
4676 | ||
6b61353c KH |
4677 | @noindent |
4678 | and | |
d7bd46ed | 4679 | |
d7bd46ed | 4680 | @example |
d7bd46ed | 4681 | @group |
6b61353c KH |
4682 | int foo() throws Cyphr, |
4683 | Bar, @hereFn{c-lineup-java-throws} | |
4684 | Vlod @hereFn{c-lineup-java-throws} | |
d7bd46ed | 4685 | @end group |
6b61353c KH |
4686 | @end example |
4687 | ||
4688 | @workswith @code{func-decl-cont}. | |
4689 | @end defun | |
4690 | ||
4691 | @comment ------------------------------------------------------------ | |
4692 | ||
4693 | @defun c-lineup-knr-region-comment | |
4694 | @findex lineup-knr-region-comment (c-) | |
4695 | Line up a comment in the ``K&R region'' with the declaration. That is | |
4696 | the region between the function or class header and the beginning of the | |
4697 | block. E.g: | |
d7bd46ed | 4698 | |
6b61353c | 4699 | @example |
d7bd46ed | 4700 | @group |
6b61353c KH |
4701 | int main() |
4702 | /* Called at startup. */ @hereFn{c-lineup-knr-region-comment} | |
4703 | @{ | |
4704 | return 0; | |
4705 | @} | |
d7bd46ed | 4706 | @end group |
6b61353c KH |
4707 | @end example |
4708 | ||
4709 | Return @code{nil} if called in any other situation, to be useful in list | |
4710 | expressions. | |
d7bd46ed | 4711 | |
6b61353c KH |
4712 | @workswith @code{comment-intro}. |
4713 | @end defun | |
4714 | ||
4715 | @comment ------------------------------------------------------------ | |
4716 | ||
4717 | @defun c-lineup-math | |
4718 | @findex lineup-math (c-) | |
4719 | Line up the current line to after the equal sign on the first line in the | |
4720 | statement. If there isn't any, indent with @code{c-basic-offset}. If | |
4721 | the current line contains an equal sign too, try to align it with the | |
4722 | first one. | |
4723 | ||
4724 | @workswith @code{topmost-intro-cont}, @code{statement-cont}, | |
4725 | @code{arglist-cont}, @code{arglist-cont-nonempty}. | |
4726 | @end defun | |
4727 | ||
4728 | @comment ------------------------------------------------------------ | |
4729 | ||
4730 | @defun c-lineup-multi-inher | |
4731 | @findex lineup-multi-inher (c-) | |
4732 | Line up the classes in C++ multiple inheritance clauses and member | |
4733 | initializers under each other. E.g: | |
4734 | ||
4735 | @example | |
d7bd46ed | 4736 | @group |
6b61353c KH |
4737 | Foo::Foo (int a, int b): |
4738 | Cyphr (a), | |
4739 | Bar (b) @hereFn{c-lineup-multi-inher} | |
d7bd46ed | 4740 | @end group |
6b61353c | 4741 | @end example |
d7bd46ed | 4742 | |
6b61353c KH |
4743 | @noindent |
4744 | and | |
4745 | ||
4746 | @example | |
d7bd46ed | 4747 | @group |
6b61353c KH |
4748 | class Foo |
4749 | : public Cyphr, | |
4750 | public Bar @hereFn{c-lineup-multi-inher} | |
d7bd46ed | 4751 | @end group |
6b61353c KH |
4752 | @end example |
4753 | ||
4754 | @noindent | |
4755 | and | |
d7bd46ed | 4756 | |
6b61353c KH |
4757 | @example |
4758 | @group | |
4759 | Foo::Foo (int a, int b) | |
4760 | : Cyphr (a) | |
4761 | , Bar (b) @hereFn{c-lineup-multi-inher} | |
4762 | @end group | |
d7bd46ed GM |
4763 | @end example |
4764 | ||
6b61353c KH |
4765 | @workswith @code{inher-cont}, @code{member-init-cont}. |
4766 | @end defun | |
d7bd46ed | 4767 | |
6b61353c | 4768 | @comment ------------------------------------------------------------ |
d7bd46ed | 4769 | |
6b61353c KH |
4770 | @defun c-lineup-ObjC-method-call |
4771 | @findex lineup-ObjC-method-call (c-) | |
4772 | For Objective-C code, line up selector args as Emacs Lisp mode does | |
4773 | with function args: go to the position right after the message receiver, | |
4774 | and if you are at the end of the line, indent the current line | |
4775 | c-basic-offset columns from the opening bracket; otherwise you are | |
4776 | looking at the first character of the first method call argument, so | |
4777 | lineup the current line with it. | |
d7bd46ed | 4778 | |
6b61353c KH |
4779 | @workswith @code{objc-method-call-cont}. |
4780 | @end defun | |
d7bd46ed | 4781 | |
6b61353c | 4782 | @comment ------------------------------------------------------------ |
d7bd46ed | 4783 | |
6b61353c KH |
4784 | @defun c-lineup-ObjC-method-args |
4785 | @findex lineup-ObjC-method-args (c-) | |
4786 | For Objective-C code, line up the colons that separate args. The colon | |
4787 | on the current line is aligned with the one on the first line. | |
d7bd46ed | 4788 | |
6b61353c KH |
4789 | @workswith @code{objc-method-args-cont}. |
4790 | @end defun | |
d7bd46ed | 4791 | |
6b61353c KH |
4792 | @comment ------------------------------------------------------------ |
4793 | ||
4794 | @defun c-lineup-ObjC-method-args-2 | |
4795 | @findex lineup-ObjC-method-args-2 (c-) | |
4796 | Similar to @code{c-lineup-ObjC-method-args} but lines up the colon on | |
4797 | the current line with the colon on the previous line. | |
4798 | ||
4799 | @workswith @code{objc-method-args-cont}. | |
4800 | @end defun | |
d7bd46ed | 4801 | |
6b61353c KH |
4802 | @comment ------------------------------------------------------------ |
4803 | ||
4804 | @defun c-lineup-runin-statements | |
d7bd46ed | 4805 | @findex lineup-runin-statements (c-) |
d7bd46ed GM |
4806 | Line up statements for coding standards which place the first statement |
4807 | in a block on the same line as the block opening brace@footnote{Run-in | |
4808 | style doesn't really work too well. You might need to write your own | |
4809 | custom indentation functions to better support this style.}. E.g: | |
6b61353c | 4810 | |
d7bd46ed GM |
4811 | @example |
4812 | @group | |
d7bd46ed | 4813 | int main() |
6b61353c KH |
4814 | @{ puts ("Hello!"); |
4815 | return 0; @hereFn{c-lineup-runin-statements} | |
d7bd46ed | 4816 | @} |
d7bd46ed GM |
4817 | @end group |
4818 | @end example | |
4819 | ||
4820 | If there is no statement after the opening brace to align with, | |
4821 | @code{nil} is returned. This makes the function usable in list | |
4822 | expressions. | |
4823 | ||
4824 | @workswith The @code{statement} syntactic symbol. | |
6b61353c | 4825 | @end defun |
d7bd46ed | 4826 | |
6b61353c | 4827 | @comment ------------------------------------------------------------ |
d7bd46ed | 4828 | |
6b61353c KH |
4829 | @defun c-lineup-streamop |
4830 | @findex lineup-streamop (c-) | |
4831 | Line up C++ stream operators (i.e. @samp{<<} and @samp{>>}). | |
4832 | ||
4833 | @workswith @code{stream-op}. | |
4834 | @end defun | |
4835 | ||
4836 | @comment ------------------------------------------------------------ | |
4837 | ||
4838 | @defun c-lineup-string-cont | |
4839 | @findex lineup-string-cont (c-) | |
4840 | Line up a continued string under the one it continues. A continued | |
4841 | string in this sense is where a string literal follows directly after | |
4842 | another one. E.g: | |
4843 | ||
4844 | @example | |
4845 | @group | |
4846 | result = prefix + "A message " | |
4847 | "string."; @hereFn{c-lineup-string-cont} | |
4848 | @end group | |
4849 | @end example | |
4850 | ||
4851 | @code{nil} is returned in other situations, to allow stacking with other | |
4852 | lineup functions. | |
d7bd46ed | 4853 | |
6b61353c KH |
4854 | @workswith @code{topmost-intro-cont}, @code{statement-cont}, |
4855 | @code{arglist-cont}, @code{arglist-cont-nonempty}. | |
4856 | @end defun | |
4857 | ||
4858 | @comment ------------------------------------------------------------ | |
4859 | ||
4860 | @defun c-lineup-template-args | |
d7bd46ed | 4861 | @findex lineup-template-args (c-) |
d7bd46ed GM |
4862 | Line up the arguments of a template argument list under each other, but |
4863 | only in the case where the first argument is on the same line as the | |
4864 | opening @samp{<}. | |
4865 | ||
4866 | To allow this function to be used in a list expression, @code{nil} is | |
4867 | returned if there's no template argument on the first line. | |
4868 | ||
4869 | @workswith @code{template-args-cont}. | |
6b61353c | 4870 | @end defun |
d7bd46ed | 4871 | |
6b61353c | 4872 | @comment ------------------------------------------------------------ |
d7bd46ed | 4873 | |
6b61353c KH |
4874 | @defun c-lineup-topmost-intro-cont |
4875 | @findex lineup-topmost-intro-cont (c-) | |
4876 | Line up declaration continuation lines zero or one indentation | |
4877 | step@footnote{This function is mainly provided to mimic the behavior of | |
4878 | CC Mode 5.28 and earlier where this case wasn't handled consistently so | |
4879 | that those lines could be analyzed as either topmost-intro-cont or | |
4880 | statement-cont. It's used for @code{topmost-intro-cont} by default, but | |
4881 | you might consider using @code{+} instead.}. For lines preceding a | |
4882 | definition, zero is used. For other lines, @code{c-basic-offset} is | |
4883 | added to the indentation. E.g: | |
d7bd46ed | 4884 | |
6b61353c KH |
4885 | @example |
4886 | @group | |
4887 | int | |
4888 | neg (int i) @hereFn{c-lineup-topmost-intro-cont} | |
4889 | @{ | |
4890 | return -i; | |
4891 | @} | |
4892 | @end group | |
4893 | @end example | |
d7bd46ed | 4894 | |
6b61353c KH |
4895 | @noindent |
4896 | and | |
d7bd46ed | 4897 | |
6b61353c KH |
4898 | @example |
4899 | @group | |
4900 | struct | |
4901 | larch @hereFn{c-lineup-topmost-intro-cont} | |
4902 | @{ | |
4903 | double height; | |
4904 | @} | |
4905 | the_larch, @hereFn{c-lineup-topmost-intro-cont} | |
4906 | another_larch; @hereFn{c-lineup-topmost-intro-cont} | |
4907 | @sssTBasicOffset{} | |
4908 | @end group | |
4909 | @end example | |
d7bd46ed | 4910 | |
6b61353c KH |
4911 | @noindent |
4912 | and | |
d7bd46ed | 4913 | |
6b61353c KH |
4914 | @example |
4915 | @group | |
4916 | struct larch | |
4917 | the_larch, @hereFn{c-lineup-topmost-intro-cont} | |
4918 | another_larch; @hereFn{c-lineup-topmost-intro-cont} | |
4919 | @end group | |
4920 | @end example | |
d7bd46ed | 4921 | |
6b61353c KH |
4922 | @workswith @code{topmost-intro-cont}. |
4923 | @end defun | |
d7bd46ed | 4924 | |
6b61353c KH |
4925 | @comment ------------------------------------------------------------ |
4926 | ||
4927 | @defun c-lineup-whitesmith-in-block | |
d7bd46ed | 4928 | @findex lineup-whitesmith-in-block (c-) |
6b61353c | 4929 | Line up lines inside a block in Whitesmith style. It's done in a way |
d7bd46ed | 4930 | that works both when the opening brace hangs and when it doesn't. E.g: |
6b61353c | 4931 | |
d7bd46ed GM |
4932 | @example |
4933 | @group | |
d7bd46ed GM |
4934 | something |
4935 | @{ | |
6b61353c | 4936 | foo; @hereFn{c-lineup-whitesmith-in-block} |
d7bd46ed | 4937 | @} |
d7bd46ed GM |
4938 | @end group |
4939 | @end example | |
6b61353c | 4940 | |
d7bd46ed GM |
4941 | @noindent |
4942 | and | |
6b61353c | 4943 | |
d7bd46ed GM |
4944 | @example |
4945 | @group | |
d7bd46ed | 4946 | something @{ |
6b61353c | 4947 | foo; @hereFn{c-lineup-whitesmith-in-block} |
d7bd46ed | 4948 | @} |
6b61353c | 4949 | @sssTBasicOffset{} |
d7bd46ed GM |
4950 | @end group |
4951 | @end example | |
4952 | ||
4953 | In the first case the indentation is kept unchanged, in the second | |
4954 | @code{c-basic-offset} is added. | |
4955 | ||
4956 | @workswith @code{defun-close}, @code{defun-block-intro}, | |
4957 | @code{block-close}, @code{brace-list-close}, @code{brace-list-intro}, | |
6b61353c KH |
4958 | @code{statement-block-intro} and all @code{in*} symbols, |
4959 | e.g. @code{inclass} and @code{inextern-lang}. | |
4960 | @end defun | |
d7bd46ed | 4961 | |
d7bd46ed | 4962 | |
6b61353c KH |
4963 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
4964 | @node AWK Mode, Odds and Ends, Indentation Functions, Top | |
4965 | @comment node-name, next, previous, up | |
4966 | @chapter Status of AWK Mode | |
4967 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
4968 | ||
4969 | @dfn{AWK mode} existed until recently in the file @file{awk-mode.el} | |
4970 | as a mode derived from c-mode. It had not been actively maintained to | |
4971 | keep pace with the newer @ccmode{}, and its indentation mechanism no | |
4972 | longer worked satisfactorally. | |
4973 | ||
4974 | The current AWK mode is based around the GNU implementation, | |
4975 | @emph{GAWK version 3.1.0}, though it should work pretty well with any | |
4976 | AWK. It has now been updated and integrated into @ccmode{} to a | |
4977 | substantial extent, though as yet not all the features of @ccmode{} | |
4978 | have been adapted to support it. | |
4979 | ||
4980 | If your (X)Emacs is set up to use the old file @file{awk-mode.elc} | |
4981 | (which will usually be the case if you have obtained this @ccmode{} | |
4982 | independently of (X)Emacs itself), or if you are not sure, insert the | |
4983 | following form into your @file{.emacs} or @file{init.el} so that the new | |
4984 | AWK mode will be used instead: | |
4985 | ||
4986 | @example | |
4987 | (autoload 'awk-mode "cc-mode" nil t) | |
4988 | @end example | |
4989 | ||
4990 | You can check which AWK mode you are running by displaying the mode | |
4991 | documentation string with @kbd{C-h m} from an AWK buffer. The newer | |
4992 | mode's doc string contains @code{To submit a problem report, enter | |
4993 | `C-c C-b'} near the top of the doc string where the older mode has | |
4994 | @code{This is much like C mode except ....}. | |
4995 | ||
4996 | Since this newer AWK mode makes essential use of a relatively new | |
4997 | Emacs Lisp feature@footnote{Specifically, the @code{syntax-table} text | |
4998 | property.}, you need either GNU Emacs 20.1 (or later) or XEmacs 21.4 | |
4999 | (or later) to use it. If your Emacs version is earlier than one of | |
5000 | these, the older @file{awk-mode.el} will get loaded and run in place | |
5001 | of the AWK mode described here, even when you have put the above | |
5002 | @code{autoload} form into your @file{.emacs} or @file{init.el}. | |
5003 | Upgrading your (X)Emacs is strongly recommended if this is the case. | |
d7bd46ed | 5004 | |
6b61353c KH |
5005 | Here is an overview of which @ccmode{} features currently work with |
5006 | AWK mode and which don't: | |
5007 | ||
5008 | @table @asis | |
5009 | @item Indentation Engine | |
5010 | The @ccmode{} indentation engine fully supports AWK mode. | |
5011 | @xref{Indentation Engine}. | |
5012 | ||
5013 | AWK mode handles code formatted in the conventional AWK fashion: | |
5014 | @samp{@{}s which start actions, user-defined functions, or compound | |
5015 | statements are placed on the same line as the associated construct; the | |
5016 | matching @samp{@}}s are normally placed under the start of the | |
5017 | respective pattern, function definition, or structured statement. | |
5018 | @c Add in a bit about the @samp{@}} being on the same line when the | |
5019 | @c contents are short. | |
5020 | ||
5021 | The predefined indentation functions (@pxref{Indentation Functions}) | |
5022 | haven't yet been adapted for AWK mode, though some of them may work | |
5023 | serendipitously. There shouldn't be any problems writing custom | |
5024 | indentation functions for AWK mode. | |
5025 | ||
5026 | The command @kbd{C-c C-q} (@code{c-indent-defun}) hasn't yet been | |
5027 | adapted for AWK, though in practice it works properly nearly all the | |
5028 | time. Should it fail, explicitly set the region around the function | |
5029 | (using @kbd{C-u C-SPC}: @kbd{C-M-h} probably won't work either) then do | |
5030 | @kbd{C-M-\} (@code{indent-region}). | |
5031 | ||
5032 | @item Font Locking | |
5033 | There is a single level of font locking in AWK mode, rather than the | |
5034 | three distinct levels the other modes have. There are several | |
5035 | idiosyncrasies in AWK mode's font-locking due to the peculiarities of | |
5036 | the AWK language itself. @xref{AWK Mode Font Locking}. | |
5037 | ||
5038 | @item Comment Commands | |
5039 | @kbd{M-;} (@code{indent-for-comment}) works fine. None of the other | |
5040 | @ccmode{} comment formatting commands have yet been adapted for AWK | |
5041 | mode. @xref{Text Filling and Line Breaking}. | |
5042 | ||
5043 | @item Movement Commands | |
5044 | Most of the movement commands work in AWK mode. The most important | |
5045 | exceptions are @kbd{M-a} (@code{c-beginning-of-statement}) and | |
5046 | @kbd{M-e} (@code{c-end-of-statement}) which haven't yet been adapted. | |
5047 | ||
5048 | The notion of @dfn{defun} has been augmented to include pattern-action | |
5049 | pairs. See @ref{AWK Mode Defuns} for a description of commands which | |
5050 | work on AWK ``defuns''. | |
5051 | ||
5052 | Since there is no preprocessor in AWK, the commands which move to | |
5053 | preprocessor directives (e.g. @code{c-up-conditional}) are meaningless | |
5054 | in AWK mode and are not bound in the AWK mode keymap. | |
5055 | ||
5056 | @item Auto-newline Insertion and Clean-ups | |
5057 | Auto-newline insertion hasn't yet been adapted for AWK. Some of the | |
5058 | clean-ups can actually convert good AWK code into syntactically | |
5059 | invalid code. | |
5060 | ||
5061 | If auto-newline or its associated clean-ups are enabled generally for | |
5062 | the modes in @ccmode{}, you are strongly recommended to disable them | |
5063 | in the AWK Mode hook. @xref{Initialising AWK Mode}. | |
5064 | ||
5065 | The clean-up @code{space-before-funcall}, which is independent of | |
5066 | auto-newline, should never be active in AWK mode (since inserting a | |
5067 | space between a user function's name and its opening @samp{(} makes | |
5068 | the call syntactically invalid). If necessary, this should be | |
5069 | disabled in the AWK Mode hook. @xref{Initialising AWK Mode}. | |
5070 | ||
5071 | @end table | |
5072 | ||
5073 | @menu | |
5074 | * Initialising AWK Mode:: | |
5075 | * AWK Mode Font Locking:: | |
5076 | * AWK Mode Defuns:: | |
5077 | @end menu | |
5078 | ||
5079 | ||
5080 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5081 | @node Initialising AWK Mode, AWK Mode Font Locking, , AWK Mode | |
5082 | @comment node-name, next, previous, up | |
5083 | @section AWK mode - What to put in your @file{.emacs} or @file{init.el} | |
5084 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5085 | ||
5086 | Much of the AWK mode initialization can, of course, be done by the | |
5087 | @ccmode{} general initialization procedure. You may want to use certain | |
5088 | @ccmode{} features such as @code{auto-newline} and @code{clean-ups} in | |
5089 | the other modes, and you might thus have enabled them in a | |
5090 | @code{c-mode-common-hook} function, as described in @ref{Sample .emacs File}. | |
5091 | These features have not yet been amended for AWK mode, and far from | |
5092 | being useful, can be irritating in AWK mode or actually make AWK code | |
5093 | syntactically invalid. Adding the following code to your | |
5094 | @file{.emacs} or @file{init.el} file will disable them for AWK mode. | |
5095 | ||
5096 | @example | |
5097 | (defun my-awk-mode-hook () | |
5098 | "Disable certain @ccmode{} features which could impair AWK mode." | |
5099 | (c-toggle-auto-state -1) ; disable automatic insertions of newlines | |
5100 | (if (memq 'space-before-funcall c-cleanup-list) | |
5101 | (setq c-cleanup-list ; don't automatically insert a space into "foo(" | |
5102 | (remove 'space-before-funcall c-cleanup-list)))) | |
5103 | (add-hook 'awk-mode-hook 'my-awk-mode-hook) | |
5104 | @end example | |
5105 | ||
5106 | Naturally you can add your own AWK-specific customizations to this | |
5107 | function. @xref{Hooks}. | |
5108 | ||
5109 | ||
5110 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5111 | @node AWK Mode Font Locking, AWK Mode Defuns, Initialising AWK Mode, AWK Mode | |
5112 | @comment node-name, next, previous, up | |
5113 | @section AWK Mode Font Locking | |
5114 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5115 | ||
5116 | The general appearance of font-locking in AWK mode is much like in any | |
5117 | other programming mode. @xref{Faces For Font Lock,,,elisp}. | |
5118 | ||
5119 | The following faces are, however, used in a non-standard fashion in | |
5120 | AWK mode: | |
5121 | ||
5122 | @table @asis | |
5123 | @item @code{font-lock-variable-name-face} | |
5124 | This face was intended for variable declarations. Since variables are | |
5125 | not declared in AWK, this face is used instead for AWK system | |
5126 | variables (such as @code{NF}) and ``Special File Names'' (such as | |
5127 | @code{"/dev/stderr"}). | |
5128 | ||
5129 | @item @code{font-lock-builtin-face} (Emacs)/@code{font-lock-preprocessor-face} (XEmacs) | |
5130 | This face is normally used for preprocessor directives in @ccmode{}. | |
5131 | There are no such things in AWK, so this face is used instead for | |
5132 | standard functions (such as @code{match}). | |
5133 | ||
5134 | @item @code{font-lock-string-face} | |
5135 | As well as being used for strings, including localizable strings, | |
5136 | (delimited by @samp{"} and @samp{_"}), this face is also used for AWK | |
5137 | regular expressions (delimited by @samp{/}). | |
5138 | ||
5139 | @item @code{font-lock-warning-face} (Emacs)/@code{c-invalid-face} (XEmacs) | |
5140 | This face highlights the following syntactically invalid AWK | |
5141 | constructs: | |
5142 | ||
5143 | @itemize @bullet | |
5144 | @item | |
5145 | An unterminated string or regular expression. Here the opening | |
5146 | delimiter (@samp{"} or @samp{/} or @samp{_"}) is displayed in | |
5147 | @code{font-lock-warning-face}. This is most noticeable when typing in a | |
5148 | new string/regular expression into a buffer, when the warning-face | |
5149 | serves as a continual reminder to terminate the construct. | |
5150 | ||
5151 | AWK mode fontifies unterminated strings/regular expressions | |
5152 | differently from other modes: Only the text up to the end of the line | |
5153 | is fontified as a string (escaped newlines being handled correctly), | |
5154 | rather than the text up to the next string quote. | |
5155 | ||
5156 | @item | |
5157 | A space between the function name and opening parenthesis when calling | |
5158 | a user function. The last character of the function name and the | |
5159 | opening parenthesis are highlighted. This font-locking rule will | |
5160 | spuriously highlight a valid concatenation expression where an | |
5161 | identifier precedes a parenthesised expression. Unfortunately. | |
5162 | ||
5163 | @item | |
5164 | Whitespace following the @samp{\} in what otherwise looks like an | |
5165 | escaped newline. The @samp{\} is highlighted. | |
5166 | @end itemize | |
5167 | @end table | |
5168 | ||
5169 | ||
5170 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5171 | @node AWK Mode Defuns, , AWK Mode Font Locking, AWK Mode | |
5172 | @comment node-name, next, previous, up | |
5173 | @section AWK Mode Defuns | |
5174 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5175 | ||
5176 | In AWK mode, @dfn{defun} means either a user-defined function or a | |
5177 | pattern-action pair. Either the pattern or the action may be | |
5178 | implicit. | |
5179 | ||
5180 | The beginning of a defun is recognised heuristically as, more or less, | |
5181 | code which begins in column zero. Having the @samp{@{} in column zero, | |
5182 | as is suggested for some modes, is neither necessary nor helpful in AWK | |
5183 | mode. | |
5184 | ||
5185 | More precisely, the beginning of a defun is code which begins in | |
5186 | column zero, and which isn't a closing brace, a comment, or a | |
5187 | continuation of the previous line. Code is the @dfn{continuation of | |
5188 | the previous line} when that line is syntactically incomplete, for | |
5189 | example when it ends with @samp{@{} or an escaped newline. | |
5190 | ||
5191 | The end of a defun is the @samp{@}} which matches the @samp{@{} (if | |
5192 | any) at the beginning of the action or function body, or the EOL or | |
5193 | @samp{;} which marks an implicit action. Although this @samp{@}} is | |
5194 | usually placed in column zero, AWK mode doesn't need it to be placed | |
5195 | there. | |
5196 | ||
5197 | @table @asis | |
5198 | @item @kbd{C-M-a} @code{c-awk-beginning-of-defun} | |
5199 | @itemx @kbd{C-M-e} @code{c-awk-end-of-defun} | |
5200 | @findex c-awk-beginning-of-defun | |
5201 | @findex awk-beginning-of-defun (c-) | |
5202 | @findex c-awk-end-of-defun | |
5203 | @findex awk-end-of-defun (c-) | |
5204 | Move point back to the beginning or forward to the end of the current | |
5205 | AWK defun. These functions can take prefix-arguments, their | |
5206 | functionality being entirely equivalent to @code{beginning-of-defun} | |
5207 | and @code{end-of-defun}. @xref{Moving by Defuns,,,emacs}. | |
5208 | ||
5209 | @item @kbd{C-M-h} @code{c-mark-function} | |
5210 | This works fine with AWK defuns. @xref{Indentation Commands}. | |
d7bd46ed GM |
5211 | @end table |
5212 | ||
6bf7aab6 | 5213 | |
d7bd46ed | 5214 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
6b61353c KH |
5215 | @node Odds and Ends, Performance Issues, AWK Mode, Top |
5216 | @comment node-name, next, previous, up | |
5217 | @chapter Odds and Ends | |
5218 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5219 | ||
5220 | The stuff that didn't fit in anywhere else is documented here. | |
5221 | ||
5222 | @defopt c-require-final-newline | |
5223 | @vindex require-final-newline (c-) | |
5224 | Controls whether a final newline is ensured when the file is saved. The | |
5225 | value is an association list that for each language mode specifies the | |
5226 | value to give to @code{require-final-newline} at mode initialization; | |
5227 | see that variable for details about the value. If a language isn't | |
5228 | present on the association list, CC Mode won't set | |
5229 | @code{require-final-newline} in buffers for that language. | |
5230 | ||
5231 | The default is to set @code{require-final-newline} to @code{t} in the | |
5232 | languages that mandates that source files should end with newlines, | |
5233 | i.e. C, C++ and Objective-C. | |
5234 | @end defopt | |
5235 | ||
5236 | @defopt c-echo-syntactic-information-p | |
5237 | @vindex echo-syntactic-information-p (c-) | |
5238 | If non-@code{nil}, the syntactic analysis for the current line is shown | |
5239 | in the echo area when it's indented (unless | |
5240 | @code{c-syntactic-indentation} is @code{nil}). That's useful when | |
5241 | finding out which syntactic symbols to modify to get the indentation you | |
5242 | want. | |
5243 | @end defopt | |
5244 | ||
5245 | @defopt c-report-syntactic-errors | |
5246 | @vindex report-syntactic-errors (c-) | |
5247 | If non-@code{nil}, certain syntactic errors are reported with a ding and | |
5248 | a message, for example when an @code{else} is indented for which there | |
5249 | is no corresponding @code{if}. | |
5250 | ||
5251 | Note however that @ccmode{} doesn't make any special effort to check for | |
5252 | syntactic errors; that's the job of the compiler. The reason it can | |
5253 | report cases like the one above is that it can't find the correct | |
5254 | anchoring position to indent the line in that case. | |
5255 | @end defopt | |
5256 | ||
5257 | ||
5258 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5259 | @node Performance Issues, Limitations and Known Bugs, Odds and Ends, Top | |
d7bd46ed | 5260 | @comment node-name, next, previous, up |
6b61353c KH |
5261 | @chapter Performance Issues |
5262 | @cindex performance | |
6bf7aab6 DL |
5263 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
5264 | ||
6b61353c KH |
5265 | @comment FIXME: (ACM, 2003/5/24). Check whether AWK needs mentioning here. |
5266 | ||
6bf7aab6 | 5267 | C and its derivative languages are highly complex creatures. Often, |
6b61353c KH |
5268 | ambiguous code situations arise that require @ccmode{} to scan large |
5269 | portions of the buffer to determine syntactic context. Such | |
5270 | pathological code can cause @ccmode{} to perform fairly badly. This | |
5271 | section gives some insight in how @ccmode{} operates, how that interacts | |
5272 | with some coding styles, and what you can use to improve performance. | |
5273 | ||
5274 | The overall goal is that @ccmode{} shouldn't be overly slow (i.e. take | |
5275 | more than a fraction of a second) in any interactive operation. | |
5276 | I.e. it's tuned to limit the maximum response time in single operations, | |
5277 | which sometimes is at the expense of batch-like operations like | |
5278 | reindenting whole blocks. If you find that @ccmode{} gradually gets | |
5279 | slower and slower in certain situations, perhaps as the file grows in | |
5280 | size or as the macro or comment you're editing gets bigger, then chances | |
5281 | are that something isn't working right. You should consider reporting | |
5282 | it, unless it's something that's mentioned in this section. | |
6bf7aab6 DL |
5283 | |
5284 | Because @ccmode{} has to scan the buffer backwards from the current | |
5285 | insertion point, and because C's syntax is fairly difficult to parse in | |
5286 | the backwards direction, @ccmode{} often tries to find the nearest | |
6b61353c KH |
5287 | position higher up in the buffer from which to begin a forward scan |
5288 | (it's typically an opening or closing parethesis of some kind). The | |
5289 | farther this position is from the current insertion point, the slower it | |
5290 | gets. | |
6bf7aab6 DL |
5291 | |
5292 | @findex beginning-of-defun | |
5293 | @findex defun-prompt-regexp | |
5294 | One of the simplest things you can do to reduce scan time, is make sure | |
d7bd46ed | 5295 | any brace that opens a top-level construct@footnote{E.g. a function in |
6bf7aab6 DL |
5296 | C, or outermost class definition in C++ or Java.} always appears in the |
5297 | leftmost column. This is actually an Emacs constraint, as embodied in | |
d7bd46ed | 5298 | the @code{beginning-of-defun} function which @ccmode{} uses heavily. If |
6b61353c KH |
5299 | you hang top-level open braces on the right side of the line, then you |
5300 | might want to set the variable @code{defun-prompt-regexp} to something | |
5301 | reasonable, however that ``something reasonable'' is difficult to | |
5302 | define, so @ccmode{} doesn't do it for you. | |
6bf7aab6 DL |
5303 | |
5304 | @vindex c-Java-defun-prompt-regexp | |
5305 | @vindex Java-defun-prompt-regexp (c-) | |
6b61353c KH |
5306 | A special note about @code{defun-prompt-regexp} in Java mode: The common |
5307 | style is to hang the opening braces of functions and classes on the | |
5308 | right side of the line, and that doesn't work well with the Emacs | |
5309 | approach. @ccmode{} comes with a variable | |
6bf7aab6 DL |
5310 | @code{c-Java-defun-prompt-regexp} which tries to define a regular |
5311 | expression usable for this style, but there are problems with it. In | |
5312 | some cases it can cause @code{beginning-of-defun} to hang@footnote{This | |
5313 | has been observed in Emacs 19.34 and XEmacs 19.15.}. For this reason, | |
5314 | it is not used by default, but if you feel adventurous, you can set | |
5315 | @code{defun-prompt-regexp} to it in your mode hook. In any event, | |
6b61353c KH |
5316 | setting and relying on @code{defun-prompt-regexp} will definitely slow |
5317 | things down because (X)Emacs will be doing regular expression searches a | |
5318 | lot, so you'll probably be taking a hit either way! | |
5319 | ||
5320 | @ccmode{} maintains a cache of the opening parentheses of the blocks | |
5321 | surrounding the point, and it adapts that cache as the point is moved | |
5322 | around. That means that in bad cases it can take noticeable time to | |
5323 | indent a line in a new surrounding, but after that it gets fast as long | |
5324 | as the point isn't moved far off. The farther the point is moved, the | |
5325 | less useful is the cache. Since editing typically is done in ``chunks'' | |
5326 | rather than on single lines far apart from each other, the cache | |
5327 | typically gives good performance even when the code doesn't fit the | |
5328 | Emacs approach to finding the defun starts. | |
d7bd46ed GM |
5329 | |
5330 | @vindex c-enable-xemacs-performance-kludge-p | |
5331 | @vindex enable-xemacs-performance-kludge-p (c-) | |
6b61353c | 5332 | XEmacs users can set the variable |
d7bd46ed GM |
5333 | @code{c-enable-xemacs-performance-kludge-p} to non-@code{nil}. This |
5334 | tells @ccmode{} to use XEmacs-specific built-in functions which, in some | |
6b61353c | 5335 | circumstances, can locate the top-most opening brace much more quickly than |
d7bd46ed GM |
5336 | @code{beginning-of-defun}. Preliminary testing has shown that for |
5337 | styles where these braces are hung (e.g. most JDK-derived Java styles), | |
5338 | this hack can improve performance of the core syntax parsing routines | |
5339 | from 3 to 60 times. However, for styles which @emph{do} conform to | |
5340 | Emacs' recommended style of putting top-level braces in column zero, | |
5341 | this hack can degrade performance by about as much. Thus this variable | |
6b61353c KH |
5342 | is set to @code{nil} by default, since the Emacs-friendly styles should |
5343 | be more common (and encouraged!). Note that this variable has no effect | |
5344 | in Emacs since the necessary built-in functions don't exist (in Emacs | |
5345 | 21.3 as of this writing in May 2003). | |
5346 | ||
5347 | Text properties are used to speed up skipping over syntactic whitespace, | |
5348 | i.e. comments and preprocessor directives. Indenting a line after a | |
5349 | huge macro definition can be slow the first time, but after that the | |
5350 | text properties are in place and it should be fast (even after you've | |
5351 | edited other parts of the file and then moved back). | |
5352 | ||
5353 | Font locking can be a CPU hog, especially the font locking done on | |
5354 | decoration level 3 which tries to be very accurate. Note that that | |
5355 | level is designed to be used with a font lock support mode that only | |
5356 | fontifies the text that's actually shown, i.e. Lazy Lock or Just-in-time | |
5357 | Lock mode, so make sure you use one of them. Fontification of a whole | |
5358 | buffer with some thousand lines can often take over a minute. That is | |
5359 | a known weakness; the idea is that it never should happen. | |
5360 | ||
5361 | The most effective way to speed up font locking is to reduce the | |
5362 | decoration level to 2 by setting @code{font-lock-maximum-decoration} | |
5363 | appropriately. That level is designed to be as pretty as possible | |
5364 | without sacrificing performance. @xref{Font Locking Preliminaries}, for | |
5365 | more info. | |
6bf7aab6 DL |
5366 | |
5367 | ||
cb7f2e96 GM |
5368 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
5369 | @node Limitations and Known Bugs, Frequently Asked Questions, Performance Issues, Top | |
5370 | @comment node-name, next, previous, up | |
6b61353c | 5371 | @chapter Limitations and Known Bugs |
cb7f2e96 GM |
5372 | @cindex limitations |
5373 | @cindex bugs | |
5374 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5375 | ||
5376 | @itemize @bullet | |
5377 | @item | |
6b61353c KH |
5378 | There is no way to apply auto newline settings (@pxref{Auto-newline |
5379 | Insertion}) on already typed lines. That's only a feature to ease | |
5380 | interactive editing. | |
cb7f2e96 | 5381 | |
6b61353c KH |
5382 | To generalize this issue a bit: @ccmode{} is not intended to be used as |
5383 | a reformatter for old code in some more or less batch-like way. With | |
5384 | the exception of some functions like @code{c-indent-region}, it's only | |
5385 | geared to be used interactively to edit new code. There's currently no | |
5386 | intention to change this goal. | |
5387 | ||
5388 | If you want to reformat old code, you're probably better off using some | |
5389 | other tool instead, e.g. @ref{Top, , GNU indent, indent, The `indent' | |
5390 | Manual}, which has more powerful reformatting capabilities than | |
5391 | @ccmode{}. | |
cb7f2e96 | 5392 | |
cb7f2e96 | 5393 | @item |
6b61353c KH |
5394 | @vindex signal-error-on-buffer-boundary |
5395 | XEmacs has a variable called @code{signal-error-on-buffer-boundary}. | |
5396 | It's used as a solution to user interface problems associated with | |
cb7f2e96 | 5397 | buffer movement and the @code{zmacs-region} deactivation on errors. |
6b61353c KH |
5398 | However, setting this variable to a non-default value in XEmacs 19 and |
5399 | 20 had the deleterious side effect of breaking many built-in primitive | |
5400 | functions. @strong{Do not set this variable to @code{nil} in XEmacs | |
5401 | 19 and 20}; you will cause serious problems in @ccmode{} and probably | |
5402 | other XEmacs packages! In XEmacs 21 the effects of the variable is | |
5403 | limited to some functions that are only used interactively, so it's | |
5404 | not a problem there. | |
cb7f2e96 GM |
5405 | @end itemize |
5406 | ||
5407 | ||
6bf7aab6 | 5408 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
cb7f2e96 | 5409 | @node Frequently Asked Questions, Getting the Latest CC Mode Release, Limitations and Known Bugs, Top |
d7bd46ed | 5410 | @comment node-name, next, previous, up |
cb7f2e96 | 5411 | @appendix Frequently Asked Questions |
6bf7aab6 DL |
5412 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
5413 | ||
6b61353c KH |
5414 | @itemize @bullet |
5415 | @item | |
6bf7aab6 | 5416 | @kindex C-x h |
d7bd46ed | 5417 | @kindex C-M-\ |
6b61353c | 5418 | @emph{How do I reindent the whole file?} |
6bf7aab6 | 5419 | |
6b61353c KH |
5420 | Visit the file and hit @kbd{C-x h} to mark the whole buffer. Then hit |
5421 | @kbd{C-M-\}. | |
6bf7aab6 | 5422 | |
6b61353c KH |
5423 | @item |
5424 | @kindex C-M-q | |
5425 | @kindex C-M-u | |
5426 | @emph{How do I reindent the current block?} | |
6bf7aab6 | 5427 | |
6b61353c KH |
5428 | First move to the brace which opens the block with @kbd{C-M-u}, then |
5429 | reindent that expression with @kbd{C-M-q}. | |
6bf7aab6 | 5430 | |
6b61353c KH |
5431 | @item |
5432 | @kindex RET | |
5433 | @kindex C-j | |
5434 | @emph{Why doesn't the @kbd{RET} key indent the new line?} | |
6bf7aab6 | 5435 | |
6b61353c KH |
5436 | Emacs' convention is that @kbd{RET} just adds a newline, and that |
5437 | @kbd{C-j} adds a newline and indents it. You can make @kbd{RET} do this | |
5438 | too by adding this to your @code{c-mode-common-hook}: | |
6bf7aab6 | 5439 | |
6bf7aab6 | 5440 | @example |
d7bd46ed | 5441 | (define-key c-mode-base-map "\C-m" 'c-context-line-break) |
6bf7aab6 DL |
5442 | @end example |
5443 | ||
5444 | This is a very common question. If you want this to be the default | |
d7bd46ed | 5445 | behavior, don't lobby me, lobby RMS! @t{:-)} |
6bf7aab6 | 5446 | |
6b61353c KH |
5447 | @item |
5448 | @emph{I put @code{(c-set-offset 'substatement-open 0)} in my | |
5449 | @file{.emacs} file but I get an error saying that @code{c-set-offset}'s | |
5450 | function definition is void. What's wrong?} | |
6bf7aab6 | 5451 | |
6b61353c KH |
5452 | This means that @ccmode{} wasn't loaded into your Emacs session by the |
5453 | time the @code{c-set-offset} call was reached, most likely because | |
5454 | @ccmode{} is being autoloaded. Instead of putting the | |
5455 | @code{c-set-offset} line in your top-level @file{.emacs} file, put it in | |
5456 | your @code{c-mode-common-hook}, or simply modify @code{c-offsets-alist} | |
5457 | directly: | |
f214c025 | 5458 | |
6b61353c KH |
5459 | @example |
5460 | (setq c-offsets-alist '((substatement-open . 0))) | |
6bf7aab6 DL |
5461 | @end example |
5462 | ||
6b61353c KH |
5463 | @item |
5464 | @kindex M-a | |
5465 | @kindex M-e | |
5466 | @emph{@kbd{M-a} and @kbd{M-e} used to move over entire balanced brace | |
5467 | lists, but now they move into blocks. How do I get the old behavior | |
5468 | back?} | |
5469 | ||
5470 | Use @kbd{C-M-f} and @kbd{C-M-b} to move over balanced brace blocks. Use | |
5471 | @kbd{M-a} and @kbd{M-e} to move by statements, which will also move into | |
5472 | blocks. | |
5473 | ||
5474 | @item | |
5475 | @emph{Whenever I try to indent a line or type an ``electric'' key such | |
5476 | as @kbd{;}, @kbd{@{}, or @kbd{@}}, I get an error that look like this: | |
5477 | @code{Invalid function: (macro . #[...}. What gives?} | |
5478 | ||
5479 | This is a common error when @ccmode{} hasn't been compiled correctly, | |
5480 | especially under Emacs 19.34@footnote{Technically, it's because some | |
5481 | macro wasn't defined during the compilation, so the byte compiler put | |
5482 | in function calls instead of the macro expansions. Later, when the | |
5483 | interpreter tries to call the macro as a function, it shows this | |
5484 | (somewhat cryptic) error message.}. If you are using the standalone | |
d7bd46ed GM |
5485 | @ccmode{} distribution, try recompiling it according to the instructions |
5486 | in the @file{README} file. | |
6b61353c | 5487 | @end itemize |
6bf7aab6 DL |
5488 | |
5489 | ||
5490 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
cb7f2e96 | 5491 | @node Getting the Latest CC Mode Release, Mailing Lists and Submitting Bug Reports, Frequently Asked Questions, Top |
d7bd46ed | 5492 | @comment node-name, next, previous, up |
cb7f2e96 | 5493 | @appendix Getting the Latest CC Mode Release |
6bf7aab6 DL |
5494 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
5495 | ||
6b61353c KH |
5496 | @ccmode{} has been standard with all versions of Emacs since 19.34 and |
5497 | of XEmacs since 19.16. | |
d7bd46ed | 5498 | |
6b61353c | 5499 | @cindex web site |
d7bd46ed | 5500 | Due to release schedule skew, it is likely that all of these Emacsen |
177c0ea7 | 5501 | have old versions of @ccmode{} and so should be upgraded. Access to the |
d7bd46ed | 5502 | @ccmode{} source code, as well as more detailed information on Emacsen |
6b61353c | 5503 | compatibility, etc. are all available on the web site: |
d7bd46ed | 5504 | |
6b61353c KH |
5505 | @quotation |
5506 | @uref{http://cc-mode.sourceforge.net/} | |
5507 | @end quotation | |
6bf7aab6 | 5508 | |
6bf7aab6 | 5509 | |
cb7f2e96 GM |
5510 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
5511 | @node Mailing Lists and Submitting Bug Reports, Sample .emacs File, Getting the Latest CC Mode Release, Top | |
5512 | @comment node-name, next, previous, up | |
5513 | @appendix Mailing Lists and Submitting Bug Reports | |
cb7f2e96 GM |
5514 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
5515 | ||
5516 | @kindex C-c C-b | |
5517 | @findex c-submit-bug-report | |
5518 | @findex submit-bug-report (c-) | |
6b61353c KH |
5519 | To report bugs, use the @kbd{C-c C-b} (bound to |
5520 | @code{c-submit-bug-report}) command. This provides vital information | |
5521 | we need to reproduce your problem. Make sure you include a concise, | |
5522 | but complete code example. Please try to boil your example down to | |
5523 | just the essential code needed to reproduce the problem, and include | |
5524 | an exact recipe of steps needed to expose the bug. Be especially sure | |
5525 | to include any code that appears @emph{before} your bug example, if | |
5526 | you think it might affect our ability to reproduce it. | |
cb7f2e96 GM |
5527 | |
5528 | Please try to produce the problem in an Emacs instance without any | |
5529 | customizations loaded (i.e. start it with the @code{-q -no-site-file} | |
5530 | arguments). If it works correctly there, the problem might be caused by | |
5531 | faulty customizations in either your own or your site configuration. In | |
5532 | that case, we'd appreciate if you isolate the Emacs Lisp code that trigs | |
5533 | the bug and include it in your report. | |
5534 | ||
5535 | @cindex bug report mailing list | |
6b61353c KH |
5536 | Bug reports are sent to @email{bug-cc-mode@@gnu.org}. You can also send |
5537 | other questions and suggestions (kudos? @t{;-)} to that address. It's a | |
5538 | mailing list which you can join or browse an archive of; see the web | |
5539 | site at @uref{http://cc-mode.sourceforge.net/} for further details. | |
cb7f2e96 GM |
5540 | |
5541 | @cindex announcement mailing list | |
5542 | If you want to get announcements of new @ccmode{} releases, send the | |
5543 | word @emph{subscribe} in the body of a message to | |
6b61353c KH |
5544 | @email{cc-mode-announce-request@@lists.sourceforge.net}. It's possible |
5545 | to subscribe from the web site too. Announcements will also be posted | |
5546 | to the Usenet newsgroups @code{gnu.emacs.sources}, @code{comp.emacs} and | |
5547 | @code{comp.emacs.xemacs}. | |
cb7f2e96 GM |
5548 | |
5549 | ||
6bf7aab6 | 5550 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
6b61353c | 5551 | @node Sample .emacs File, Command and Function Index, Mailing Lists and Submitting Bug Reports, Top |
d7bd46ed | 5552 | @comment node-name, next, previous, up |
cb7f2e96 | 5553 | @appendix Sample .emacs file |
6bf7aab6 DL |
5554 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
5555 | ||
5556 | @example | |
6b61353c KH |
5557 | ;; Here's a sample .emacs file that might help you along the way. |
5558 | ;; Just copy this region and paste it into your .emacs file. You may | |
5559 | ;; want to change some of the actual values. | |
6bf7aab6 DL |
5560 | |
5561 | (defconst my-c-style | |
5562 | '((c-tab-always-indent . t) | |
5563 | (c-comment-only-line-offset . 4) | |
5564 | (c-hanging-braces-alist . ((substatement-open after) | |
5565 | (brace-list-open))) | |
5566 | (c-hanging-colons-alist . ((member-init-intro before) | |
5567 | (inher-intro) | |
5568 | (case-label after) | |
5569 | (label after) | |
5570 | (access-label after))) | |
5571 | (c-cleanup-list . (scope-operator | |
5572 | empty-defun-braces | |
5573 | defun-close-semi)) | |
5574 | (c-offsets-alist . ((arglist-close . c-lineup-arglist) | |
5575 | (substatement-open . 0) | |
5576 | (case-label . 4) | |
5577 | (block-open . 0) | |
5578 | (knr-argdecl-intro . -))) | |
6b61353c | 5579 | (c-echo-syntactic-information-p . t)) |
6bf7aab6 DL |
5580 | "My C Programming Style") |
5581 | ||
d7bd46ed | 5582 | ;; offset customizations not in my-c-style |
f214c025 | 5583 | (setq c-offsets-alist '((member-init-intro . ++))) |
d7bd46ed GM |
5584 | |
5585 | ;; Customizations for all modes in CC Mode. | |
6bf7aab6 DL |
5586 | (defun my-c-mode-common-hook () |
5587 | ;; add my personal style and set it for the current buffer | |
5588 | (c-add-style "PERSONAL" my-c-style t) | |
6bf7aab6 DL |
5589 | ;; other customizations |
5590 | (setq tab-width 8 | |
5591 | ;; this will make sure spaces are used instead of tabs | |
5592 | indent-tabs-mode nil) | |
5593 | ;; we like auto-newline and hungry-delete | |
5594 | (c-toggle-auto-hungry-state 1) | |
47d7776c | 5595 | ;; key bindings for all supported languages. We can put these in |
6bf7aab6 | 5596 | ;; c-mode-base-map because c-mode-map, c++-mode-map, objc-mode-map, |
d7bd46ed | 5597 | ;; java-mode-map, idl-mode-map, and pike-mode-map inherit from it. |
6b61353c | 5598 | (define-key c-mode-base-map "\C-m" 'c-context-line-break)) |
6bf7aab6 DL |
5599 | |
5600 | (add-hook 'c-mode-common-hook 'my-c-mode-common-hook) | |
5601 | @end example | |
5602 | ||
d7bd46ed | 5603 | |
6bf7aab6 | 5604 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
6b61353c | 5605 | @node Command and Function Index, Variable Index, Sample .emacs File, Top |
d7bd46ed | 5606 | @comment node-name, next, previous, up |
6b61353c | 5607 | @unnumbered Command and Function Index |
d7bd46ed | 5608 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
6bf7aab6 | 5609 | |
6b61353c KH |
5610 | Since most @ccmode{} commands are prepended with the string |
5611 | @samp{c-}, each appears under its @code{c-@var{thing}} name and its | |
5612 | @code{@var{thing} (c-)} name. | |
5613 | @iftex | |
5614 | @sp 2 | |
5615 | @end iftex | |
5616 | @printindex fn | |
6bf7aab6 DL |
5617 | |
5618 | ||
d7bd46ed | 5619 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
6b61353c | 5620 | @node Variable Index, Concept Index, Command and Function Index, Top |
d7bd46ed | 5621 | @comment node-name, next, previous, up |
6b61353c | 5622 | @unnumbered Variable Index |
d7bd46ed | 5623 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
6bf7aab6 | 5624 | |
6b61353c KH |
5625 | Since most @ccmode{} variables are prepended with the string |
5626 | @samp{c-}, each appears under its @code{c-@var{thing}} name and its | |
5627 | @code{@var{thing} (c-)} name. | |
6bf7aab6 DL |
5628 | @iftex |
5629 | @sp 2 | |
5630 | @end iftex | |
6b61353c | 5631 | @printindex vr |
6bf7aab6 DL |
5632 | |
5633 | ||
d7bd46ed | 5634 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
6b61353c | 5635 | @node Concept Index, , Variable Index, Top |
d7bd46ed | 5636 | @comment node-name, next, previous, up |
6b61353c | 5637 | @unnumbered Concept Index |
d7bd46ed | 5638 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
6bf7aab6 | 5639 | |
6b61353c | 5640 | @printindex cp |
6bf7aab6 DL |
5641 | |
5642 | ||
d7bd46ed | 5643 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
6b61353c | 5644 | @comment Epilogue. |
d7bd46ed | 5645 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
6bf7aab6 | 5646 | |
cb7f2e96 | 5647 | @iftex |
6bf7aab6 DL |
5648 | @page |
5649 | @summarycontents | |
5650 | @contents | |
cb7f2e96 GM |
5651 | @end iftex |
5652 | ||
6bf7aab6 | 5653 | @bye |
6b61353c KH |
5654 | |
5655 | @ignore | |
5656 | arch-tag: c4cab162-5e57-4366-bdce-4a9db2fc97f0 | |
5657 | @end ignore |