Commit | Line | Data |
---|---|---|
4009494e GM |
1 | \input texinfo |
2 | @c Notes to self regarding line handling: | |
3 | @c | |
4 | @c Empty lines are often significant before @end directives; avoid them. | |
5 | @c | |
6 | @c Empty lines before and after @example directives are significant in | |
7 | @c info output but not in TeX. Empty lines inside @example directives | |
8 | @c are significant. | |
9 | ||
10 | @c Conventions for formatting examples: | |
11 | @c o If the example contains empty lines then put the surrounding empty | |
12 | @c lines inside the @example directives. Put them outside otherwise. | |
13 | @c o Use @group inside the example only if it shows indentation where | |
14 | @c the relation between lines inside is relevant. | |
15 | @c o Format line number columns like this: | |
16 | @c 1: foo | |
17 | @c 2: bar | |
18 | @c ^ one space | |
19 | @c ^^ two columns, right alignment | |
20 | @c o Check line lengths in TeX output; they can typically be no longer | |
21 | @c than 70 chars, 60 if the paragraph is indented. | |
22 | ||
23 | @comment TBD: Document the finer details of statement anchoring? | |
24 | ||
25 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
26 | @comment %**start of header (This is for running Texinfo on a region) | |
27 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
28 | ||
29 | ||
30 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
31 | @comment How to make the various output formats: | |
32 | @comment (Thanks to Robert Chassell for supplying this information.) | |
33 | @comment Note that Texinfo 4.7 (or later) is needed. | |
34 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
35 | @ignore | |
36 | In each of the following pairs of commands, the first generates a | |
37 | version with cross references pointing to the GNU Emacs manuals, | |
38 | the second with them pointing to the XEmacs manuals. | |
39 | ## Info output | |
40 | makeinfo cc-mode.texi | |
41 | makeinfo -DXEMACS cc-mode.texi | |
42 | ||
43 | ## DVI output | |
44 | ## You may need to set up the environment variable TEXINPUTS so | |
45 | ## that tex can find the file texinfo.tex - See the tex | |
46 | ## manpage. | |
47 | texi2dvi cc-mode.texi | |
48 | texi2dvi -t "@set XEMACS " cc-mode.texi | |
49 | ||
50 | ## HTML output. (The --no-split parameter is optional) | |
51 | makeinfo --html --no-split cc-mode.texi | |
52 | makeinfo --html --no-split -DXEMACS cc-mode.texi | |
53 | ||
54 | ## Plain text output | |
55 | makeinfo --fill-column=70 --no-split --paragraph-indent=0 \ | |
56 | --no-headers --output=cc-mode.txt cc-mode.texi | |
57 | makeinfo --fill-column=70 --no-split --paragraph-indent=0 \ | |
58 | --no-headers --output=cc-mode.txt -DXEMACS cc-mode.texi | |
59 | ||
60 | ## DocBook output | |
61 | makeinfo --docbook --no-split --paragraph-indent=0 \ | |
62 | cc-mode.texi | |
63 | makeinfo --docbook --no-split --paragraph-indent=0 \ | |
64 | -DXEMACS cc-mode.texi | |
65 | ||
66 | ## XML output | |
67 | makeinfo --xml --no-split --paragraph-indent=0 \ | |
68 | cc-mode.texi | |
69 | makeinfo --xml --no-split --paragraph-indent=0 \ | |
70 | -DXEMACS cc-mode.texi | |
71 | ||
72 | #### (You must be in the same directory as the viewed file.) | |
73 | ||
74 | ## View DVI output | |
75 | xdvi cc-mode.dvi & | |
76 | ||
77 | ## View HTML output | |
78 | mozilla cc-mode.html | |
79 | @end ignore | |
80 | ||
81 | @comment No overfull hbox marks in the dvi file. | |
82 | @finalout | |
83 | ||
db78a8cb | 84 | @setfilename ../../info/ccmode |
4009494e GM |
85 | @settitle CC Mode Manual |
86 | @footnotestyle end | |
87 | ||
88 | @c The following four macros generate the filenames and titles of the | |
89 | @c main (X)Emacs manual and the Elisp/Lispref manual. Leave the | |
90 | @c Texinfo variable `XEMACS' unset to generate a GNU Emacs version, set it | |
1df7defd | 91 | @c to generate an XEmacs version, e.g., with |
4009494e GM |
92 | @c "makeinfo -DXEMACS cc-mode.texi". |
93 | @ifset XEMACS | |
94 | @macro emacsman | |
95 | xemacs | |
96 | @end macro | |
97 | @macro emacsmantitle | |
98 | XEmacs User's Manual | |
99 | @end macro | |
100 | @macro lispref | |
101 | lispref | |
102 | @end macro | |
103 | @macro lispreftitle | |
104 | XEmacs Lisp Reference Manual | |
105 | @end macro | |
106 | @end ifset | |
107 | ||
108 | @ifclear XEMACS | |
109 | @macro emacsman | |
110 | emacs | |
111 | @end macro | |
112 | @macro emacsmantitle | |
113 | GNU Emacs Manual | |
114 | @end macro | |
115 | @macro lispref | |
116 | elisp | |
117 | @end macro | |
118 | @macro lispreftitle | |
119 | GNU Emacs Lisp Reference Manual | |
120 | @end macro | |
121 | @end ifclear | |
122 | ||
123 | ||
124 | @macro ccmode | |
125 | CC Mode | |
126 | @end macro | |
127 | ||
128 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
129 | @comment @setchapternewpage odd !! we don't want blank pages !! | |
130 | @comment %**end of header (This is for running Texinfo on a region) | |
131 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
132 | ||
133 | ||
134 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
135 | @comment | |
136 | @comment Texinfo manual for CC Mode | |
137 | @comment Generated from the original README file by Krishna Padmasola | |
138 | @comment <krishna@earth-gw.njit.edu> | |
139 | @comment | |
140 | @comment Authors: | |
141 | @comment Barry A. Warsaw | |
142 | @comment Martin Stjernholm | |
143 | @comment Alan Mackenzie | |
144 | @comment | |
145 | @comment Maintained by Martin Stjernholm and Alan Mackenzie <bug-cc-mode@gnu.org> | |
146 | @comment | |
147 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
148 | ||
149 | @comment Define an index for syntactic symbols. | |
4009494e | 150 | @defindex ss |
4009494e GM |
151 | |
152 | @comment Combine key, syntactic symbol and concept indices into one. | |
153 | @syncodeindex ss cp | |
154 | @syncodeindex ky cp | |
155 | ||
156 | @copying | |
157 | This manual is for CC Mode in Emacs. | |
158 | ||
ab422c4d | 159 | Copyright @copyright{} 1995--2013 Free Software Foundation, Inc. |
4009494e GM |
160 | |
161 | @quotation | |
162 | Permission is granted to copy, distribute and/or modify this document | |
6a2c4aec | 163 | under the terms of the GNU Free Documentation License, Version 1.3 or |
7b2d06e1 GM |
164 | any later version published by the Free Software Foundation; with no |
165 | Invariant Sections, with the Front-Cover texts being ``A GNU Manual'', | |
166 | and with the Back-Cover Texts as in (a) below. A copy of the license | |
167 | is included in the section entitled ``GNU Free Documentation License''. | |
4009494e | 168 | |
6f093307 | 169 | (a) The FSF's Back-Cover Text is: ``You have the freedom to copy and |
6bf430d1 | 170 | modify this GNU manual.'' |
4009494e GM |
171 | @end quotation |
172 | @end copying | |
173 | ||
174 | @comment Info directory entry for use by install-info. The indentation | |
175 | @comment here is by request from the FSF folks. | |
0c973505 | 176 | @dircategory Emacs editing modes |
4009494e | 177 | @direntry |
62e034c2 | 178 | * CC Mode: (ccmode). Emacs mode for editing C, C++, Objective-C, |
f9405d87 | 179 | Java, Pike, AWK, and CORBA IDL code. |
4009494e GM |
180 | @end direntry |
181 | ||
182 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
183 | @comment TeX title page | |
184 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
185 | ||
186 | @titlepage | |
187 | @sp 10 | |
188 | ||
47d42d81 | 189 | @center @titlefont{CC Mode 5.32} |
4009494e | 190 | @sp 2 |
605f02ee | 191 | @center A GNU Emacs mode for editing C and C-like languages |
4009494e GM |
192 | @sp 2 |
193 | @center Barry A. Warsaw, Martin Stjernholm, Alan Mackenzie | |
194 | ||
195 | @page | |
196 | @vskip 0pt plus 1filll | |
197 | @insertcopying | |
198 | ||
97af9a72 GM |
199 | This manual was generated from cc-mode.texi, which is distributed with Emacs, |
200 | or can be downloaded from @url{http://savannah.gnu.org/projects/emacs/}. | |
4009494e GM |
201 | @end titlepage |
202 | ||
203 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
204 | @comment The Top node contains the master menu for the Info file. | |
205 | @comment This appears only in the Info file, not the printed manual. | |
206 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
207 | ||
5dc584b5 KB |
208 | @summarycontents |
209 | @contents | |
210 | ||
4009494e GM |
211 | @node Top, Introduction, (dir), (dir) |
212 | @comment node-name, next, previous, up | |
213 | ||
5dc584b5 | 214 | @ifnottex |
4009494e GM |
215 | @top @ccmode{} |
216 | ||
217 | @ccmode{} is a GNU Emacs mode for editing files containing C, C++, | |
218 | Objective-C, Java, CORBA IDL (and the variants PSDL and CIDL), Pike | |
219 | and AWK code. It provides syntax-based indentation, font locking, and | |
220 | has several handy commands and some minor modes to make the editing | |
221 | easier. It does not provide tools to look up and navigate between | |
f99f1641 | 222 | functions, classes, etc.; there are other packages for that. |
5dc584b5 KB |
223 | |
224 | @insertcopying | |
225 | @end ifnottex | |
4009494e GM |
226 | |
227 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
228 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
229 | ||
230 | @menu | |
231 | * Introduction:: | |
232 | * Overview:: | |
233 | * Getting Started:: | |
234 | * Commands:: | |
235 | * Font Locking:: | |
236 | * Config Basics:: | |
237 | * Custom Filling and Breaking:: | |
238 | * Custom Auto-newlines:: | |
239 | * Clean-ups:: | |
240 | * Indentation Engine Basics:: | |
241 | * Customizing Indentation:: | |
242 | * Custom Macros:: | |
243 | * Odds and Ends:: | |
55f612f0 | 244 | * Sample Init File:: |
4009494e GM |
245 | * Performance Issues:: |
246 | * Limitations and Known Bugs:: | |
247 | * FAQ:: | |
248 | * Updating CC Mode:: | |
249 | * Mailing Lists and Bug Reports:: | |
250 | * GNU Free Documentation License:: | |
251 | * Command and Function Index:: | |
252 | * Variable Index:: | |
253 | * Concept and Key Index:: | |
254 | ||
255 | @detailmenu | |
256 | --- The Detailed Node Listing --- | |
257 | ||
258 | Commands | |
259 | ||
260 | * Indentation Commands:: | |
261 | * Comment Commands:: | |
262 | * Movement Commands:: | |
263 | * Filling and Breaking:: | |
264 | * Minor Modes:: | |
265 | * Electric Keys:: | |
266 | * Auto-newlines:: | |
267 | * Hungry WS Deletion:: | |
268 | * Subword Movement:: | |
269 | * Other Commands:: | |
270 | ||
271 | Font Locking | |
272 | ||
273 | * Font Locking Preliminaries:: | |
274 | * Faces:: | |
275 | * Doc Comments:: | |
276 | * AWK Mode Font Locking:: | |
277 | ||
278 | Configuration Basics | |
279 | ||
280 | * CC Hooks:: | |
281 | * Style Variables:: | |
282 | * Styles:: | |
283 | ||
284 | Styles | |
285 | ||
91af3942 PE |
286 | * Built-in Styles:: |
287 | * Choosing a Style:: | |
288 | * Adding Styles:: | |
289 | * Guessing the Style:: | |
290 | * File Styles:: | |
4009494e GM |
291 | |
292 | Customizing Auto-newlines | |
293 | ||
294 | * Hanging Braces:: | |
295 | * Hanging Colons:: | |
296 | * Hanging Semicolons and Commas:: | |
297 | ||
298 | Hanging Braces | |
299 | ||
300 | * Custom Braces:: | |
301 | ||
302 | Indentation Engine Basics | |
303 | ||
304 | * Syntactic Analysis:: | |
305 | * Syntactic Symbols:: | |
306 | * Indentation Calculation:: | |
307 | ||
308 | Syntactic Symbols | |
309 | ||
91af3942 PE |
310 | * Function Symbols:: |
311 | * Class Symbols:: | |
312 | * Conditional Construct Symbols:: | |
313 | * Switch Statement Symbols:: | |
314 | * Brace List Symbols:: | |
315 | * External Scope Symbols:: | |
316 | * Paren List Symbols:: | |
317 | * Literal Symbols:: | |
318 | * Multiline Macro Symbols:: | |
319 | * Objective-C Method Symbols:: | |
5cee0a9c | 320 | * Java Symbols:: |
91af3942 PE |
321 | * Statement Block Symbols:: |
322 | * K&R Symbols:: | |
4009494e GM |
323 | |
324 | Customizing Indentation | |
325 | ||
326 | * c-offsets-alist:: | |
327 | * Interactive Customization:: | |
328 | * Line-Up Functions:: | |
329 | * Custom Line-Up:: | |
330 | * Other Indentation:: | |
331 | ||
332 | Line-Up Functions | |
333 | ||
334 | * Brace/Paren Line-Up:: | |
335 | * List Line-Up:: | |
336 | * Operator Line-Up:: | |
337 | * Comment Line-Up:: | |
338 | * Misc Line-Up:: | |
339 | ||
536610a4 AM |
340 | Customizing Macros |
341 | ||
91af3942 PE |
342 | * Macro Backslashes:: |
343 | * Macros with ;:: | |
536610a4 | 344 | |
4009494e GM |
345 | @end detailmenu |
346 | @end menu | |
347 | ||
348 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
349 | @node Introduction, Overview, Top, Top | |
350 | @comment node-name, next, previous, up | |
351 | @chapter Introduction | |
352 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
353 | ||
354 | @cindex BOCM | |
355 | @cindex history | |
356 | @cindex awk-mode.el | |
357 | @cindex c-mode.el | |
358 | @cindex c++-mode.el | |
359 | ||
360 | Welcome to @ccmode{}, a GNU Emacs mode for editing files containing C, | |
361 | C++, Objective-C, Java, CORBA IDL (and the variants CORBA PSDL and | |
362 | CIDL), Pike and AWK code. This incarnation of the mode is descended | |
363 | from @file{c-mode.el} (also called ``Boring Old C Mode'' or BOCM | |
364 | @t{:-)}, @file{c++-mode.el} version 2, which Barry Warsaw had been | |
365 | maintaining since 1992, and @file{awk-mode.el}, a long neglected mode | |
366 | in the (X)Emacs base. | |
367 | ||
368 | Late in 1997, Martin Stjernholm joined Barry on the @ccmode{} | |
369 | Maintainers Team, and implemented the Pike support. In 2000 Martin | |
370 | took over as the sole maintainer. In 2001 Alan Mackenzie joined the | |
371 | team, implementing AWK support in version 5.30. @ccmode{} did not | |
f99f1641 | 372 | originally contain the font lock support for its languages; that |
4009494e GM |
373 | was added in version 5.30. |
374 | ||
375 | This manual describes @ccmode{} | |
376 | @comment The following line must appear on its own, so that the | |
47d42d81 | 377 | version 5.32. |
4009494e GM |
378 | @comment Release.py script can update the version number automatically |
379 | ||
380 | @ccmode{} supports the editing of K&R and ANSI C, C++, Objective-C, | |
381 | Java, CORBA's Interface Definition Language, Pike@footnote{A C-like | |
382 | scripting language with its roots in the LPC language used in some MUD | |
383 | engines. See @uref{http://pike.ida.liu.se/}.} and AWK files. In this | |
384 | way, you can easily set up consistent font locking and coding styles for | |
385 | use in editing all of these languages, although AWK is not yet as | |
386 | uniformly integrated as the other languages. | |
387 | ||
388 | @findex c-mode | |
389 | @findex c++-mode | |
390 | @findex objc-mode | |
391 | @findex java-mode | |
392 | @findex idl-mode | |
393 | @findex pike-mode | |
394 | @findex awk-mode | |
395 | Note that the name of this package is ``@ccmode{}'', but there is no top | |
396 | level @code{cc-mode} entry point. All of the variables, commands, and | |
397 | functions in @ccmode{} are prefixed with @code{c-@var{thing}}, and | |
398 | @code{c-mode}, @code{c++-mode}, @code{objc-mode}, @code{java-mode}, | |
399 | @code{idl-mode}, @code{pike-mode}, and @code{awk-mode} entry points are | |
400 | provided. This package is intended to be a replacement for | |
401 | @file{c-mode.el}, @file{c++-mode.el} and @file{awk-mode.el}. | |
402 | ||
403 | A special word of thanks goes to Krishna Padmasola for his work in | |
404 | converting the original @file{README} file to Texinfo format. I'd | |
405 | also like to thank all the @ccmode{} victims who help enormously | |
406 | during the early beta stages of @ccmode{}'s development. | |
407 | ||
408 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
409 | @node Overview, Getting Started, Introduction, Top | |
410 | @comment node-name, next, previous, up@cindex organization of the manual | |
411 | @chapter Overview of the Manual | |
412 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
413 | ||
414 | @noindent | |
415 | The manual starts with several introductory chapters (including this | |
416 | one). | |
417 | ||
418 | @noindent | |
419 | The next chunk of the manual describes the day to day @emph{use} of | |
420 | @ccmode{} (as contrasted with how to customize it). | |
421 | ||
422 | @itemize @bullet | |
423 | @item | |
424 | The chapter ``Commands'' describes in detail how to use (nearly) all | |
425 | of @ccmode{}'s features. There are extensive cross-references from | |
426 | here to the corresponding sections later in the manual which tell you | |
427 | how to customize these features. | |
428 | ||
429 | @item | |
430 | ``Font Locking'' describes how ``syntax highlighting'' is applied to | |
431 | your buffers. It is mainly background information and can be skipped | |
432 | over at a first reading. | |
433 | @end itemize | |
434 | ||
435 | @noindent | |
436 | The next chunk of the manual describes how to @emph{customize} | |
437 | @ccmode{}. Typically, an overview of a topic is given at the chapter | |
438 | level, then the sections and subsections describe the material in | |
439 | increasing detail. | |
440 | ||
441 | @itemize @bullet | |
442 | @item | |
443 | The chapter ``Configuration Basics'' tells you @emph{how} to write | |
f99f1641 | 444 | customizations: whether in hooks, in styles, in both, or in neither, |
4009494e GM |
445 | depending on your needs. It describes the @ccmode{} style system and |
446 | lists the standard styles that @ccmode{} supplies. | |
447 | ||
448 | @item | |
449 | The next few chapters describe in detail how to customize the various | |
450 | features of @ccmode{}. | |
451 | ||
452 | @item | |
453 | Finally, there is a sample @file{.emacs} fragment, which might help you | |
454 | in creating your own customization. | |
455 | @end itemize | |
456 | ||
457 | @noindent | |
458 | The manual ends with ``this and that'', things that don't fit cleanly | |
459 | into any of the previous chunks. | |
460 | ||
461 | @itemize @bullet | |
462 | @item | |
463 | Two chapters discuss the performance of @ccmode{} and known | |
464 | bugs/limitations. | |
465 | ||
466 | @item | |
467 | The FAQ contains a list of common problems and questions. | |
468 | ||
469 | @item | |
470 | The next two chapters tell you how to get in touch with the @ccmode{} | |
f99f1641 | 471 | project: whether for updating @ccmode{} or submitting bug reports. |
4009494e GM |
472 | @end itemize |
473 | ||
474 | @noindent | |
475 | Finally, there are the customary indices. | |
476 | ||
477 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
478 | @node Getting Started, Commands, Overview, Top | |
479 | @comment node-name, next, previous, up | |
480 | @chapter Getting Started | |
481 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
482 | ||
483 | If you got this version of @ccmode{} with Emacs or XEmacs, it should | |
484 | work just fine right out of the box. Note however that you might not | |
485 | have the latest @ccmode{} release and might want to upgrade your copy | |
486 | (see below). | |
487 | ||
7d11dd81 RS |
488 | You should probably start by skimming through the entire Commands chapter |
489 | (@pxref{Commands}) to get an overview of @ccmode{}'s capabilities. | |
4009494e GM |
490 | |
491 | After trying out some commands, you may dislike some aspects of | |
492 | @ccmode{}'s default configuration. Here is an outline of how to | |
493 | change some of the settings that newcomers to @ccmode{} most often | |
494 | want to change: | |
495 | ||
496 | @table @asis | |
497 | @item c-basic-offset | |
498 | This Lisp variable holds an integer, the number of columns @ccmode{} | |
499 | indents nested code. To set this value to 6, customize | |
500 | @code{c-basic-offset} or put this into your @file{.emacs}: | |
501 | ||
502 | @example | |
503 | (setq c-basic-offset 6) | |
504 | @end example | |
505 | ||
506 | @item The (indentation) style | |
507 | The basic ``shape'' of indentation created by @ccmode{}---by default, | |
508 | this is @code{gnu} style (except for Java and AWK buffers). A list of | |
509 | the available styles and their descriptions can be found in | |
510 | @ref{Built-in Styles}. A complete specification of the @ccmode{} | |
511 | style system, including how to create your own style, can be found in | |
512 | the chapter @ref{Styles}. To set your style to @code{linux}, either | |
513 | customize @code{c-default-style} or put this into your @file{.emacs}: | |
514 | ||
515 | @example | |
516 | (setq c-default-style '((java-mode . "java") | |
517 | (awk-mode . "awk") | |
518 | (other . "linux"))) | |
519 | @end example | |
520 | ||
521 | @item Electric Indentation | |
522 | Normally, when you type ``punctuation'' characters such as @samp{;} or | |
523 | @samp{@{}, @ccmode{} instantly reindents the current line. This can | |
524 | be disconcerting until you get used to it. To disable @dfn{electric | |
525 | indentation} in the current buffer, type @kbd{C-c C-l}. Type the same | |
526 | thing to enable it again. To have electric indentation disabled by | |
527 | default, put the following into your @file{.emacs} file@footnote{There | |
528 | is no ``easy customization'' facility for making this change.}: | |
529 | ||
530 | @example | |
531 | (setq-default c-electric-flag nil) | |
532 | @end example | |
533 | ||
534 | @noindent | |
535 | Details of this and other similar ``Minor Modes'' appear in the | |
536 | section @ref{Minor Modes}. | |
537 | ||
538 | @item Making the @key{RET} key indent the new line | |
539 | The standard Emacs binding for @key{RET} just adds a new line. If you | |
540 | want it to reindent the new line as well, rebind the key. Note that | |
541 | the action of rebinding would fail if the pertinent keymap didn't yet | |
542 | exist---we thus need to delay the action until after @ccmode{} has | |
543 | been loaded. Put the following code into your @file{.emacs}: | |
544 | ||
545 | @example | |
546 | (defun my-make-CR-do-indent () | |
547 | (define-key c-mode-base-map "\C-m" 'c-context-line-break)) | |
548 | (add-hook 'c-initialization-hook 'my-make-CR-do-indent) | |
549 | @end example | |
550 | ||
551 | @noindent | |
552 | This example demonstrates the use of a very powerful @ccmode{} (and | |
553 | Emacs) facility, the hook. The use of @ccmode{}'s hooks is described | |
554 | in @ref{CC Hooks}. | |
555 | @end table | |
556 | ||
557 | All these settings should occur in your @file{.emacs} @emph{before} | |
558 | any @ccmode{} buffers get loaded---in particular, before any call of | |
559 | @code{desktop-read}. | |
560 | ||
561 | As you get to know the mode better, you may want to make more | |
562 | ambitious changes to your configuration. For this, you should start | |
563 | reading the chapter @ref{Config Basics}. | |
564 | ||
565 | If you are upgrading an existing @ccmode{} installation, please see | |
566 | the @file{README} file for installation details. In particular, if | |
567 | you are going to be editing AWK files, @file{README} describes how to | |
568 | configure your (X)Emacs so that @ccmode{} will supersede the obsolete | |
569 | @code{awk-mode.el} which might have been supplied with your (X)Emacs. | |
570 | @ccmode{} might not work with older versions of Emacs or XEmacs. See | |
571 | the @ccmode{} release notes at @uref{http://cc-mode.sourceforge.net} | |
572 | for the latest information on Emacs version and package compatibility | |
573 | (@pxref{Updating CC Mode}). | |
574 | ||
575 | @deffn Command c-version | |
576 | @findex version (c-) | |
577 | You can find out what version of @ccmode{} you are using by visiting a C | |
578 | file and entering @kbd{M-x c-version RET}. You should see this message in | |
579 | the echo area: | |
580 | ||
581 | @example | |
582 | Using CC Mode version 5.XX | |
583 | @end example | |
584 | ||
585 | @noindent | |
586 | where @samp{XX} is the minor release number. | |
587 | @end deffn | |
588 | ||
589 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
590 | @node Commands, Font Locking, Getting Started, Top | |
591 | @comment node-name, next, previous, up | |
592 | @chapter Commands | |
593 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
594 | ||
595 | This chapter specifies all of CC Mode's commands, and thus contains | |
596 | nearly everything you need to know to @emph{use} @ccmode{} (as | |
597 | contrasted with configuring it). @dfn{Commands} here means both | |
598 | control key sequences and @dfn{electric keys}, these being characters | |
599 | such as @samp{;} which, as well as inserting themselves into the | |
600 | buffer, also do other things. | |
601 | ||
602 | You might well want to review | |
603 | @ifset XEMACS | |
604 | @ref{Lists,,,@emacsman{}, @emacsmantitle{}}, | |
605 | @end ifset | |
606 | @ifclear XEMACS | |
607 | @ref{Moving by Parens,,,@emacsman{}, @emacsmantitle{}}, | |
608 | @end ifclear | |
609 | which describes commands for moving around brace and parenthesis | |
610 | structures. | |
611 | ||
612 | ||
613 | @menu | |
614 | * Indentation Commands:: | |
615 | * Comment Commands:: | |
616 | * Movement Commands:: | |
617 | * Filling and Breaking:: | |
618 | * Minor Modes:: | |
619 | * Electric Keys:: | |
620 | * Auto-newlines:: | |
621 | * Hungry WS Deletion:: | |
622 | * Subword Movement:: | |
623 | * Other Commands:: | |
624 | @end menu | |
625 | ||
626 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
627 | @node Indentation Commands, Comment Commands, Commands, Commands | |
628 | @comment node-name, next, previous,up | |
629 | @section Indentation Commands | |
630 | @cindex indentation | |
631 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
632 | ||
633 | The following commands reindent C constructs. Note that when you | |
634 | change your coding style, either interactively or through some other | |
635 | means, your file does @emph{not} automatically get reindented. You | |
636 | will need to execute one of the following commands to see the effects | |
637 | of your changes. | |
638 | ||
639 | @cindex GNU indent program | |
640 | Also, variables like @code{c-hanging-*} and @code{c-cleanup-list} | |
641 | (@pxref{Custom Auto-newlines}) only affect how on-the-fly code is | |
642 | formatted. Changing the ``hanginess'' of a brace and then | |
643 | reindenting, will not move the brace to a different line. For this, | |
644 | you're better off getting an external program like GNU @code{indent}, | |
645 | which will rearrange brace location, amongst other things. | |
646 | ||
647 | Preprocessor directives are handled as syntactic whitespace from other | |
1df7defd | 648 | code, i.e., they can be interspersed anywhere without affecting the |
4009494e GM |
649 | indentation of the surrounding code, just like comments. |
650 | ||
651 | The code inside macro definitions is, by default, still analyzed | |
652 | syntactically so that you get relative indentation there just as you'd | |
653 | get if the same code was outside a macro. However, since there is no | |
1df7defd | 654 | hint about the syntactic context, i.e., whether the macro expands to an |
4009494e GM |
655 | expression, to some statements, or perhaps to whole functions, the |
656 | syntactic recognition can be wrong. @ccmode{} manages to figure it | |
657 | out correctly most of the time, though. | |
658 | ||
536610a4 AM |
659 | Some macros, when invoked, ''have their own semicolon''. To get the |
660 | next line indented correctly, rather than as a continuation line, | |
661 | @xref{Macros with ;}. | |
662 | ||
4009494e GM |
663 | Reindenting large sections of code can take a long time. When |
664 | @ccmode{} reindents a region of code, it is essentially equivalent to | |
665 | hitting @key{TAB} on every line of the region. | |
666 | ||
667 | These commands indent code: | |
668 | ||
669 | @table @asis | |
670 | @item @kbd{@key{TAB}} (@code{c-indent-command}) | |
671 | @kindex TAB | |
672 | @findex c-indent-command | |
673 | @findex indent-command (c-) | |
674 | This command indents the current line. That is all you need to know | |
675 | about it for normal use. | |
676 | ||
677 | @code{c-indent-command} does different things, depending on the | |
678 | setting of @code{c-syntactic-indentation} (@pxref{Indentation Engine | |
679 | Basics}): | |
680 | ||
681 | @itemize @bullet | |
682 | @item | |
683 | When it's non-@code{nil} (which it normally is), the command indents | |
684 | the line according to its syntactic context. With a prefix argument | |
685 | (@kbd{C-u @key{TAB}}), it will re-indent the entire | |
686 | expression@footnote{this is only useful for a line starting with a | |
687 | comment opener or an opening brace, parenthesis, or string quote.} | |
688 | that begins at the line's left margin. | |
689 | ||
690 | @item | |
691 | When it's @code{nil}, the command indents the line by an extra | |
692 | @code{c-basic-offset} columns. A prefix argument acts as a | |
693 | multiplier. A bare prefix (@kbd{C-u @key{TAB}}) is equivalent to -1, | |
694 | removing @code{c-basic-offset} columns from the indentation. | |
695 | @end itemize | |
696 | ||
697 | The precise behavior is modified by several variables: With | |
698 | @code{c-tab-always-indent}, you can make @key{TAB} insert whitespace | |
699 | in some circumstances---@code{c-insert-tab-function} then defines | |
700 | precisely what sort of ``whitespace'' this will be. Set the standard | |
701 | Emacs variable @code{indent-tabs-mode} to @code{t} if you want real | |
702 | @samp{tab} characters to be used in the indentation, to @code{nil} if | |
9879e263 | 703 | you want only spaces. @xref{Just Spaces,,,@emacsman{}, |
4009494e GM |
704 | @emacsmantitle{}}. |
705 | ||
706 | @defopt c-tab-always-indent | |
707 | @vindex tab-always-indent (c-) | |
708 | @cindex literal | |
709 | This variable modifies how @key{TAB} operates. | |
710 | @itemize @bullet | |
711 | @item | |
712 | When it is @code{t} (the default), @key{TAB} simply indents the | |
713 | current line. | |
714 | @item | |
715 | When it is @code{nil}, @key{TAB} (re)indents the line only if point is | |
716 | to the left of the first non-whitespace character on the line. | |
717 | Otherwise it inserts some whitespace (a tab or an equivalent number of | |
f99f1641 | 718 | spaces; see below) at point. |
4009494e GM |
719 | @item |
720 | With some other value, the line is reindented. Additionally, if point | |
721 | is within a string or comment, some whitespace is inserted. | |
722 | @end itemize | |
723 | @end defopt | |
724 | ||
725 | @defopt c-insert-tab-function | |
726 | @vindex insert-tab-function (c-) | |
727 | @findex tab-to-tab-stop | |
728 | When ``some whitespace'' is inserted as described above, what actually | |
729 | happens is that the function stored in @code{c-insert-tab-function} is | |
730 | called. Normally, this is @code{insert-tab}, which inserts a real tab | |
731 | character or the equivalent number of spaces (depending on | |
732 | @code{indent-tabs-mode}). Some people, however, set | |
733 | @code{c-insert-tab-function} to @code{tab-to-tab-stop} so as to get | |
734 | hard tab stops when indenting. | |
735 | @end defopt | |
736 | @end table | |
737 | ||
738 | @noindent | |
739 | The kind of indentation the next five commands do depends on the | |
740 | setting of @code{c-syntactic-indentation} (@pxref{Indentation Engine | |
741 | Basics}): | |
742 | @itemize @bullet | |
743 | @item | |
744 | when it is non-@code{nil} (the default), the commands indent lines | |
745 | according to their syntactic context; | |
746 | @item | |
747 | when it is @code{nil}, they just indent each line the same amount as | |
748 | the previous non-blank line. The commands that indent a region aren't | |
749 | very useful in this case. | |
750 | @end itemize | |
751 | ||
752 | @table @asis | |
753 | @item @kbd{C-j} (@code{newline-and-indent}) | |
754 | @kindex C-j | |
755 | @findex newline-and-indent | |
756 | Inserts a newline and indents the new blank line, ready to start | |
757 | typing. This is a standard (X)Emacs command. | |
758 | ||
759 | @item @kbd{C-M-q} (@code{c-indent-exp}) | |
760 | @kindex C-M-q | |
761 | @findex c-indent-exp | |
762 | @findex indent-exp (c-) | |
763 | Indents an entire balanced brace or parenthesis expression. Note that | |
764 | point must be on the opening brace or parenthesis of the expression | |
765 | you want to indent. | |
766 | ||
767 | @item @kbd{C-c C-q} (@code{c-indent-defun}) | |
768 | @kindex C-c C-q | |
769 | @findex c-indent-defun | |
770 | @findex indent-defun (c-) | |
771 | Indents the entire top-level function, class or macro definition | |
772 | encompassing point. It leaves point unchanged. This function can't be | |
773 | used to reindent a nested brace construct, such as a nested class or | |
774 | function, or a Java method. The top-level construct being reindented | |
1df7defd | 775 | must be complete, i.e., it must have both a beginning brace and an ending |
4009494e GM |
776 | brace. |
777 | ||
778 | @item @kbd{C-M-\} (@code{indent-region}) | |
779 | @kindex C-M-\ | |
780 | @findex indent-region | |
781 | Indents an arbitrary region of code. This is a standard Emacs command, | |
782 | tailored for C code in a @ccmode{} buffer. Note, of course, that point | |
783 | and mark must delineate the region you want to indent. | |
784 | ||
785 | @item @kbd{C-M-h} (@code{c-mark-function}) | |
786 | @kindex C-M-h | |
787 | @findex c-mark-function | |
788 | @findex mark-function (c-) | |
789 | While not strictly an indentation command, this is useful for marking | |
790 | the current top-level function or class definition as the current | |
791 | region. As with @code{c-indent-defun}, this command operates on | |
792 | top-level constructs, and can't be used to mark say, a Java method. | |
793 | @end table | |
794 | ||
795 | These variables are also useful when indenting code: | |
796 | ||
797 | @defopt indent-tabs-mode | |
798 | This is a standard Emacs variable that controls how line indentation | |
799 | is composed. When it's non-@code{nil}, tabs can be used in a line's | |
800 | indentation, otherwise only spaces are used. | |
801 | @end defopt | |
802 | ||
803 | @defopt c-progress-interval | |
804 | @vindex progress-interval (c-) | |
805 | When indenting large regions of code, this variable controls how often a | |
806 | progress message is displayed. Set this variable to @code{nil} to | |
807 | inhibit the progress messages, or set it to an integer which is how | |
808 | often (in seconds) progress messages are to be displayed. | |
809 | @end defopt | |
810 | ||
811 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
812 | @node Comment Commands, Movement Commands, Indentation Commands, Commands | |
813 | @comment node-name, next, previous, up | |
814 | @section Comment Commands | |
815 | @cindex comments (insertion of) | |
816 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
817 | ||
818 | @table @asis | |
819 | @item @kbd{C-c C-c} (@code{comment-region}) | |
820 | @kindex C-c C-c | |
821 | @findex comment-region | |
822 | This command comments out the lines that start in the region. With a | |
f99f1641 | 823 | negative argument, it does the opposite: it deletes the comment |
4009494e GM |
824 | delimiters from these lines. @xref{Multi-Line Comments,,, emacs, GNU |
825 | Emacs Manual}, for fuller details. @code{comment-region} isn't | |
f99f1641 | 826 | actually part of @ccmode{}; it is given a @ccmode{} binding for |
4009494e GM |
827 | convenience. |
828 | ||
829 | @item @kbd{M-;} (@code{comment-dwim} or @code{indent-for-comment} @footnote{The name of this command varies between (X)Emacs versions.}) | |
830 | @kindex M-; | |
831 | @findex comment-dwim | |
832 | @findex indent-for-comment | |
833 | Insert a comment at the end of the current line, if none is there | |
834 | already. Then reindent the comment according to @code{comment-column} | |
835 | @ifclear XEMACS | |
836 | (@pxref{Options for Comments,,, emacs, GNU Emacs Manual}) | |
837 | @end ifclear | |
838 | @ifset XEMACS | |
839 | (@pxref{Comments,,, xemacs, XEmacs User's Manual}) | |
840 | @end ifset | |
841 | and the variables below. Finally, position the point after the | |
842 | comment starter. @kbd{C-u M-;} kills any comment on the current line, | |
843 | together with any whitespace before it. This is a standard Emacs | |
844 | command, but @ccmode{} enhances it a bit with two variables: | |
845 | ||
846 | @defopt c-indent-comment-alist | |
847 | @vindex indent-comment-alist (c-) | |
848 | @vindex comment-column | |
849 | This style variable allows you to vary the column that @kbd{M-;} puts | |
850 | the comment at, depending on what sort of code is on the line, and | |
851 | possibly the indentation of any similar comment on the preceding line. | |
852 | It is an association list that maps different types of lines to | |
853 | actions describing how they should be handled. If a certain line type | |
854 | isn't present on the list then the line is indented to the column | |
855 | specified by @code{comment-column}. | |
856 | ||
857 | See the documentation string for a full description of this | |
858 | variable (use @kbd{C-h v c-indent-comment-alist}). | |
859 | @end defopt | |
860 | ||
861 | @defopt c-indent-comments-syntactically-p | |
862 | @vindex indent-comments-syntactically-p (c-) | |
863 | Normally, when this style variable is @code{nil}, @kbd{M-;} will | |
864 | indent comment-only lines according to @code{c-indent-comment-alist}, | |
865 | just as it does with lines where other code precede the comments. | |
866 | However, if you want it to act just like @key{TAB} for comment-only | |
867 | lines you can get that by setting | |
868 | @code{c-indent-comments-syntactically-p} to non-@code{nil}. | |
869 | ||
870 | If @code{c-indent-comments-syntactically-p} is non-@code{nil} then | |
871 | @code{c-indent-comment-alist} won't be consulted at all for comment-only | |
872 | lines. | |
873 | @end defopt | |
874 | @end table | |
875 | ||
876 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
877 | @node Movement Commands, Filling and Breaking, Comment Commands, Commands | |
878 | @comment node-name, next, previous, up | |
879 | @section Movement Commands | |
880 | @cindex movement | |
881 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
882 | ||
883 | @ccmode{} contains some useful commands for moving around in C code. | |
884 | ||
885 | @table @asis | |
886 | @item @kbd{C-M-a} (@code{c-beginning-of-defun}) | |
887 | @itemx @kbd{C-M-e} (@code{c-end-of-defun}) | |
888 | @findex c-beginning-of-defun | |
889 | @findex c-end-of-defun | |
020716e1 AM |
890 | @vindex c-defun-tactic |
891 | @vindex defun-tactic (c-) | |
4009494e GM |
892 | |
893 | Move to the beginning or end of the current or next function. Other | |
894 | constructs (such as a structs or classes) which have a brace block | |
895 | also count as ``functions'' here. To move over several functions, you | |
896 | can give these commands a repeat count. | |
897 | ||
898 | The start of a function is at its header. The end of the function is | |
899 | after its closing brace, or after the semicolon of a construct (such | |
900 | as a @code{struct}) which doesn't end at the brace. These two | |
901 | commands try to leave point at the beginning of a line near the actual | |
902 | start or end of the function. This occasionally causes point not to | |
903 | move at all. | |
904 | ||
020716e1 AM |
905 | By default, these commands will recognize functions contained within a |
906 | @dfn{declaration scope} such as a C++ @code{class} or @code{namespace} | |
907 | construct, should the point start inside it. If @ccmode fails to find | |
908 | function beginnings or ends inside the current declaration scope, it | |
909 | will search the enclosing scopes. If you want @ccmode to recognize | |
910 | functions only at the top level@footnote{this was @ccmode{}'s | |
40ba43b4 | 911 | behavior prior to version 5.32.}, set @code{c-defun-tactic} to |
020716e1 AM |
912 | @code{t}. |
913 | ||
4009494e GM |
914 | These functions are analogous to the Emacs built-in commands |
915 | @code{beginning-of-defun} and @code{end-of-defun}, except they | |
916 | eliminate the constraint that the top-level opening brace of the defun | |
917 | must be in column zero. See @ref{Defuns,,,@emacsman{}, | |
918 | @emacsmantitle{}}, for more information. | |
919 | ||
920 | @item @kbd{C-M-a} (AWK Mode) (@code{c-awk-beginning-of-defun}) | |
921 | @itemx @kbd{C-M-e} (AWK Mode) (@code{c-awk-end-of-defun}) | |
922 | @kindex C-M-a (AWK Mode) | |
923 | @kindex C-M-e (AWK Mode) | |
924 | @findex c-awk-beginning-of-defun | |
925 | @findex awk-beginning-of-defun (c-) | |
926 | @findex c-awk-end-of-defun | |
927 | @findex awk-end-of-defun (c-) | |
928 | Move to the beginning or end of the current or next AWK defun. These | |
929 | commands can take prefix-arguments, their functionality being entirely | |
930 | equivalent to @code{beginning-of-defun} and @code{end-of-defun}. | |
931 | ||
932 | AWK Mode @dfn{defuns} are either pattern/action pairs (either of which | |
933 | might be implicit) or user defined functions. Having the @samp{@{} and | |
934 | @samp{@}} (if there are any) in column zero, as is suggested for some | |
935 | modes, is neither necessary nor helpful in AWK mode. | |
936 | ||
937 | @item @kbd{M-a} (@code{c-beginning-of-statement}) | |
938 | @itemx @kbd{M-e} (@code{c-end-of-statement}) | |
939 | @kindex M-a | |
940 | @kindex M-e | |
941 | @findex c-beginning-of-statement | |
942 | @findex c-end-of-statement | |
943 | @findex beginning-of-statement (c-) | |
944 | @findex end-of-statement (c-) | |
945 | Move to the beginning or end of the innermost C statement. If point | |
946 | is already there, move to the next beginning or end of a statement, | |
947 | even if that means moving into a block. (Use @kbd{C-M-b} or | |
948 | @kbd{C-M-f} to move over a balanced block.) A prefix argument @var{n} | |
949 | means move over @var{n} statements. | |
950 | ||
951 | If point is within or next to a comment or a string which spans more | |
952 | than one line, these commands move by sentences instead of statements. | |
953 | ||
954 | When called from a program, these functions take three optional | |
955 | arguments: the repetition count, a buffer position limit which is the | |
956 | farthest back to search for the syntactic context, and a flag saying | |
957 | whether to do sentence motion in or near comments and multiline | |
958 | strings. | |
959 | ||
960 | @item @kbd{C-c C-u} (@code{c-up-conditional}) | |
961 | @kindex C-c C-u | |
962 | @findex c-up-conditional | |
963 | @findex up-conditional (c-) | |
964 | Move back to the containing preprocessor conditional, leaving the mark | |
965 | behind. A prefix argument acts as a repeat count. With a negative | |
966 | argument, move forward to the end of the containing preprocessor | |
967 | conditional. | |
968 | ||
969 | @samp{#elif} is treated like @samp{#else} followed by @samp{#if}, so the | |
970 | function stops at them when going backward, but not when going | |
971 | forward. | |
972 | ||
973 | This key sequence is not bound in AWK Mode, which doesn't have | |
974 | preprocessor statements. | |
975 | ||
976 | @item @kbd{M-x c-up-conditional-with-else} | |
977 | @findex c-up-conditional-with-else | |
978 | @findex up-conditional-with-else (c-) | |
979 | A variety of @code{c-up-conditional} that also stops at @samp{#else} | |
980 | lines. Normally those lines are ignored. | |
981 | ||
982 | @item @kbd{M-x c-down-conditional} | |
983 | @findex c-down-conditional | |
984 | @findex down-conditional (c-) | |
985 | Move forward into the next nested preprocessor conditional, leaving | |
986 | the mark behind. A prefix argument acts as a repeat count. With a | |
987 | negative argument, move backward into the previous nested preprocessor | |
988 | conditional. | |
989 | ||
990 | @samp{#elif} is treated like @samp{#else} followed by @samp{#if}, so the | |
991 | function stops at them when going forward, but not when going backward. | |
992 | ||
993 | @item @kbd{M-x c-down-conditional-with-else} | |
994 | @findex c-down-conditional-with-else | |
995 | @findex down-conditional-with-else (c-) | |
996 | A variety of @code{c-down-conditional} that also stops at @samp{#else} | |
997 | lines. Normally those lines are ignored. | |
998 | ||
999 | @item @kbd{C-c C-p} (@code{c-backward-conditional}) | |
1000 | @itemx @kbd{C-c C-n} (@code{c-forward-conditional}) | |
1001 | @kindex C-c C-p | |
1002 | @kindex C-c C-n | |
1003 | @findex c-backward-conditional | |
1004 | @findex c-forward-conditional | |
1005 | @findex backward-conditional (c-) | |
1006 | @findex forward-conditional (c-) | |
1007 | Move backward or forward across a preprocessor conditional, leaving | |
1008 | the mark behind. A prefix argument acts as a repeat count. With a | |
1009 | negative argument, move in the opposite direction. | |
1010 | ||
1011 | These key sequences are not bound in AWK Mode, which doesn't have | |
1012 | preprocessor statements. | |
1013 | ||
1014 | @item @kbd{M-x c-backward-into-nomenclature} | |
1015 | @itemx @kbd{M-x c-forward-into-nomenclature} | |
1016 | @findex c-backward-into-nomenclature | |
1017 | @findex c-forward-into-nomenclature | |
1018 | @findex backward-into-nomenclature (c-) | |
1019 | @findex forward-into-nomenclature (c-) | |
1020 | A popular programming style, especially for object-oriented languages | |
1021 | such as C++ is to write symbols in a mixed case format, where the | |
1022 | first letter of each word is capitalized, and not separated by | |
1df7defd | 1023 | underscores. E.g., @samp{SymbolsWithMixedCaseAndNoUnderlines}. |
4009494e GM |
1024 | |
1025 | These commands move backward or forward to the beginning of the next | |
1026 | capitalized word. With prefix argument @var{n}, move @var{n} times. | |
1027 | If @var{n} is negative, move in the opposite direction. | |
1028 | ||
1029 | Note that these two commands have been superseded by | |
aaef4f91 | 1030 | @code{subword-mode}, which you should use instead. @xref{Subword |
4009494e GM |
1031 | Movement}. They might be removed from a future release of @ccmode{}. |
1032 | @end table | |
1033 | ||
1034 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1035 | @node Filling and Breaking, Minor Modes, Movement Commands, Commands | |
1036 | @comment node-name, next, previous, up | |
1037 | @section Filling and Line Breaking Commands | |
1038 | @cindex text filling | |
1039 | @cindex line breaking | |
1040 | @cindex comment handling | |
1041 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1042 | ||
1043 | Since there's a lot of normal text in comments and string literals, | |
1044 | @ccmode{} provides features to edit these like in text mode. The goal | |
1df7defd | 1045 | is to do it seamlessly, i.e., you can use auto fill mode, sentence and |
4009494e GM |
1046 | paragraph movement, paragraph filling, adaptive filling etc. wherever |
1047 | there's a piece of normal text without having to think much about it. | |
1048 | @ccmode{} keeps the indentation, fixes suitable comment line prefixes, | |
1049 | and so on. | |
1050 | ||
1051 | You can configure the exact way comments get filled and broken, and | |
1052 | where Emacs does auto-filling (see @pxref{Custom Filling and | |
1053 | Breaking}). Typically, the style system (@pxref{Styles}) will have | |
1054 | set this up for you, so you probably won't have to bother. | |
1055 | ||
1056 | @findex auto-fill-mode | |
1057 | @cindex Auto Fill mode | |
1058 | @cindex paragraph filling | |
1059 | Line breaks are by default handled (almost) the same regardless of | |
9879e263 | 1060 | whether they are made by auto fill mode (@pxref{Auto |
1df7defd | 1061 | Fill,,,@emacsman{}, @emacsmantitle{}}), by paragraph filling (e.g., with |
4009494e GM |
1062 | @kbd{M-q}), or explicitly with @kbd{M-j} or similar methods. In |
1063 | string literals, the new line gets the same indentation as the | |
1064 | previous nonempty line.@footnote{You can change this default by | |
1065 | setting the @code{string} syntactic symbol (@pxref{Syntactic Symbols} | |
1066 | and @pxref{Customizing Indentation})}. | |
1067 | ||
1068 | @table @asis | |
1069 | @item @kbd{M-q} (@code{c-fill-paragraph}) | |
1070 | @kindex M-q | |
1071 | @findex c-fill-paragraph | |
1072 | @findex fill-paragraph (c-) | |
1073 | @cindex Javadoc markup | |
1074 | @cindex Pike autodoc markup | |
1075 | This command fills multiline string literals and both block | |
1076 | and line style comments. In Java buffers, the Javadoc markup words | |
1077 | are recognized as paragraph starters. The line oriented Pike autodoc | |
1078 | markup words are recognized in the same way in Pike mode. | |
1079 | ||
1080 | The formatting of the starters (@code{/*}) and enders (@code{*/}) of | |
1081 | block comments are kept as they were before the filling. I.e., if | |
1082 | either the starter or ender were on a line of its own, then it stays | |
1083 | on its own line; conversely, if the delimiter has comment text on its | |
1084 | line, it keeps at least one word of that text with it on the line. | |
1085 | ||
1086 | This command is the replacement for @code{fill-paragraph} in @ccmode{} | |
1087 | buffers. | |
1088 | ||
1089 | @item @kbd{M-j} (@code{c-indent-new-comment-line}) | |
1090 | @kindex M-j | |
1091 | @findex c-indent-new-comment-line | |
1092 | @findex indent-new-comment-line (c-) | |
1093 | This breaks the current line at point and indents the new line. If | |
1094 | point was in a comment, the new line gets the proper comment line | |
1095 | prefix. If point was inside a macro, a backslash is inserted before | |
1096 | the line break. It is the replacement for | |
1097 | @code{indent-new-comment-line}. | |
1098 | ||
1099 | @item @kbd{M-x c-context-line-break} | |
1100 | @findex c-context-line-break | |
1101 | @findex context-line-break (c-) | |
1102 | Insert a line break suitable to the context: If the point is inside a | |
1103 | comment, the new line gets the suitable indentation and comment line | |
1104 | prefix like @code{c-indent-new-comment-line}. In normal code it's | |
1105 | indented like @code{newline-and-indent} would do. In macros it acts | |
1106 | like @code{newline-and-indent} but additionally inserts and optionally | |
1107 | aligns the line ending backslash so that the macro remains unbroken. | |
1108 | @xref{Custom Macros}, for details about the backslash alignment. In a | |
1109 | string, a backslash is inserted only if the string is within a | |
1110 | macro@footnote{In GCC, unescaped line breaks within strings are | |
1111 | valid.}. | |
1112 | ||
1113 | This function is not bound to a key by default, but it's intended to be | |
1114 | used on the @kbd{RET} key. If you like the behavior of | |
1115 | @code{newline-and-indent} on @kbd{RET}, you should consider switching to | |
55f612f0 | 1116 | this function. @xref{Sample Init File}. |
4009494e GM |
1117 | |
1118 | @item @kbd{M-x c-context-open-line} | |
1119 | @findex c-context-open-line | |
1120 | @findex context-open-line (c-) | |
1121 | This is to @kbd{C-o} (@kbd{M-x open-line}) as | |
1df7defd | 1122 | @code{c-context-line-break} is to @kbd{RET}. I.e., it works just like |
4009494e GM |
1123 | @code{c-context-line-break} but leaves the point before the inserted |
1124 | line break. | |
1125 | @end table | |
1126 | ||
1127 | ||
1128 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1129 | @node Minor Modes, Electric Keys, Filling and Breaking, Commands | |
1130 | @comment node-name, next, previous, up | |
1131 | @section Minor Modes | |
1132 | @cindex Minor Modes | |
1133 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1134 | ||
1135 | @ccmode{} contains several minor-mode-like features that you might | |
1136 | find useful while writing new code or editing old code: | |
1137 | ||
1138 | @table @asis | |
1139 | @item electric mode | |
1140 | When this is enabled, certain visible characters cause reformatting as | |
1141 | they are typed. This is normally helpful, but can be a nuisance when | |
1142 | editing chaotically formatted code. It can also be disconcerting, | |
1143 | especially for users who are new to @ccmode{}. | |
1144 | @item auto-newline mode | |
1145 | This automatically inserts newlines where you'd probably want to type | |
1df7defd | 1146 | them yourself, e.g., after typing @samp{@}}s. Its action is suppressed |
4009494e GM |
1147 | when electric mode is disabled. |
1148 | @item hungry-delete mode | |
1149 | This lets you delete a contiguous block of whitespace with a single | |
f99f1641 | 1150 | key: for example, the newline and indentation just inserted by |
4009494e GM |
1151 | auto-newline when you want to back up and write a comment after the |
1152 | last statement. | |
1153 | @item subword mode | |
1154 | This mode makes basic word movement commands like @kbd{M-f} | |
1155 | (@code{forward-word}) and @kbd{M-b} (@code{backward-word}) treat the | |
1156 | parts of sillycapsed symbols as different words. | |
1df7defd | 1157 | E.g., @samp{NSGraphicsContext} is treated as three words @samp{NS}, |
4009494e GM |
1158 | @samp{Graphics}, and @samp{Context}. |
1159 | @item syntactic-indentation mode | |
1160 | When this is enabled (which it normally is), indentation commands such | |
1161 | as @kbd{C-j} indent lines of code according to their syntactic | |
1162 | structure. Otherwise, a line is simply indented to the same level as | |
1163 | the previous one and @kbd{@key{TAB}} adjusts the indentation in steps | |
1164 | of `c-basic-offset'. | |
1165 | @end table | |
1166 | ||
1167 | Full details on how these minor modes work are at @ref{Electric Keys}, | |
1168 | @ref{Auto-newlines}, @ref{Hungry WS Deletion}, @ref{Subword Movement}, | |
1169 | and @ref{Indentation Engine Basics}. | |
1170 | ||
1171 | You can toggle each of these minor modes on and off, and you can | |
c5e87d10 | 1172 | configure @ccmode{} so that it starts up with your favorite |
55f612f0 | 1173 | combination of them (@pxref{Sample Init File}). By default, when |
4009494e GM |
1174 | you initialize a buffer, electric mode and syntactic-indentation mode |
1175 | are enabled but the other two modes are disabled. | |
1176 | ||
1177 | @ccmode{} displays the current state of the first four of these minor | |
1178 | modes on the modeline by appending letters to the major mode's name, | |
f99f1641 | 1179 | one letter for each enabled minor mode: @samp{l} for electric mode, |
4009494e GM |
1180 | @samp{a} for auto-newline mode, @samp{h} for hungry delete mode, and |
1181 | @samp{w} for subword mode. If all these modes were enabled, you'd see | |
1182 | @samp{C/lahw}@footnote{The @samp{C} would be replaced with the name of | |
1183 | the language in question for the other languages @ccmode{} supports.}. | |
1184 | ||
1185 | Here are the commands to toggle these modes: | |
1186 | ||
1187 | @table @asis | |
1188 | @item @kbd{C-c C-l} (@code{c-toggle-electric-state}) | |
1189 | @kindex C-c C-l | |
1190 | @findex c-toggle-electric-state | |
1191 | @findex toggle-electric-state (c-) | |
1192 | Toggle electric minor mode. When the command turns the mode off, it | |
1193 | also suppresses auto-newline mode. | |
1194 | ||
1195 | @item @kbd{C-c C-a} (@code{c-toggle-auto-newline}) | |
1196 | @kindex C-c C-a | |
1197 | @findex c-toggle-auto-newline | |
1198 | @findex toggle-auto-newline (c-) | |
1199 | Toggle auto-newline minor mode. When the command turns the mode on, | |
1200 | it also enables electric minor mode. | |
1201 | ||
1202 | @item @kbd{M-x c-toggle-hungry-state}@footnote{Prior to @ccmode{} 5.31, this command was bound to @kbd{C-c C-d}.} | |
1203 | @findex c-toggle-hungry-state | |
1204 | @findex toggle-hungry-state (c-) | |
1205 | Toggle hungry-delete minor mode. | |
1206 | ||
1207 | @item @kbd{M-x c-toggle-auto-hungry-state}@footnote{Prior to @ccmode{} 5.31, this command was bound to @kbd{C-c C-t}.} | |
1208 | @findex c-toggle-auto-hungry-state | |
1209 | @findex toggle-auto-hungry-state (c-) | |
1210 | Toggle both auto-newline and hungry delete minor modes. | |
1211 | ||
aaef4f91 | 1212 | @item @kbd{C-c C-w} (@code{M-x subword-mode}) |
4009494e | 1213 | @kindex C-c C-w |
aaef4f91 | 1214 | @findex subword-mode |
4009494e GM |
1215 | Toggle subword mode. |
1216 | ||
1217 | @item @kbd{M-x c-toggle-syntactic-indentation} | |
1218 | @findex c-toggle-syntactic-indentation | |
1219 | @findex toggle-syntactic-indentation (c-) | |
1220 | Toggle syntactic-indentation mode. | |
1221 | @end table | |
1222 | ||
1223 | Common to all the toggle functions above is that if they are called | |
1224 | programmatically, they take an optional numerical argument. A | |
1225 | positive value will turn on the minor mode (or both of them in the | |
1226 | case of @code{c-toggle-auto-hungry-state}) and a negative value will | |
1227 | turn it (or them) off. | |
1228 | ||
1229 | ||
1230 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1231 | @node Electric Keys, Auto-newlines, Minor Modes, Commands | |
1232 | @comment node-name, next, previous, up | |
1233 | @section Electric Keys and Keywords | |
1234 | @cindex electric characters | |
1235 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1236 | ||
f99f1641 | 1237 | Most punctuation keys provide @dfn{electric} behavior: as well as |
4009494e GM |
1238 | inserting themselves they perform some other action, such as |
1239 | reindenting the line. This reindentation saves you from having to | |
1240 | reindent a line manually after typing, say, a @samp{@}}. A few | |
1241 | keywords, such as @code{else}, also trigger electric action. | |
1242 | ||
a1bf7841 | 1243 | You can inhibit the electric behavior described here by disabling |
4009494e GM |
1244 | electric minor mode (@pxref{Minor Modes}). |
1245 | ||
1246 | Common to all these keys is that they only behave electrically when | |
1247 | used in normal code (as contrasted with getting typed in a string | |
1248 | literal or comment). Those which cause re-indentation do so only when | |
1249 | @code{c-syntactic-indentation} has a non-@code{nil} value (which it | |
1250 | does by default). | |
1251 | ||
1252 | These keys and keywords are: | |
1253 | @c ACM, 2004/8/24: c-electric-pound doesn't check c-s-i: this is more | |
1254 | @c like a bug in the code than a bug in this document. It'll get | |
1255 | @c fixed in the code sometime. | |
1256 | ||
1257 | @table @kbd | |
1258 | @item # | |
1259 | @kindex # | |
1260 | @findex c-electric-pound | |
1261 | @findex electric-pound (c-) | |
1262 | @vindex c-electric-pound-behavior | |
1263 | @vindex electric-pound-behavior (c-) | |
1264 | Pound (bound to @code{c-electric-pound}) is electric when typed as the | |
1265 | first non-whitespace character on a line and not within a macro | |
1266 | definition. In this case, the variable @code{c-electric-pound-behavior} | |
1267 | is consulted for the electric behavior. This variable takes a list | |
1268 | value, although the only element currently defined is @code{alignleft}, | |
1269 | which tells this command to force the @samp{#} character into column | |
1270 | zero. This is useful for entering preprocessor macro definitions. | |
1271 | ||
1272 | Pound is not electric in AWK buffers, where @samp{#} starts a comment, | |
1273 | and is bound to @code{self-insert-command} like any typical printable | |
1274 | character. | |
1275 | @c ACM, 2004/8/24: Change this (and the code) to do AWK comment | |
1276 | @c reindentation. | |
1277 | ||
1278 | @item * | |
1279 | @kindex * | |
1280 | @itemx / | |
1281 | @kindex / | |
1282 | @findex c-electric-star | |
1283 | @findex electric-star (c-) | |
1284 | @findex c-electric-slash | |
1285 | @findex electric-slash (c-) | |
1286 | A star (bound to @code{c-electric-star}) or a slash | |
1287 | (@code{c-electric-slash}) causes reindentation when you type it as the | |
1288 | second component of a C style block comment opener (@samp{/*}) or a | |
1289 | C++ line comment opener (@samp{//}) respectively, but only if the | |
1df7defd | 1290 | comment opener is the first thing on the line (i.e., there's only |
4009494e GM |
1291 | whitespace before it). |
1292 | ||
1293 | Additionally, you can configure @ccmode{} so that typing a slash at | |
1294 | the start of a line within a block comment will terminate the | |
1295 | comment. You don't need to have electric minor mode enabled to get | |
a1bf7841 | 1296 | this behavior. @xref{Clean-ups}. |
4009494e GM |
1297 | |
1298 | In AWK mode, @samp{*} and @samp{/} do not delimit comments and are not | |
1299 | electric. | |
1300 | ||
1301 | @item < | |
1302 | @kindex < | |
1303 | @itemx > | |
1304 | @kindex > | |
1305 | @findex c-electric-lt-gt | |
1306 | @findex electric-lt-gt (c-) | |
1307 | A less-than or greater-than sign (bound to @code{c-electric-lt-gt}) is | |
1308 | electric in two circumstances: when it is an angle bracket in a C++ | |
1309 | @samp{template} declaration (and similar constructs in other | |
1310 | languages) and when it is the second of two @kbd{<} or @kbd{>} | |
1311 | characters in a C++ style stream operator. In either case, the line | |
1312 | is reindented. Angle brackets in C @samp{#include} directives are not | |
1313 | electric. | |
1314 | ||
1315 | @item ( | |
1316 | @kindex ( | |
1317 | @itemx ) | |
1318 | @kindex ) | |
1319 | @findex c-electric-paren | |
1320 | @findex electric-paren (c-) | |
1321 | The normal parenthesis characters @samp{(} and @samp{)} (bound to | |
1322 | @code{c-electric-paren}) reindent the current line. This is useful | |
1323 | for getting the closing parenthesis of an argument list aligned | |
1324 | automatically. | |
1325 | ||
1326 | You can also configure @ccmode{} to insert a space automatically | |
1327 | between a function name and the @samp{(} you've just typed, and to | |
1328 | remove it automatically after typing @samp{)}, should the argument | |
1329 | list be empty. You don't need to have electric minor mode enabled to | |
1330 | get these actions. @xref{Clean-ups}. | |
1331 | ||
1332 | @item @{ | |
1333 | @kindex @{ | |
1334 | @itemx @} | |
1335 | @kindex @} | |
1336 | @findex c-electric-brace | |
1337 | @findex electric-brace (c-) | |
1338 | Typing a brace (bound to @code{c-electric-brace}) reindents the | |
1339 | current line. Also, one or more newlines might be inserted if | |
1340 | auto-newline minor mode is enabled. @xref{Auto-newlines}. | |
1341 | Additionally, you can configure @ccmode{} to compact excess whitespace | |
1342 | inserted by auto-newline mode in certain circumstances. | |
1343 | @xref{Clean-ups}. | |
1344 | ||
1345 | @item : | |
1346 | @kindex : | |
1347 | @findex c-electric-colon | |
1348 | @findex electric-colon (c-) | |
1349 | Typing a colon (bound to @code{c-electric-colon}) reindents the | |
1350 | current line. Additionally, one or more newlines might be inserted if | |
1351 | auto-newline minor mode is enabled. @xref{Auto-newlines}. If you | |
1352 | type a second colon immediately after such an auto-newline, by default | |
1353 | the whitespace between the two colons is removed, leaving a C++ scope | |
1354 | operator. @xref{Clean-ups}. | |
1355 | ||
1356 | If you prefer, you can insert @samp{::} in a single operation, | |
1357 | avoiding all these spurious reindentations, newlines, and clean-ups. | |
1358 | @xref{Other Commands}. | |
1359 | ||
1360 | @item ; | |
1361 | @kindex ; | |
1362 | @itemx , | |
1363 | @kindex , | |
1364 | @findex c-electric-semi&comma | |
1365 | @findex electric-semi&comma (c-) | |
1366 | Typing a semicolon or comma (bound to @code{c-electric-semi&comma}) | |
1367 | reindents the current line. Also, a newline might be inserted if | |
1368 | auto-newline minor mode is enabled. @xref{Auto-newlines}. | |
1369 | Additionally, you can configure @ccmode{} so that when auto-newline | |
1370 | has inserted whitespace after a @samp{@}}, it will be removed again | |
1371 | when you type a semicolon or comma just after it. @xref{Clean-ups}. | |
1372 | ||
1373 | @end table | |
1374 | ||
1375 | @deffn Command c-electric-continued-statement | |
1376 | @findex electric-continued-statement (c-) | |
1377 | ||
1378 | Certain keywords are electric, causing reindentation when they are | |
1379 | preceded only by whitespace on the line. The keywords are those that | |
1380 | continue an earlier statement instead of starting a new one: | |
1381 | @code{else}, @code{while}, @code{catch} (only in C++ and Java) and | |
1382 | @code{finally} (only in Java). | |
1383 | ||
1384 | An example: | |
1385 | ||
1386 | @example | |
1387 | @group | |
1388 | for (i = 0; i < 17; i++) | |
1389 | if (a[i]) | |
1390 | res += a[i]->offset; | |
1391 | else | |
1392 | @end group | |
1393 | @end example | |
1394 | ||
1395 | Here, the @code{else} should be indented like the preceding @code{if}, | |
1396 | since it continues that statement. @ccmode{} will automatically | |
1397 | reindent it after the @code{else} has been typed in full, since only | |
1398 | then is it possible to decide whether it's a new statement or a | |
1399 | continuation of the preceding @code{if}. | |
1400 | ||
1401 | @vindex abbrev-mode | |
1402 | @findex abbrev-mode | |
1403 | @cindex Abbrev mode | |
9879e263 | 1404 | @ccmode{} uses Abbrev mode (@pxref{Abbrevs,,,@emacsman{}, @emacsmantitle{}}) |
4009494e GM |
1405 | to accomplish this. It's therefore turned on by default in all language |
1406 | modes except IDL mode, since CORBA IDL doesn't have any statements. | |
1407 | @end deffn | |
1408 | ||
1409 | ||
1410 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1411 | @node Auto-newlines, Hungry WS Deletion, Electric Keys, Commands | |
1412 | @comment node-name, next, previous, up | |
1413 | @section Auto-newline Insertion | |
1414 | @cindex auto-newline | |
1415 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1416 | ||
1417 | When you have @dfn{Auto-newline minor mode} enabled (@pxref{Minor | |
1418 | Modes}), @ccmode{} inserts newlines for you automatically (in certain | |
1419 | syntactic contexts) when you type a left or right brace, a colon, a | |
1420 | semicolon, or a comma. Sometimes a newline appears before the | |
1421 | character you type, sometimes after it, sometimes both. | |
1422 | ||
1423 | Auto-newline only triggers when the following conditions hold: | |
1424 | ||
1425 | @itemize @bullet | |
1426 | @item | |
1427 | Auto-newline minor mode is enabled, as evidenced by the indicator | |
1df7defd | 1428 | @samp{a} after the mode name on the modeline (e.g., @samp{C/a} or |
4009494e GM |
1429 | @samp{C/la}). |
1430 | ||
1431 | @item | |
1432 | The character was typed at the end of a line, or with only whitespace | |
1433 | after it, and possibly a @samp{\} escaping the newline. | |
1434 | ||
1435 | @item | |
1436 | The character is not on its own line already. (This applies only to | |
1437 | insertion of a newline @emph{before} the character.) | |
1438 | ||
1439 | @item | |
1440 | @cindex literal | |
1441 | @cindex syntactic whitespace | |
1442 | The character was not typed inside of a literal @footnote{A | |
1443 | @dfn{literal} is defined as any comment, string, or preprocessor macro | |
1444 | definition. These constructs are also known as @dfn{syntactic | |
1445 | whitespace} since they are usually ignored when scanning C code.}. | |
1446 | ||
1447 | @item | |
1df7defd | 1448 | No numeric argument was supplied to the command (i.e., it was typed as |
4009494e GM |
1449 | normal, with no @kbd{C-u} prefix). |
1450 | @end itemize | |
1451 | ||
1452 | You can configure the precise circumstances in which newlines get | |
1453 | inserted (see @pxref{Custom Auto-newlines}). Typically, the style | |
1454 | system (@pxref{Styles}) will have set this up for you, so you probably | |
1455 | won't have to bother. | |
1456 | ||
1457 | Sometimes @ccmode{} inserts an auto-newline where you don't want one, | |
1458 | such as after a @samp{@}} when you're about to type a @samp{;}. | |
1459 | Hungry deletion can help here (@pxref{Hungry WS Deletion}), or you can | |
1460 | activate an appropriate @dfn{clean-up}, which will remove the excess | |
1461 | whitespace after you've typed the @samp{;}. See @ref{Clean-ups} for a | |
1462 | full description. See also @ref{Electric Keys} for a summary of | |
1463 | clean-ups listed by key. | |
1464 | ||
1465 | ||
1466 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1467 | @node Hungry WS Deletion, Subword Movement, Auto-newlines, Commands | |
1468 | @comment node-name, next, previous, up | |
1469 | @section Hungry Deletion of Whitespace | |
1470 | @cindex hungry-deletion | |
1471 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1472 | ||
1473 | If you want to delete an entire block of whitespace at point, you can | |
1474 | use @dfn{hungry deletion}. This deletes all the contiguous whitespace | |
1475 | either before point or after point in a single operation. | |
1476 | ``Whitespace'' here includes tabs and newlines, but not comments or | |
1477 | preprocessor commands. Hungry deletion can markedly cut down on the | |
1478 | number of times you have to hit deletion keys when, for example, | |
1479 | you've made a mistake on the preceding line and have already pressed | |
1480 | @kbd{C-j}. | |
1481 | ||
1482 | Hungry deletion is a simple feature that some people find extremely | |
1483 | useful. In fact, you might find yourself wanting it in @strong{all} | |
1484 | your editing modes! | |
1485 | ||
1486 | Loosely speaking, in what follows, @dfn{@key{DEL}} means ``the | |
1487 | backspace key'' and @dfn{@key{DELETE}} means ``the forward delete | |
1488 | key''. This is discussed in more detail below. | |
1489 | ||
1490 | There are two different ways you can use hungry deletion: | |
1491 | ||
1492 | @table @asis | |
1493 | @item Using @dfn{Hungry Delete Mode} with @kbd{@key{DEL}} and @kbd{C-d} | |
1494 | Here you toggle Hungry Delete minor mode with @kbd{M-x | |
1495 | c-toggle-hungry-state}@footnote{Prior to @ccmode{} 5.31, this command | |
1496 | was bound to @kbd{C-c C-d}. @kbd{C-c C-d} is now the default binding | |
1497 | for @code{c-hungry-delete-forward}.} (@pxref{Minor Modes}.) This | |
1498 | makes @kbd{@key{DEL}} and @kbd{C-d} do backwards and forward hungry | |
1499 | deletion. | |
1500 | ||
1501 | @table @asis | |
1502 | @item @kbd{@key{DEL}} (@code{c-electric-backspace}) | |
1503 | @kindex DEL | |
1504 | @findex c-electric-backspace | |
1505 | @findex electric-backspace (c-) | |
1506 | This command is run by default when you hit the @kbd{DEL} key. When | |
1507 | hungry delete mode is enabled, it deletes any amount of whitespace in | |
1508 | the backwards direction. Otherwise, or when used with a prefix | |
1509 | argument or in a literal (@pxref{Auto-newlines}), the command just | |
1510 | deletes backwards in the usual way. (More precisely, it calls the | |
1511 | function contained in the variable @code{c-backspace-function}, | |
1512 | passing it the prefix argument, if any.) | |
1513 | ||
1514 | @item @code{c-backspace-function} | |
1515 | @vindex c-backspace-function | |
1516 | @vindex backspace-function (c-) | |
1517 | @findex backward-delete-char-untabify | |
1518 | Hook that gets called by @code{c-electric-backspace} when it doesn't | |
1519 | do an ``electric'' deletion of the preceding whitespace. The default | |
1520 | value is @code{backward-delete-char-untabify} | |
1521 | (@pxref{Deletion,,,@lispref{}, @lispreftitle{}}, the function which | |
1522 | deletes a single character. | |
1523 | ||
1524 | @item @kbd{C-d} (@code{c-electric-delete-forward}) | |
1525 | @kindex C-d | |
1526 | @findex c-electric-delete-forward | |
1527 | @findex electric-delete-forward (c-) | |
1528 | This function, which is bound to @kbd{C-d} by default, works just like | |
1529 | @code{c-electric-backspace} but in the forward direction. When it | |
1530 | doesn't do an ``electric'' deletion of the following whitespace, it | |
1531 | just does @code{delete-char}, more or less. (Strictly speaking, it | |
1532 | calls the function in @code{c-delete-function} with the prefix | |
1533 | argument.) | |
1534 | ||
1535 | @item @code{c-delete-function} | |
1536 | @vindex c-delete-function | |
1537 | @vindex delete-function (c-) | |
1538 | @findex delete-char | |
1539 | Hook that gets called by @code{c-electric-delete-forward} when it | |
1540 | doesn't do an ``electric'' deletion of the following whitespace. The | |
1541 | default value is @code{delete-char}. | |
1542 | @end table | |
1543 | ||
1544 | @item Using Distinct Bindings | |
1545 | The other (newer and recommended) way to use hungry deletion is to | |
1546 | perform @code{c-hungry-delete-backwards} and | |
1547 | @code{c-hungry-delete-forward} directly through their key sequences | |
1548 | rather than using the minor mode toggling. | |
1549 | ||
1550 | @table @asis | |
1551 | @item @kbd{C-c C-@key{DEL}}, or @kbd{C-c @key{DEL}} (@code{c-hungry-delete-backwards})@footnote{This command was formerly known as @code{c-hungry-backspace}.} | |
1552 | @kindex C-c C-<backspace> | |
1553 | @kindex C-c <backspace> | |
1554 | @kindex C-c C-DEL | |
1555 | @kindex C-c DEL | |
1556 | @findex c-hungry-delete-backwards | |
1557 | @findex hungry-delete-backwards (c-) | |
1558 | Delete any amount of whitespace in the backwards direction (regardless | |
1559 | whether hungry-delete mode is enabled or not). This command is bound | |
1560 | to both @kbd{C-c C-@key{DEL}} and @kbd{C-c @key{DEL}}, since the more | |
1561 | natural one, @kbd{C-c C-@key{DEL}}, is sometimes difficult to type at | |
1562 | a character terminal. | |
1563 | ||
1564 | @item @kbd{C-c C-d}, @kbd{C-c C-@key{DELETE}}, or @kbd{C-c @key{DELETE}} (@code{c-hungry-delete-forward}) | |
1565 | @kindex C-c C-d | |
1566 | @kindex C-c C-<DELETE> | |
1567 | @kindex C-c <DELETE> | |
1568 | @findex c-hungry-delete-forward | |
1569 | @findex hungry-delete-forward (c-) | |
1570 | Delete any amount of whitespace in the forward direction (regardless | |
1571 | whether hungry-delete mode is enabled or not). This command is bound | |
1572 | to both @kbd{C-c C-@key{DELETE}} and @kbd{C-c @key{DELETE}} for the | |
1573 | same reason as for @key{DEL} above. | |
1574 | @end table | |
1575 | @end table | |
1576 | ||
1577 | @kindex <delete> | |
1578 | @kindex <backspace> | |
1579 | ||
1580 | When we talk about @kbd{@key{DEL}}, and @kbd{@key{DELETE}} above, we | |
1581 | actually do so without connecting them to the physical keys commonly | |
1582 | known as @key{Backspace} and @key{Delete}. The default bindings to | |
1583 | those two keys depends on the flavor of (X)Emacs you are using. | |
1584 | ||
1585 | @findex c-electric-delete | |
1586 | @findex electric-delete (c-) | |
1587 | @findex c-hungry-delete | |
1588 | @findex hungry-delete (c-) | |
1589 | @vindex delete-key-deletes-forward | |
1590 | In XEmacs 20.3 and beyond, the @key{Backspace} key is bound to | |
1591 | @code{c-electric-backspace} and the @key{Delete} key is bound to | |
1592 | @code{c-electric-delete}. You control the direction it deletes in by | |
1593 | setting the variable @code{delete-key-deletes-forward}, a standard | |
1594 | XEmacs variable. | |
1595 | @c This variable is encapsulated by XEmacs's (defsubst delete-forward-p ...). | |
1596 | When this variable is non-@code{nil}, @code{c-electric-delete} will do | |
1597 | forward deletion with @code{c-electric-delete-forward}, otherwise it | |
1598 | does backward deletion with @code{c-electric-backspace}. Similarly, | |
1599 | @kbd{C-c @key{Delete}} and @kbd{C-c C-@key{Delete}} are bound to | |
1600 | @code{c-hungry-delete} which is controlled in the same way by | |
1601 | @code{delete-key-deletes-forward}. | |
1602 | ||
1603 | @findex normal-erase-is-backspace-mode | |
1604 | ||
1605 | Emacs 21 and later automatically binds @key{Backspace} and | |
1606 | @key{Delete} to @kbd{DEL} and @kbd{C-d} according to your environment, | |
1607 | and @ccmode{} extends those bindings to @kbd{C-c C-@key{Backspace}} | |
1608 | etc. If you need to change the bindings through | |
1609 | @code{normal-erase-is-backspace-mode} then @ccmode{} will also adapt | |
1610 | its extended bindings accordingly. | |
1611 | ||
1612 | In earlier (X)Emacs versions, @ccmode{} doesn't bind either | |
1613 | @key{Backspace} or @key{Delete} directly. Only the key codes | |
1614 | @kbd{DEL} and @kbd{C-d} are bound, and it's up to the default bindings | |
1615 | to map the physical keys to them. You might need to modify this | |
1616 | yourself if the defaults are unsuitable. | |
1617 | ||
1618 | Getting your @key{Backspace} and @key{Delete} keys properly set up can | |
1619 | sometimes be tricky. The information in @ref{DEL Does Not | |
1620 | Delete,,,emacs, GNU Emacs Manual}, might be helpful if you're having | |
1621 | trouble with this in GNU Emacs. | |
1622 | ||
1623 | ||
1624 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1625 | @node Subword Movement, Other Commands, Hungry WS Deletion, Commands | |
1626 | @comment node-name, next, previous, up | |
1627 | @section Subword Movement and Editing | |
1628 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1629 | ||
1630 | @cindex nomenclature | |
1631 | @cindex subword | |
1632 | In spite of the GNU Coding Standards, it is popular to name a symbol | |
1df7defd | 1633 | by mixing uppercase and lowercase letters, e.g., @samp{GtkWidget}, |
4009494e GM |
1634 | @samp{EmacsFrameClass}, or @samp{NSGraphicsContext}. Here we call |
1635 | these mixed case symbols @dfn{nomenclatures}. Also, each capitalized | |
1636 | (or completely uppercase) part of a nomenclature is called a | |
1637 | @dfn{subword}. Here are some examples: | |
1638 | ||
1639 | @multitable {@samp{NSGraphicsContext}} {@samp{NS}, @samp{Graphics}, and @samp{Context}} | |
1640 | @c This could be converted to @headitem when we require Texinfo 4.7 | |
1641 | @iftex | |
1642 | @item @b{Nomenclature} | |
1643 | @tab @b{Subwords} | |
1644 | @end iftex | |
1645 | @ifnottex | |
1646 | @item Nomenclature | |
1647 | @tab Subwords | |
1648 | @item --------------------------------------------------------- | |
1649 | @end ifnottex | |
1650 | @item @samp{GtkWindow} | |
1651 | @tab @samp{Gtk} and @samp{Window} | |
1652 | @item @samp{EmacsFrameClass} | |
1653 | @tab @samp{Emacs}, @samp{Frame}, and @samp{Class} | |
1654 | @item @samp{NSGraphicsContext} | |
1655 | @tab @samp{NS}, @samp{Graphics}, and @samp{Context} | |
1656 | @end multitable | |
1657 | ||
1658 | The subword minor mode replaces the basic word oriented movement and | |
1659 | editing commands with variants that recognize subwords in a | |
1660 | nomenclature and treat them as separate words: | |
1661 | ||
1662 | @findex c-forward-subword | |
1663 | @findex forward-subword (c-) | |
1664 | @findex c-backward-subword | |
1665 | @findex backward-subword (c-) | |
1666 | @findex c-mark-subword | |
1667 | @findex mark-subword (c-) | |
1668 | @findex c-kill-subword | |
1669 | @findex kill-subword (c-) | |
1670 | @findex c-backward-kill-subword | |
1671 | @findex backward-kill-subword (c-) | |
1672 | @findex c-transpose-subwords | |
1673 | @findex transpose-subwords (c-) | |
1674 | @findex c-capitalize-subword | |
1675 | @findex capitalize-subword (c-) | |
1676 | @findex c-upcase-subword | |
1677 | @findex upcase-subword (c-) | |
1678 | @findex c-downcase-subword | |
1679 | @findex downcase-subword (c-) | |
1680 | @multitable @columnfractions .20 .40 .40 | |
1681 | @c This could be converted to @headitem when we require Texinfo 4.7 | |
1682 | @iftex | |
1683 | @item @b{Key} @tab @b{Word oriented command} @tab @b{Subword oriented command} | |
1684 | @end iftex | |
1685 | @ifnottex | |
1686 | @item Key @tab Word oriented command @tab Subword oriented command | |
1687 | @item ---------------------------------------------------------------------------- | |
1688 | @end ifnottex | |
1689 | @item @kbd{M-f} @tab @code{forward-word} @tab @code{c-forward-subword} | |
1690 | @item @kbd{M-b} @tab @code{backward-word} @tab @code{c-backward-subword} | |
1691 | @item @kbd{M-@@} @tab @code{mark-word} @tab @code{c-mark-subword} | |
1692 | @item @kbd{M-d} @tab @code{kill-word} @tab @code{c-kill-subword} | |
1693 | @item @kbd{M-DEL} @tab @code{backward-kill-word} @tab @code{c-backward-kill-subword} | |
1694 | @item @kbd{M-t} @tab @code{transpose-words} @tab @code{c-transpose-subwords} | |
1695 | @item @kbd{M-c} @tab @code{capitalize-word} @tab @code{c-capitalize-subword} | |
1696 | @item @kbd{M-u} @tab @code{upcase-word} @tab @code{c-upcase-subword} | |
1697 | @item @kbd{M-l} @tab @code{downcase-word} @tab @code{c-downcase-subword} | |
1698 | @end multitable | |
1699 | ||
1700 | Note that if you have changed the key bindings for the word oriented | |
1701 | commands in your @file{.emacs} or a similar place, the keys you have | |
1702 | configured are also used for the corresponding subword oriented | |
1703 | commands. | |
1704 | ||
1705 | Type @kbd{C-c C-w} to toggle subword mode on and off. To make the | |
1706 | mode turn on automatically, put the following code in your | |
1707 | @file{.emacs}: | |
1708 | ||
1709 | @example | |
1710 | (add-hook 'c-mode-common-hook | |
aaef4f91 | 1711 | (lambda () (subword-mode 1))) |
4009494e GM |
1712 | @end example |
1713 | ||
aaef4f91 MH |
1714 | As a bonus, you can also use @code{subword-mode} in non-@ccmode{} |
1715 | buffers by typing @kbd{M-x subword-mode}. | |
4009494e GM |
1716 | |
1717 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1718 | @node Other Commands, , Subword Movement, Commands | |
1719 | @comment node-name, next, previous, up | |
1720 | @section Other Commands | |
1721 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1722 | ||
1723 | Here are the various other commands that didn't fit anywhere else: | |
1724 | ||
1725 | @table @asis | |
1726 | @item @kbd{C-c .} (@code{c-set-style}) | |
1727 | @kindex C-c . | |
1728 | @findex c-set-style | |
1729 | @findex set-style (c-) | |
1730 | Switch to the specified style in the current buffer. Use like this: | |
1731 | ||
1732 | @example | |
1733 | @kbd{C-c . @var{style-name} @key{RET}} | |
1734 | @end example | |
1735 | ||
1736 | You can use the @key{TAB} in the normal way to do completion on the | |
1737 | style name. Note that all style names are case insensitive, even the | |
1738 | ones you define yourself. | |
1739 | ||
1740 | Setting a style in this way does @emph{not} automatically reindent your | |
1741 | file. For commands that you can use to view the effect of your changes, | |
1742 | see @ref{Indentation Commands} and @ref{Filling and Breaking}. | |
1743 | ||
1744 | For details of the @ccmode{} style system, see @ref{Styles}. | |
1745 | @item @kbd{C-c :} (@code{c-scope-operator}) | |
1746 | @kindex C-c : | |
1747 | @findex c-scope-operator | |
1748 | @findex scope-operator (c-) | |
1749 | In C++, it is also sometimes desirable to insert the double-colon scope | |
1750 | operator without performing the electric behavior of colon insertion. | |
1751 | @kbd{C-c :} does just this. | |
1752 | ||
1753 | @item @kbd{C-c C-\} (@code{c-backslash-region}) | |
1754 | @kindex C-c C-\ | |
1755 | @findex c-backslash-region | |
1756 | @findex backslash-region (c-) | |
1757 | This function inserts and aligns or deletes end-of-line backslashes in | |
1758 | the current region. These are typically used in multi-line macros. | |
1759 | ||
1760 | With no prefix argument, it inserts any missing backslashes and aligns | |
1761 | them according to the @code{c-backslash-column} and | |
1762 | @code{c-backslash-max-column} variables. With a prefix argument, it | |
1763 | deletes any backslashes. | |
1764 | ||
1765 | The function does not modify blank lines at the start of the region. If | |
1766 | the region ends at the start of a line, it always deletes the backslash | |
1767 | (if any) at the end of the previous line. | |
1768 | ||
1769 | To customize the precise workings of this command, @ref{Custom Macros}. | |
1770 | @end table | |
1771 | ||
1772 | @noindent | |
1773 | The recommended line breaking function, @code{c-context-line-break} | |
1774 | (@pxref{Filling and Breaking}), is especially nice if you edit | |
1775 | multiline macros frequently. When used inside a macro, it | |
1776 | automatically inserts and adjusts the mandatory backslash at the end | |
1777 | of the line to keep the macro together, and it leaves the point at the | |
1778 | right indentation column for the code. Thus you can write code inside | |
1779 | macros almost exactly as you can elsewhere, without having to bother | |
1780 | with the trailing backslashes. | |
1781 | ||
1782 | @table @asis | |
1783 | @item @kbd{C-c C-e} (@code{c-macro-expand}) | |
1784 | @kindex C-c C-e | |
1785 | @findex c-macro-expand | |
1786 | @findex macro-expand (c-) | |
1787 | This command expands C, C++, Objective C or Pike macros in the region, | |
1788 | using an appropriate external preprocessor program. Normally it | |
1789 | displays its output in a temporary buffer, but if you give it a prefix | |
1790 | arg (with @kbd{C-u C-c C-e}) it will overwrite the original region | |
1791 | with the expansion. | |
1792 | ||
1793 | The command does not work in any of the other modes, and the key | |
1794 | sequence is not bound in these other modes. | |
1795 | ||
1796 | @code{c-macro-expand} isn't actually part of @ccmode{}, even though it | |
1797 | is bound to a @ccmode{} key sequence. If you need help setting it up | |
1798 | or have other problems with it, you can either read its source code or | |
1799 | ask for help in the standard (X)Emacs forums. | |
1800 | @end table | |
1801 | ||
1802 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1803 | @node Font Locking, Config Basics, Commands, Top | |
1804 | @comment node-name, next, previous, up | |
1805 | @chapter Font Locking | |
1806 | @cindex font locking | |
1807 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1808 | ||
1809 | @cindex Font Lock mode | |
1810 | ||
1811 | @ccmode{} provides font locking for its supported languages by | |
1812 | supplying patterns for use with Font Lock mode. This means that you | |
1813 | get distinct faces on the various syntactic parts such as comments, | |
1814 | strings, keywords and types, which is very helpful in telling them | |
1815 | apart at a glance and discovering syntactic errors. @xref{Font | |
1816 | Lock,,, emacs, GNU Emacs Manual}, for ways to enable font locking in | |
1817 | @ccmode{} buffers. | |
1818 | ||
1819 | @strong{Please note:} The font locking in AWK mode is currently not | |
1820 | integrated with the rest of @ccmode{}. Only the last section of this | |
1df7defd | 1821 | chapter, @ref{AWK Mode Font Locking}, applies to AWK@. The other |
4009494e GM |
1822 | sections apply to the other languages. |
1823 | ||
1824 | @menu | |
1825 | * Font Locking Preliminaries:: | |
1826 | * Faces:: | |
1827 | * Doc Comments:: | |
1828 | * AWK Mode Font Locking:: | |
1829 | @end menu | |
1830 | ||
1831 | ||
1832 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1833 | @node Font Locking Preliminaries, Faces, Font Locking, Font Locking | |
1834 | @comment node-name, next, previous, up | |
1835 | @section Font Locking Preliminaries | |
1836 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1837 | ||
1838 | The font locking for most of the @ccmode{} languages were provided | |
1839 | directly by the Font Lock package prior to version 5.30 of @ccmode{}. | |
1840 | In the transition to @ccmode{} the patterns have been reworked | |
1841 | completely and are applied uniformly across all the languages except AWK | |
1842 | mode, just like the indentation rules (although each language still has | |
1843 | some peculiarities of its own, of course). Since the languages | |
1844 | previously had completely separate font locking patterns, this means | |
1845 | that it's a bit different in most languages now. | |
1846 | ||
1847 | The main goal for the font locking in @ccmode{} is accuracy, to provide | |
1848 | a dependable aid in recognizing the various constructs. Some, like | |
1849 | strings and comments, are easy to recognize while others, like | |
1850 | declarations and types, can be very tricky. @ccmode{} can go to great | |
1851 | lengths to recognize declarations and casts correctly, especially when | |
1852 | the types aren't recognized by standard patterns. This is a fairly | |
1853 | demanding analysis which can be slow on older hardware, and it can | |
1854 | therefore be disabled by choosing a lower decoration level with the | |
1855 | variable @code{font-lock-maximum-decoration} (@pxref{Font Lock,,, | |
1856 | emacs, GNU Emacs Manual}). | |
1857 | ||
1858 | @vindex font-lock-maximum-decoration | |
1859 | ||
1860 | The decoration levels are used as follows: | |
1861 | ||
1862 | @enumerate | |
1863 | @comment 1 | |
1864 | @item | |
1865 | Minimal font locking: Fontify only comments, strings and preprocessor | |
1866 | directives (in the languages that use cpp). | |
1867 | ||
1868 | @comment 2 | |
1869 | @item | |
1870 | Fast font locking: In addition to level 1, fontify keywords, simple | |
1871 | types and declarations that are easy to recognize. The variables | |
1872 | @code{*-font-lock-extra-types} (where @samp{*} is the name of the | |
1873 | language) are used to recognize types (see below). Documentation | |
1874 | comments like Javadoc are fontified according to | |
1875 | @code{c-doc-comment-style} (@pxref{Doc Comments}). | |
1876 | ||
1877 | Use this if you think the font locking is too slow. It's the closest | |
1878 | corresponding level to level 3 in the old font lock patterns. | |
1879 | ||
1880 | @comment 3 | |
1881 | @item | |
1882 | Accurate font locking: Like level 2 but uses a different approach that | |
1883 | can recognize types and declarations much more accurately. The | |
1884 | @code{*-font-lock-extra-types} variables are still used, but user | |
1885 | defined types are recognized correctly anyway in most cases. Therefore | |
1886 | those variables should be fairly restrictive and not contain patterns | |
1887 | that are uncertain. | |
1888 | ||
1889 | @cindex Lazy Lock mode | |
1890 | @cindex Just-in-time Lock mode | |
1891 | ||
1892 | This level is designed for fairly modern hardware and a font lock | |
1893 | support mode like Lazy Lock or Just-in-time Lock mode that only | |
1894 | fontifies the parts that are actually shown. Fontifying the whole | |
1895 | buffer at once can easily get bothersomely slow even on contemporary | |
1896 | hardware. @xref{Font Lock,,,@emacsman{}, @emacsmantitle{}}. | |
1897 | @end enumerate | |
1898 | ||
1899 | @cindex user defined types | |
1900 | @cindex types, user defined | |
1901 | ||
1902 | Since user defined types are hard to recognize you can provide | |
1903 | additional regexps to match those you use: | |
1904 | ||
1905 | @defopt c-font-lock-extra-types | |
1906 | @defoptx c++-font-lock-extra-types | |
1907 | @defoptx objc-font-lock-extra-types | |
1908 | @defoptx java-font-lock-extra-types | |
1909 | @defoptx idl-font-lock-extra-types | |
1910 | @defoptx pike-font-lock-extra-types | |
1911 | For each language there's a variable @code{*-font-lock-extra-types}, | |
1912 | where @samp{*} stands for the language in question. It contains a list | |
1913 | of regexps that matches identifiers that should be recognized as types, | |
1df7defd | 1914 | e.g., @samp{\\sw+_t} to recognize all identifiers ending with @samp{_t} |
4009494e GM |
1915 | as is customary in C code. Each regexp should not match more than a |
1916 | single identifier. | |
1917 | ||
1918 | The default values contain regexps for many types in standard runtime | |
1919 | libraries that are otherwise difficult to recognize, and patterns for | |
1920 | standard type naming conventions like the @samp{_t} suffix in C and C++. | |
1921 | Java, Objective-C and Pike have as a convention to start class names | |
1922 | with capitals, so there are patterns for that in those languages. | |
1923 | ||
1924 | Despite the names of these variables, they are not only used for | |
1925 | fontification but in other places as well where @ccmode{} needs to | |
1926 | recognize types. | |
1927 | @end defopt | |
1928 | ||
1929 | ||
1930 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1931 | @node Faces, Doc Comments, Font Locking Preliminaries, Font Locking | |
1932 | @comment node-name, next, previous, up | |
1933 | @section Faces | |
1934 | @cindex faces | |
1935 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
1936 | ||
1937 | @ccmode{} attempts to use the standard faces for programming languages | |
1938 | in accordance with their intended purposes as far as possible. No extra | |
1939 | faces are currently provided, with the exception of a replacement face | |
1940 | @code{c-invalid-face} for emacsen that don't provide | |
1941 | @code{font-lock-warning-face}. | |
1942 | ||
1943 | @itemize @bullet | |
1944 | @item | |
1945 | @vindex font-lock-comment-face | |
1946 | Normal comments are fontified in @code{font-lock-comment-face}. | |
1947 | ||
1948 | @item | |
1949 | @vindex font-lock-doc-face | |
1950 | @vindex font-lock-doc-string-face | |
1951 | @vindex font-lock-comment-face | |
1952 | Comments that are recognized as documentation (@pxref{Doc Comments}) | |
1953 | get @code{font-lock-doc-face} (Emacs) or | |
1954 | @code{font-lock-doc-string-face} (XEmacs) if those faces exist. If | |
1955 | they don't then @code{font-lock-comment-face} is used. | |
1956 | ||
1957 | @item | |
1958 | @vindex font-lock-string-face | |
1959 | String and character literals are fontified in | |
1960 | @code{font-lock-string-face}. | |
1961 | ||
1962 | @item | |
1963 | @vindex font-lock-keyword-face | |
1964 | Keywords are fontified with @code{font-lock-keyword-face}. | |
1965 | ||
1966 | @item | |
1967 | @vindex font-lock-function-name-face | |
1968 | @code{font-lock-function-name-face} is used for function names in | |
1969 | declarations and definitions, and classes in those contexts. It's also | |
1970 | used for preprocessor defines with arguments. | |
1971 | ||
1972 | @item | |
1973 | @vindex font-lock-variable-name-face | |
1974 | Variables in declarations and definitions, and other identifiers in such | |
1975 | variable contexts, get @code{font-lock-variable-name-face}. It's also | |
1976 | used for preprocessor defines without arguments. | |
1977 | ||
1978 | @item | |
1979 | @vindex font-lock-constant-face | |
1980 | @vindex font-lock-reference-face | |
1981 | Builtin constants are fontified in @code{font-lock-constant-face} if it | |
1982 | exists, @code{font-lock-reference-face} otherwise. As opposed to the | |
1983 | preceding two faces, this is used on the names in expressions, and it's | |
1984 | not used in declarations, even if there happen to be a @samp{const} in | |
1985 | them somewhere. | |
1986 | ||
1987 | @item | |
1988 | @vindex font-lock-type-face | |
1989 | @code{font-lock-type-face} is put on types (both predefined and user | |
1990 | defined) and classes in type contexts. | |
1991 | ||
1992 | @item | |
1993 | @vindex font-lock-constant-face | |
1994 | @vindex font-lock-reference-face | |
1995 | Label identifiers get @code{font-lock-constant-face} if it exists, | |
1996 | @code{font-lock-reference-face} otherwise. | |
1997 | ||
1998 | @item | |
1999 | Name qualifiers and identifiers for scope constructs are fontified like | |
2000 | labels. | |
2001 | ||
2002 | @item | |
2003 | Special markup inside documentation comments are also fontified like | |
2004 | labels. | |
2005 | ||
2006 | @item | |
2007 | @vindex font-lock-preprocessor-face | |
2008 | @vindex font-lock-builtin-face | |
2009 | @vindex font-lock-reference-face | |
2010 | Preprocessor directives get @code{font-lock-preprocessor-face} if it | |
1df7defd | 2011 | exists (i.e., XEmacs). In Emacs they get @code{font-lock-builtin-face} |
4009494e GM |
2012 | or @code{font-lock-reference-face}, for lack of a closer equivalent. |
2013 | ||
2014 | @item | |
2015 | @vindex font-lock-warning-face | |
2016 | @vindex c-invalid-face | |
2017 | @vindex invalid-face (c-) | |
2018 | Some kinds of syntactic errors are fontified with | |
2019 | @code{font-lock-warning-face} in Emacs. In older XEmacs versions | |
2020 | there's no corresponding standard face, so there a special | |
2021 | @code{c-invalid-face} is used, which is defined to stand out sharply by | |
2022 | default. | |
2023 | ||
2024 | Note that it's not used for @samp{#error} or @samp{#warning} directives, | |
2025 | since those aren't syntactic errors in themselves. | |
2026 | @end itemize | |
2027 | ||
2028 | ||
2029 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
2030 | @node Doc Comments, AWK Mode Font Locking, Faces, Font Locking | |
2031 | @comment node-name, next, previous, up | |
2032 | @section Documentation Comments | |
2033 | @cindex documentation comments | |
2034 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
2035 | ||
2036 | There are various tools to supply documentation in the source as | |
1df7defd | 2037 | specially structured comments, e.g., the standard Javadoc tool in Java. |
4009494e GM |
2038 | @ccmode{} provides an extensible mechanism to fontify such comments and |
2039 | the special markup inside them. | |
2040 | ||
2041 | @defopt c-doc-comment-style | |
2042 | @vindex doc-comment-style (c-) | |
2043 | This is a style variable that specifies which documentation comment | |
1df7defd | 2044 | style to recognize, e.g., @code{javadoc} for Javadoc comments. |
4009494e GM |
2045 | |
2046 | The value may also be a list of styles, in which case all of them are | |
2047 | recognized simultaneously (presumably with markup cues that don't | |
2048 | conflict). | |
2049 | ||
2050 | The value may also be an association list to specify different comment | |
2051 | styles for different languages. The symbol for the major mode is then | |
2052 | looked up in the alist, and the value of that element is interpreted as | |
2053 | above if found. If it isn't found then the symbol `other' is looked up | |
2054 | and its value is used instead. | |
2055 | ||
2056 | The default value for @code{c-doc-comment-style} is | |
2057 | @w{@code{((java-mode . javadoc) (pike-mode . autodoc) (c-mode . gtkdoc))}}. | |
2058 | ||
2059 | Note that @ccmode{} uses this variable to set other variables that | |
2060 | handle fontification etc. That's done at mode initialization or when | |
2061 | you switch to a style which sets this variable. Thus, if you change it | |
1df7defd | 2062 | in some other way, e.g., interactively in a CC Mode buffer, you will need |
4009494e GM |
2063 | to do @kbd{M-x java-mode} (or whatever mode you're currently using) to |
2064 | reinitialize. | |
2065 | ||
2066 | @findex c-setup-doc-comment-style | |
2067 | @findex setup-doc-comment-style (c-) | |
2068 | Note also that when @ccmode{} starts up, the other variables are | |
2069 | modified before the mode hooks are run. If you change this variable in | |
2070 | a mode hook, you'll have to call @code{c-setup-doc-comment-style} | |
2071 | afterwards to redo that work. | |
2072 | @end defopt | |
2073 | ||
2074 | @ccmode{} currently provides handing of the following doc comment | |
2075 | styles: | |
2076 | ||
2077 | @table @code | |
2078 | @item javadoc | |
2079 | @cindex Javadoc markup | |
2080 | Javadoc comments, the standard tool in Java. | |
2081 | ||
2082 | @item autodoc | |
2083 | @cindex Pike autodoc markup | |
2084 | For Pike autodoc markup, the standard in Pike. | |
2085 | ||
2086 | @item gtkdoc | |
2087 | @cindex GtkDoc markup | |
2088 | For GtkDoc markup, widely used in the Gnome community. | |
2089 | @end table | |
2090 | ||
2091 | The above is by no means complete. If you'd like to see support for | |
2092 | other doc comment styles, please let us know (@pxref{Mailing Lists and | |
2093 | Bug Reports}). | |
2094 | ||
2095 | You can also write your own doc comment fontification support to use | |
2096 | with @code{c-doc-comment-style}: Supply a variable or function | |
2097 | @code{*-font-lock-keywords} where @samp{*} is the name you want to use | |
2098 | in @code{c-doc-comment-style}. If it's a variable, it's prepended to | |
2099 | @code{font-lock-keywords}. If it's a function, it's called at mode | |
2100 | initialization and the result is prepended. For an example, see | |
2101 | @code{javadoc-font-lock-keywords} in @file{cc-fonts.el}. | |
2102 | ||
2103 | If you add support for another doc comment style, please consider | |
f99f1641 | 2104 | contributing it: send a note to @email{bug-cc-mode@@gnu.org}. |
4009494e GM |
2105 | |
2106 | ||
2107 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
2108 | @node AWK Mode Font Locking, , Doc Comments, Font Locking | |
2109 | @comment node-name, next, previous, up | |
2110 | @section AWK Mode Font Locking | |
2111 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
2112 | ||
2113 | The general appearance of font-locking in AWK mode is much like in any | |
a944db14 | 2114 | other programming mode. @xref{Faces for Font Lock,,,elisp, GNU Emacs |
4009494e GM |
2115 | Lisp Reference Manual}. |
2116 | ||
2117 | The following faces are, however, used in a non-standard fashion in | |
2118 | AWK mode: | |
2119 | ||
2120 | @table @asis | |
2121 | @item @code{font-lock-variable-name-face} | |
2122 | This face was intended for variable declarations. Since variables are | |
2123 | not declared in AWK, this face is used instead for AWK system | |
2124 | variables (such as @code{NF}) and ``Special File Names'' (such as | |
2125 | @code{"/dev/stderr"}). | |
2126 | ||
2127 | @item @code{font-lock-builtin-face} (Emacs)/@code{font-lock-preprocessor-face} (XEmacs) | |
2128 | This face is normally used for preprocessor directives in @ccmode{}. | |
2129 | There are no such things in AWK, so this face is used instead for | |
2130 | standard functions (such as @code{match}). | |
2131 | ||
2132 | @item @code{font-lock-string-face} | |
2133 | As well as being used for strings, including localizable strings, | |
2134 | (delimited by @samp{"} and @samp{_"}), this face is also used for AWK | |
2135 | regular expressions (delimited by @samp{/}). | |
2136 | ||
2137 | @item @code{font-lock-warning-face} (Emacs)/@code{c-invalid-face} (XEmacs) | |
2138 | This face highlights the following syntactically invalid AWK | |
2139 | constructs: | |
2140 | ||
2141 | @itemize @bullet | |
2142 | @item | |
2143 | An unterminated string or regular expression. Here the opening | |
2144 | delimiter (@samp{"} or @samp{/} or @samp{_"}) is displayed in | |
2145 | @code{font-lock-warning-face}. This is most noticeable when typing in a | |
2146 | new string/regular expression into a buffer, when the warning-face | |
2147 | serves as a continual reminder to terminate the construct. | |
2148 | ||
2149 | AWK mode fontifies unterminated strings/regular expressions | |
2150 | differently from other modes: Only the text up to the end of the line | |
2151 | is fontified as a string (escaped newlines being handled correctly), | |
2152 | rather than the text up to the next string quote. | |
2153 | ||
2154 | @item | |
2155 | A space between the function name and opening parenthesis when calling | |
2156 | a user function. The last character of the function name and the | |
2157 | opening parenthesis are highlighted. This font-locking rule will | |
2158 | spuriously highlight a valid concatenation expression where an | |
333f9019 | 2159 | identifier precedes a parenthesized expression. Unfortunately. |
4009494e GM |
2160 | |
2161 | @item | |
2162 | Whitespace following the @samp{\} in what otherwise looks like an | |
2163 | escaped newline. The @samp{\} is highlighted. | |
2164 | @end itemize | |
2165 | @end table | |
2166 | ||
2167 | ||
2168 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
2169 | @node Config Basics, Custom Filling and Breaking, Font Locking, Top | |
2170 | @comment node-name, next, previous, up | |
2171 | @chapter Configuration Basics | |
2172 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
2173 | ||
2174 | @cindex Emacs Initialization File | |
2175 | @cindex Configuration | |
2176 | You configure @ccmode{} by setting Lisp variables and calling (and | |
2177 | perhaps writing) Lisp functions@footnote{DON'T PANIC!!! This isn't | |
2178 | difficult.}, which is usually done by adding code to an Emacs | |
2179 | initialization file. This file might be @file{site-start.el} or | |
2180 | @file{.emacs} or @file{init.el} or @file{default.el} or perhaps some | |
2181 | other file. @xref{Init File,,,@emacsman{}, @emacsmantitle{}}. For | |
2182 | the sake of conciseness, we just call this file ``your @file{.emacs}'' | |
2183 | throughout the rest of the manual. | |
2184 | ||
2185 | Several of these variables (currently 16), are known collectively as | |
2186 | @dfn{style variables}. @ccmode{} provides a special mechanism, known | |
2187 | as @dfn{styles} to make it easier to set these variables as a group, | |
2188 | to ``inherit'' settings from one style into another, and so on. Style | |
2189 | variables remain ordinary Lisp variables, whose values can be read and | |
2190 | changed independently of the style system. @xref{Style Variables}. | |
2191 | ||
2192 | There are several ways you can write the code, depending on the | |
2193 | precise effect you want---they are described further down on this page. | |
2194 | If you are new to @ccmode{}, we suggest you begin with the simplest | |
2195 | method, ``Top-level commands or the customization interface''. | |
2196 | ||
2197 | If you make conflicting settings in several of these ways, the way | |
2198 | that takes precedence is the one that appears latest in this list: | |
b207a4ec | 2199 | @itemize @w{} |
4009494e GM |
2200 | @item |
2201 | @table @asis | |
2202 | @item Style | |
22556bc5 | 2203 | @itemx File Style@footnote{In earlier versions of @ccmode{}, a File Style setting took precedence over any other setting apart from a File Local Variable setting.} |
4009494e GM |
2204 | @itemx Top-level command or ``customization interface'' |
2205 | @itemx Hook | |
22556bc5 | 2206 | @itemx File Local Variable setting |
4009494e GM |
2207 | @end table |
2208 | @end itemize | |
2209 | ||
2210 | Here is a summary of the different ways of writing your configuration | |
2211 | settings: | |
2212 | ||
2213 | @table @asis | |
2214 | @item Top-level commands or the ``customization interface'' | |
2215 | Most simply, you can write @code{setq} and similar commands at the top | |
2216 | level of your @file{.emacs} file. When you load a @ccmode{} buffer, | |
2217 | it initializes its configuration from these global values (at least, | |
2218 | for those settings you have given values to), so it makes sense to | |
2219 | have these @code{setq} commands run @emph{before} @ccmode{} is first | |
2220 | initialized---in particular, before any call to @code{desktop-read} | |
2221 | (@pxref{Saving Emacs Sessions,,, emacs, GNU Emacs Manual}). For | |
2222 | example, you might set c-basic-offset thus: | |
2223 | ||
2224 | @example | |
2225 | (setq c-basic-offset 4) | |
2226 | @end example | |
2227 | ||
2228 | You can use the more user friendly Customization interface instead, | |
2229 | but this manual does not cover in detail how that works. To do this, | |
2230 | start by typing @kbd{M-x customize-group @key{RET} c @key{RET}}. | |
2231 | @xref{Easy Customization,,,@emacsman{}, @emacsmantitle{}}. | |
2232 | @c The following note really belongs in the Emacs manual. | |
2233 | Emacs normally writes the customizations at the end of your | |
2234 | @file{.emacs} file. If you use @code{desktop-read}, you should edit | |
2235 | your @file{.emacs} to place the call to @code{desktop-read} @emph{after} | |
2236 | the customizations. | |
2237 | ||
2238 | The first initialization of @ccmode{} puts a snapshot of the | |
2239 | configuration settings into the special style @code{user}. | |
2240 | @xref{Built-in Styles}. | |
2241 | ||
2242 | For basic use of Emacs, either of these ways of configuring is | |
2243 | adequate. However, the settings are then the same in all @ccmode{} | |
2244 | buffers and it can be clumsy to communicate them between programmers. | |
2245 | For more flexibility, you'll want to use one (or both) of @ccmode{}'s | |
2246 | more sophisticated facilities, hooks and styles. | |
2247 | ||
2248 | @item Hooks | |
2249 | An Emacs @dfn{hook} is a place to put Lisp functions that you want | |
2250 | Emacs to execute later in specific circumstances. | |
2251 | @xref{Hooks,,,@lispref{}, @lispreftitle{}}. @ccmode{} supplies a main | |
f99f1641 | 2252 | hook and a language-specific hook for each language it supports; any |
4009494e GM |
2253 | functions you put onto these hooks get executed as the last part of a |
2254 | buffer's initialization. Typically you put most of your customization | |
2255 | within the main hook, and use the language-specific hooks to vary the | |
2256 | customization settings between language modes. For example, if you | |
2257 | wanted different (non-standard) values of @code{c-basic-offset} in C | |
2258 | Mode and Java Mode buffers, you could do it like this: | |
2259 | ||
2260 | @example | |
2261 | @group | |
2262 | (defun my-c-mode-hook () | |
2263 | (setq c-basic-offset 3)) | |
2264 | (add-hook 'c-mode-hook 'my-c-mode-hook) | |
2265 | ||
2266 | (defun my-java-mode-hook () | |
2267 | (setq c-basic-offset 6)) | |
2268 | (add-hook 'java-mode-hook 'my-java-mode-hook) | |
2269 | @end group | |
2270 | @end example | |
2271 | ||
2272 | See @ref{CC Hooks} for more details on the use of @ccmode{} hooks. | |
2273 | ||
2274 | @item Styles | |
2275 | A @ccmode{} @dfn{style} is a coherent collection of customizations | |
2276 | with a name. At any time, exactly one style is active in each | |
2277 | @ccmode{} buffer, either the one you have selected or a default. | |
2278 | @ccmode{} is delivered with several existing styles. Additionally, | |
2279 | you can create your own styles, possibly based on these existing | |
2280 | styles. If you worked in a programming team called the ``Free | |
2281 | Group'', which had its own coding standards, you might well have this | |
2282 | in your @file{.emacs} file: | |
2283 | ||
2284 | @example | |
2285 | (setq c-default-style '((java-mode . "java") | |
2286 | (awk-mode . "awk") | |
2287 | (other . "free-group-style"))) | |
2288 | @end example | |
2289 | ||
2290 | See @ref{Styles} for fuller details on using @ccmode{} styles and how | |
2291 | to create them. | |
2292 | ||
22556bc5 AM |
2293 | @item File Local Variable setting |
2294 | A @dfn{file local variable setting} is a setting which applies to an | |
2295 | individual source file. You put this in a @dfn{local variables list}, | |
2296 | a special block at the end of the source file (@pxref{Specifying File | |
9879e263 | 2297 | Variables,,,@emacsman{}}). |
22556bc5 | 2298 | |
4009494e GM |
2299 | @item File Styles |
2300 | A @dfn{file style} is a rarely used variant of the ``style'' mechanism | |
22556bc5 AM |
2301 | described above, which applies to an individual source file. |
2302 | @xref{File Styles}. You use this by setting certain special variables | |
9879e263 AS |
2303 | in a local variables list (@pxref{Specifying File |
2304 | Variables,,,@emacsman{}}). | |
4009494e GM |
2305 | |
2306 | @item Hooks with Styles | |
2307 | For ultimate flexibility, you can use hooks and styles together. For | |
2308 | example, if your team were developing a product which required a | |
2309 | Linux driver, you'd probably want to use the ``linux'' style for the | |
2310 | driver, and your own team's style for the rest of the code. You | |
2311 | could achieve this with code like this in your @file{.emacs}: | |
2312 | ||
2313 | @example | |
2314 | @group | |
2315 | (defun my-c-mode-hook () | |
2316 | (c-set-style | |
2317 | (if (and (buffer-file-name) | |
2318 | (string-match "/usr/src/linux" (buffer-file-name))) | |
2319 | "linux" | |
2320 | "free-group-style"))) | |
2321 | (add-hook 'c-mode-hook 'my-c-mode-hook) | |
2322 | @end group | |
2323 | @end example | |
2324 | ||
2325 | In a programming team, a hook is a also a good place for each member | |
2326 | to put his own personal preferences. For example, you might be the | |
2327 | only person in your team who likes Auto-newline minor mode. You could | |
2328 | have it enabled by default by placing the following in your | |
2329 | @file{.emacs}: | |
2330 | ||
2331 | @example | |
2332 | @group | |
2333 | (defun my-turn-on-auto-newline () | |
2334 | (c-toggle-auto-newline 1)) | |
2335 | (add-hook 'c-mode-common-hook 'my-turn-on-auto-newline) | |
2336 | @end group | |
2337 | @end example | |
2338 | @end table | |
2339 | ||
2340 | @menu | |
2341 | * CC Hooks:: | |
2342 | * Style Variables:: | |
2343 | * Styles:: | |
2344 | @end menu | |
2345 | ||
2346 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
2347 | @node CC Hooks, Style Variables, Config Basics, Config Basics | |
2348 | @comment node-name, next, previous, up | |
2349 | @section Hooks | |
2350 | @cindex mode hooks | |
2351 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
2352 | @c The node name is "CC Hooks" rather than "Hooks" because of a bug in | |
1df7defd | 2353 | @c some older versions of Info, e.g., the info.el in GNU Emacs 21.3. |
4009494e GM |
2354 | @c If you go to "Config Basics" and hit <CR> on the xref to "CC |
2355 | @c Hooks" the function Info-follow-reference searches for "*Note: CC | |
2356 | @c Hooks" from the beginning of the page. If this node were instead | |
2357 | @c named "Hooks", that search would spuriously find "*Note: | |
2358 | @c Hooks(elisp)" and go to the wrong node. | |
2359 | ||
2360 | @ccmode{} provides several hooks that you can use to customize the | |
2361 | mode for your coding style. The main hook is | |
2362 | @code{c-mode-common-hook}; typically, you'll put the bulk of your | |
2363 | customizations here. In addition, each language mode has its own | |
2364 | hook, allowing you to fine tune your settings individually for the | |
2365 | different @ccmode{} languages, and there is a package initialization | |
2366 | hook. Finally, there is @code{c-special-indent-hook}, which enables | |
2367 | you to solve anomalous indentation problems. It is described in | |
2368 | @ref{Other Indentation}, not here. All these hooks adhere to the | |
2369 | standard Emacs conventions. | |
2370 | ||
2371 | When you open a buffer, @ccmode{} first initializes it with the | |
2372 | currently active style (@pxref{Styles}). Then it calls | |
2373 | @code{c-mode-common-hook}, and finally it calls the language-specific | |
2374 | hook. Thus, any style settings done in these hooks will override | |
2375 | those set by @code{c-default-style}. | |
2376 | ||
2377 | @defvar c-initialization-hook | |
2378 | @vindex initialization-hook (c-) | |
2379 | Hook run only once per Emacs session, when @ccmode{} is initialized. | |
2380 | This is a good place to change key bindings (or add new ones) in any | |
55f612f0 | 2381 | of the @ccmode{} key maps. @xref{Sample Init File}. |
4009494e GM |
2382 | @end defvar |
2383 | ||
2384 | @defvar c-mode-common-hook | |
2385 | @vindex mode-common-hook (c-) | |
2386 | Common hook across all languages. It's run immediately before the | |
2387 | language specific hook. | |
2388 | @end defvar | |
2389 | ||
2390 | @defvar c-mode-hook | |
2391 | @defvarx c++-mode-hook | |
2392 | @defvarx objc-mode-hook | |
2393 | @defvarx java-mode-hook | |
2394 | @defvarx idl-mode-hook | |
2395 | @defvarx pike-mode-hook | |
2396 | @defvarx awk-mode-hook | |
2397 | The language specific mode hooks. The appropriate one is run as the | |
2398 | last thing when you enter that language mode. | |
2399 | @end defvar | |
2400 | ||
2401 | Although these hooks are variables defined in @ccmode{}, you can give | |
2402 | them values before @ccmode{}'s code is loaded---indeed, this is the | |
2403 | only way to use @code{c-initialization-hook}. Their values aren't | |
2404 | overwritten when @ccmode{} gets loaded. | |
2405 | ||
2406 | Here's a simplified example of what you can add to your @file{.emacs} | |
2407 | file to do things whenever any @ccmode{} language is edited. See the | |
2408 | Emacs manuals for more information on customizing Emacs via hooks. | |
55f612f0 | 2409 | @xref{Sample Init File}, for a more complete sample @file{.emacs} |
4009494e GM |
2410 | file. |
2411 | ||
2412 | @example | |
2413 | (defun my-c-mode-common-hook () | |
2414 | ;; my customizations for all of c-mode and related modes | |
2415 | (no-case-fold-search) | |
2416 | ) | |
2417 | (add-hook 'c-mode-common-hook 'my-c-mode-common-hook) | |
2418 | @end example | |
2419 | ||
2420 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
2421 | @node Style Variables, Styles, CC Hooks, Config Basics | |
2422 | @comment node-name, next, previous, up | |
2423 | @section Style Variables | |
2424 | @cindex styles | |
2425 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
2426 | ||
2427 | @cindex style variables | |
2428 | The variables that @ccmode{}'s style system control are called | |
2429 | @dfn{style variables}. Note that style variables are ordinary Lisp | |
2430 | variables, which the style system initializes; you can change their | |
1df7defd | 2431 | values at any time (e.g., in a hook function). The style system can |
4009494e GM |
2432 | also set other variables, to some extent. @xref{Styles}. |
2433 | ||
2434 | @dfn{Style variables} are handled specially in several ways: | |
2435 | ||
2436 | @itemize @bullet | |
2437 | @item | |
2438 | Style variables are by default buffer-local variables. However, they | |
2439 | can instead be made global by setting | |
2440 | @code{c-style-variables-are-local-p} to @code{nil} before @ccmode{} is | |
2441 | initialized. | |
2442 | ||
2443 | @item | |
2444 | @vindex c-old-style-variable-behavior | |
2445 | @vindex old-style-variable-behavior (c-) | |
2446 | The default global binding of any style variable (with two exceptions | |
2447 | - see below) is the special symbol @code{set-from-style}. When the | |
2448 | style system initializes a buffer-local copy of a style variable for a | |
2449 | @ccmode{} buffer, if its global binding is still that symbol then it | |
2450 | will be set from the current style. Otherwise it will retain its | |
2451 | global default@footnote{This is a big change from versions of | |
2452 | @ccmode{} earlier than 5.26, where such settings would get overridden | |
2453 | by the style system unless special precautions were taken. That was | |
2454 | changed since it was counterintuitive and confusing, especially to | |
2455 | novice users. If your configuration depends on the old overriding | |
2456 | behavior, you can set the variable | |
2457 | @code{c-old-style-variable-behavior} to non-@code{nil}.}. This | |
2458 | ``otherwise'' happens, for example, when you've set the variable with | |
2459 | @code{setq} at the top level of your @file{.emacs} (@pxref{Config | |
2460 | Basics}). | |
2461 | ||
2462 | @item | |
2463 | The style variable @code{c-offsets-alist} (@pxref{c-offsets-alist}) is | |
2464 | an association list with an element for each syntactic symbol. It's | |
2465 | handled a little differently from the other style variables. It's | |
2466 | default global binding is the empty list @code{nil}, rather than | |
2467 | @code{set-from-style}. Before the style system is initialized, you | |
2468 | can add individual elements to @code{c-offsets-alist} by calling | |
2469 | @code{c-set-offset}(@pxref{c-offsets-alist}) just like you would set | |
2470 | other style variables with @code{setq}. Those elements will then | |
2471 | prevail when the style system later initializes a buffer-local copy of | |
2472 | @code{c-offsets-alist}. | |
2473 | ||
2474 | @item | |
2475 | The style variable @code{c-special-indent-hook} is also handled in a | |
2476 | special way. Styles can only add functions to this hook, not remove | |
2477 | them, so any global settings you put on it are always | |
2478 | preserved@footnote{This did not change in version 5.26.}. The value | |
2479 | you give this variable in a style definition can be either a function | |
2480 | or a list of functions. | |
2481 | ||
2482 | @item | |
2483 | The global bindings of the style variables get captured in the special | |
2484 | @code{user} style when the style system is first initialized. | |
2485 | @xref{Built-in Styles}, for details. | |
2486 | @end itemize | |
2487 | ||
2488 | The style variables are:@* | |
2489 | @code{c-indent-comment-alist}, | |
2490 | @code{c-indent-comments-syntactically-p} (@pxref{Indentation | |
2491 | Commands});@* | |
2492 | @code{c-doc-comment-style} (@pxref{Doc Comments});@* | |
2493 | @code{c-block-comment-prefix}, @code{c-comment-prefix-regexp} | |
2494 | (@pxref{Custom Filling and Breaking});@* | |
2495 | @code{c-hanging-braces-alist} (@pxref{Hanging Braces});@* | |
2496 | @code{c-hanging-colons-alist} (@pxref{Hanging Colons});@* | |
2497 | @code{c-hanging-semi&comma-criteria} (@pxref{Hanging Semicolons and | |
2498 | Commas});@* | |
2499 | @code{c-cleanup-list} (@pxref{Clean-ups});@* | |
2500 | @code{c-basic-offset} (@pxref{Customizing Indentation});@* | |
2501 | @code{c-offsets-alist} (@pxref{c-offsets-alist});@* | |
2502 | @code{c-comment-only-line-offset} (@pxref{Comment Line-Up});@* | |
2503 | @code{c-special-indent-hook}, @code{c-label-minimum-indentation} | |
2504 | (@pxref{Other Indentation});@* | |
2505 | @code{c-backslash-column}, @code{c-backslash-max-column} | |
2506 | (@pxref{Custom Macros}). | |
2507 | ||
2508 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
2509 | @node Styles, , Style Variables, Config Basics | |
2510 | @comment node-name, next, previous, up | |
2511 | @section Styles | |
2512 | @cindex styles | |
2513 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
2514 | ||
2515 | By @dfn{style} we mean the layout of the code---things like how many | |
2516 | columns to indent a block of code, whether an opening brace gets | |
2517 | indented to the level of the code it encloses, or of the construct | |
2518 | that introduces it, or ``hangs'' at the end of a line. | |
2519 | ||
2520 | Most people only need to edit code formatted in just a few well-defined | |
2521 | and consistent styles. For example, their organization might impose a | |
2522 | ``blessed'' style that all its programmers must conform to. Similarly, | |
2523 | people who work on GNU software will have to use the GNU coding style. | |
2524 | Some shops are more lenient, allowing a variety of coding styles, and as | |
2525 | programmers come and go, there could be a number of styles in use. For | |
2526 | this reason, @ccmode{} makes it convenient for you to set up logical | |
2527 | groupings of customizations called @dfn{styles}, associate a single name | |
2528 | for any particular style, and pretty easily start editing new or | |
2529 | existing code using these styles. | |
2530 | ||
847ccf7c AM |
2531 | As an alternative to writing a style definition yourself, you can have |
2532 | @ccmode{} @dfn{guess} (at least part of) your style by looking at an | |
2533 | already formatted piece of your code, @ref{Guessing the Style}. | |
2534 | ||
4009494e | 2535 | @menu |
91af3942 PE |
2536 | * Built-in Styles:: |
2537 | * Choosing a Style:: | |
2538 | * Adding Styles:: | |
2539 | * Guessing the Style:: | |
2540 | * File Styles:: | |
4009494e GM |
2541 | @end menu |
2542 | ||
4009494e GM |
2543 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
2544 | @node Built-in Styles, Choosing a Style, Styles, Styles | |
2545 | @comment node-name, next, previous, up | |
2546 | @subsection Built-in Styles | |
2547 | @cindex styles, built-in | |
2548 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
2549 | ||
2550 | If you're lucky, one of @ccmode{}'s built-in styles might be just | |
2551 | what you're looking for. These are: | |
2552 | ||
2553 | @table @code | |
2554 | @item gnu | |
2555 | @cindex GNU style | |
2556 | Coding style blessed by the Free Software Foundation | |
2557 | for C code in GNU programs. | |
2558 | ||
2559 | @item k&r | |
2560 | @cindex K&R style | |
2561 | The classic Kernighan and Ritchie style for C code. | |
2562 | ||
2563 | @item bsd | |
2564 | @cindex BSD style | |
2565 | Also known as ``Allman style'' after Eric Allman. | |
2566 | ||
2567 | @item whitesmith | |
2568 | @cindex Whitesmith style | |
2569 | Popularized by the examples that came with Whitesmiths C, an early | |
2570 | commercial C compiler. | |
2571 | ||
2572 | @item stroustrup | |
2573 | @cindex Stroustrup style | |
2574 | The classic Stroustrup style for C++ code. | |
2575 | ||
2576 | @item ellemtel | |
2577 | @cindex Ellemtel style | |
2578 | Popular C++ coding standards as defined by ``Programming in C++, Rules | |
2579 | and Recommendations,'' Erik Nyquist and Mats Henricson, | |
2580 | Ellemtel@footnote{This document is available at | |
2581 | @uref{http://www.doc.ic.ac.uk/lab/cplus/c++.rules/} among other | |
2582 | places.}. | |
2583 | @c N.B. This URL was still valid at 2005/8/28 (ACM). | |
2584 | ||
2585 | @item linux | |
2586 | @cindex Linux style | |
2587 | C coding standard for Linux (the kernel). | |
2588 | ||
2589 | @item python | |
2590 | @cindex Python style | |
2591 | C coding standard for Python extension modules@footnote{Python is a | |
2592 | high level scripting language with a C/C++ foreign function interface. | |
2593 | For more information, see @uref{http://www.python.org/}.}. | |
2594 | ||
2595 | @item java | |
2596 | @cindex Java style | |
2597 | The style for editing Java code. Note that the default | |
2598 | value for @code{c-default-style} installs this style when you enter | |
2599 | @code{java-mode}. | |
2600 | ||
2601 | @item awk | |
2602 | @cindex AWK style | |
2603 | The style for editing AWK code. Note that the default value for | |
2604 | @code{c-default-style} installs this style when you enter | |
2605 | @code{awk-mode}. | |
2606 | ||
2607 | @item user | |
2608 | @cindex User style | |
2609 | This is a special style created by you. It consists of the factory | |
2610 | defaults for all the style variables as modified by the customizations | |
2611 | you do either with the Customization interface or by writing | |
2612 | @code{setq}s and @code{c-set-offset}s at the top level of your | |
2613 | @file{.emacs} file (@pxref{Config Basics}). The style system creates | |
2614 | this style as part of its initialization and doesn't modify it | |
2615 | afterwards. | |
2616 | @end table | |
2617 | ||
2618 | ||
2619 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
2620 | @node Choosing a Style, Adding Styles, Built-in Styles, Styles | |
2621 | @comment node-name, next, previous, up | |
2622 | @subsection Choosing a Style | |
2623 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
2624 | ||
2625 | When you create a new buffer, its style will be set from | |
2626 | @code{c-default-style}. The factory default is the style @code{gnu}, | |
2627 | except in Java and AWK modes where it's @code{java} and @code{awk}. | |
2628 | ||
2629 | Remember that if you set a style variable with the Customization | |
2630 | interface or at the top level of your @file{.emacs} file before the | |
2f0c93d1 | 2631 | style system is initialized (@pxref{Config Basics}), this setting will |
4009494e GM |
2632 | override the one that the style system would have given the variable. |
2633 | ||
2634 | To set a buffer's style interactively, use the command @kbd{C-c .} | |
2635 | (@pxref{Other Commands}). To set it from a file's local variable | |
2636 | list, @ref{File Styles}. | |
2637 | ||
2638 | @defopt c-default-style | |
2639 | @vindex default-style (c-) | |
2640 | This variable specifies which style to install by default in new | |
2641 | buffers. It takes either a style name string, or an association list | |
2642 | of major mode symbols to style names: | |
2643 | ||
2644 | @enumerate | |
2645 | @item | |
2646 | When @code{c-default-style} is a string, it must be an existing style | |
2647 | name. This style is then used for all modes. | |
2648 | ||
2649 | @item | |
2650 | When @code{c-default-style} is an association list, the mode language | |
2651 | is looked up to find a style name string. | |
2652 | ||
2653 | @item | |
2654 | If @code{c-default-style} is an association list where the mode | |
2655 | language mode isn't found then the special symbol @samp{other} is | |
2656 | looked up. If it's found then the associated style is used. | |
2657 | ||
2658 | @item | |
2659 | If @samp{other} is not found then the @samp{gnu} style is used. | |
2660 | @end enumerate | |
2661 | ||
2662 | In all cases, the style described in @code{c-default-style} is installed | |
2663 | @emph{before} the language hooks are run, so you can always override | |
2664 | this setting by including an explicit call to @code{c-set-style} in your | |
2665 | language mode hook, or in @code{c-mode-common-hook}. | |
2666 | ||
2667 | The standard value of @code{c-default-style} is @w{@code{((java-mode | |
2668 | . "java") (awk-mode . "awk") (other . "gnu"))}}. | |
2669 | @end defopt | |
2670 | ||
2671 | @defvar c-indentation-style | |
2672 | @vindex indentation-style (c-) | |
2673 | This variable always contains the buffer's current style name, as a | |
2674 | string. | |
2675 | @end defvar | |
2676 | ||
4009494e | 2677 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
847ccf7c | 2678 | @node Adding Styles, Guessing the Style, Choosing a Style, Styles |
4009494e GM |
2679 | @comment node-name, next, previous, up |
2680 | @subsection Adding and Amending Styles | |
2681 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
2682 | ||
2683 | If none of the built-in styles is appropriate, you'll probably want to | |
2684 | create a new @dfn{style definition}, possibly based on an existing | |
2685 | style. To do this, put the new style's settings into a list with the | |
f99f1641 | 2686 | following format; the list can then be passed as an argument to the |
4009494e | 2687 | function @code{c-add-style}. You can see an example of a style |
55f612f0 | 2688 | definition in @ref{Sample Init File}. |
4009494e GM |
2689 | |
2690 | @cindex style definition | |
2691 | @c @defvr {List} style definition | |
2692 | @table @asis | |
2693 | @item Structure of a Style Definition List | |
2694 | ([@var{base-style}] [(@var{variable} . @var{value}) @dots{}]) | |
2695 | ||
2696 | Optional @var{base-style}, if present, must be a string which is the | |
2697 | name of the @dfn{base style} from which this style inherits. At most | |
2698 | one @var{base-style} is allowed in a style definition. If | |
2699 | @var{base-style} is not specified, the style inherits from the table | |
2700 | of factory default values@footnote{This table is stored internally in | |
2701 | the variable c-fallback-style.} instead. All styles eventually | |
2702 | inherit from this internal table. Style loops generate errors. The | |
2703 | list of pre-existing styles can be seen in @ref{Built-in Styles}. | |
2704 | ||
2705 | The dotted pairs (@var{variable} . @var{value}) each consist of a | |
2706 | variable and the value it is to be set to when the style is later | |
2707 | activated.@footnote{Note that if the variable has been given a value | |
2708 | by the Customization interface or a @code{setq} at the top level of | |
2709 | your @file{.emacs}, this value will override the one the style system | |
2710 | tries to give it. @xref{Config Basics}.} The variable can be either a | |
2711 | @ccmode{} style variable or an arbitrary Emacs variable. In the | |
2712 | latter case, it is @emph{not} made buffer-local by the @ccmode{} style | |
2713 | system. | |
2714 | @c @end defvr | |
2715 | ||
2716 | Two variables are treated specially in the dotted pair list: | |
2717 | ||
2718 | @table @code | |
2719 | @item c-offsets-alist | |
2720 | The value is in turn a list of dotted pairs of the form | |
2721 | ||
2722 | @example | |
2723 | (@r{@var{syntactic-symbol}} . @r{@var{offset}}) | |
2724 | @end example | |
2725 | ||
2726 | as described in @ref{c-offsets-alist}. These are passed to | |
2727 | @code{c-set-offset} so there is no need to set every syntactic symbol | |
2728 | in your style, only those that are different from the inherited style. | |
2729 | ||
2730 | @item c-special-indent-hook | |
2731 | The value is added to @code{c-special-indent-hook} using | |
2732 | @code{add-hook}, so any functions already on it are kept. If the value | |
2733 | is a list, each element of the list is added with @code{add-hook}. | |
2734 | @end table | |
2735 | @end table | |
2736 | ||
2737 | Styles are kept in the @code{c-style-alist} variable, but you | |
2738 | should never modify this variable directly. Instead, @ccmode{} | |
2739 | provides the function @code{c-add-style} for this purpose. | |
2740 | ||
2741 | @defun c-add-style stylename description &optional set-p | |
2742 | @findex add-style (c-) | |
2743 | Add or update a style called @var{stylename}, a string. | |
2744 | @var{description} is the new style definition in the form described | |
2745 | above. If @var{stylename} already exists in @code{c-style-alist} then | |
2746 | it is replaced by @var{description}. (Note, this replacement is | |
2747 | total. The old style is @emph{not} merged into the new one.) | |
2748 | Otherwise, a new style is added. | |
2749 | ||
2750 | If the optional @var{set-p} is non-@code{nil} then the new style is | |
2751 | applied to the current buffer as well. The use of this facility is | |
2752 | deprecated and it might be removed from @ccmode{} in a future release. | |
2753 | You should use @code{c-set-style} instead. | |
2754 | ||
2755 | The sample @file{.emacs} file provides a concrete example of how a new | |
55f612f0 | 2756 | style can be added and automatically set. @xref{Sample Init File}. |
4009494e GM |
2757 | @end defun |
2758 | ||
2759 | @defvar c-style-alist | |
2760 | @vindex style-alist (c-) | |
2761 | This is the variable that holds the definitions for the styles. It | |
2762 | should not be changed directly; use @code{c-add-style} instead. | |
2763 | @end defvar | |
2764 | ||
847ccf7c AM |
2765 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
2766 | @node Guessing the Style, File Styles, Adding Styles, Styles | |
2767 | @comment node-name, next, previous, up | |
2768 | @subsection Guessing the Style | |
2769 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
2770 | ||
2771 | Instead of specifying a style, you can get @ccmode{} to @dfn{guess} | |
2772 | your style by examining an already formatted code buffer. @ccmode{} | |
2773 | then determines the ''most frequent'' offset (@pxref{c-offsets-alist}) | |
2774 | for each of the syntactic symbols (@pxref{Indentation Engine Basics}) | |
2775 | encountered in the buffer, and the ''most frequent'' value of | |
2776 | c-basic-offset (@pxref{Customizing Indentation}), then merges the | |
2777 | current style with these ''guesses'' to form a new style. This | |
2778 | combined style is known as the @dfn{guessed style}. | |
2779 | ||
2780 | To do this, call @code{c-guess} (or one of the other 5 guessing | |
2781 | commands) on your sample buffer. The analysis of your code may take | |
2782 | some time. | |
2783 | ||
2784 | You can then set the guessed style in any @ccmode{} buffer with | |
2785 | @code{c-guess-install}. You can display the style with | |
2786 | @code{c-guess-view}, and preserve it by copying it into your | |
2787 | @file{.emacs} for future use, preferably after editing it. | |
2788 | ||
2789 | @table @asis | |
2790 | @item @kbd{M-x c-guess-no-install} | |
2791 | @itemx @kbd{M-x c-guess-buffer-no-install} | |
2792 | @itemx @kbd{M-x c-guess-region-no-install} | |
2793 | @findex c-guess-no-install | |
2794 | @findex c-guess-buffer-no-install | |
2795 | @findex c-guess-region-no-install | |
2796 | @findex guess-no-install (c-) | |
2797 | @findex guess-buffer-no-install (c-) | |
2798 | @findex guess-region-no-install (c-) | |
2799 | These commands analyze a part of the current buffer and guess the | |
2800 | style from it. | |
2801 | ||
2802 | The part of the buffer examined is either the region | |
2803 | (@code{c-guess-region-no-install}), the entire buffer | |
2804 | (@code{c-guess-buffer-no-install}), or the first | |
2805 | @code{c-guess-region-max} bytes (@code{c-guess-no-install}). | |
2806 | ||
2807 | Each of these commands can be given an optional prefix argument. This | |
2808 | instructs @ccmode{} to combine the new guesses with the current | |
2809 | guesses before forming the guessed style. | |
2810 | @end table | |
2811 | ||
2812 | @table @asis | |
2813 | @item @kbd{M-x c-guess} | |
2814 | @itemx @kbd{M-x c-guess-buffer} | |
2815 | @itemx @kbd{M-x c-guess-region} | |
2816 | @findex c-guess | |
2817 | @findex c-guess-buffer | |
2818 | @findex c-guess-region | |
2819 | @findex guess (c-) | |
2820 | @findex guess-buffer (c-) | |
2821 | @findex guess-region (c-) | |
2822 | These commands analyze a part of the current buffer, guess the style | |
2823 | from it, then install the guessed style on the buffer. The guessed | |
2824 | style is given a name based on the buffer's absolute file name, and | |
2825 | you can then set this style on any @ccmode{} buffer with @kbd{C-c .}. | |
2826 | ||
2827 | The part of the buffer examined is either the region | |
2828 | (@code{c-guess-region}), the entire buffer (@code{c-guess-buffer}), or | |
2829 | the first @code{c-guess-region-max} bytes (@code{c-guess}). | |
2830 | ||
2831 | Each of these commands can be given an optional prefix argument. This | |
2832 | instructs @ccmode{} to combine the new guesses with the current | |
2833 | guesses before forming the guessed style. | |
2834 | @end table | |
2835 | ||
2836 | @defopt c-guess-region-max | |
2837 | @vindex guess-region-max (c-) | |
2838 | This variable, default 50000, is the size in bytes of the buffer | |
2839 | portion examined by c-guess and c-guess-no-install. If set to | |
2840 | @code{nil}, the entire buffer is examined. | |
2841 | @end defopt | |
2842 | ||
2843 | @defopt c-guess-offset-threshold | |
2844 | @vindex guess-offset-threshold (c-) | |
2845 | This variable, default 10, is the maximum offset, either outwards or | |
2846 | inwards, which will be taken into account by the analysis process. | |
2847 | Any offset bigger than this will be ignored. For no limit, set this | |
2848 | variable to a large number. | |
2849 | @end defopt | |
2850 | ||
2851 | @table @asis | |
2852 | @item @kbd{M-x c-guess-install} | |
2853 | @findex c-guess-install | |
2854 | @findex guess-install (c-) | |
2855 | ||
2856 | Set the current buffer's style to the guessed style. This prompts you | |
2857 | to enter an optional new style name to give to the guessed style. By | |
2858 | default, this name is based on the buffer's absolute file name. You | |
2859 | can then use this style like any other. | |
2860 | ||
2861 | @item @kbd{M-x c-guess-view} | |
2862 | @findex c-guess-view | |
2863 | @findex guess-view (c-) | |
2864 | Display the most recently guessed style in a temporary buffer. This | |
2865 | display is in the form of a @code{c-add-style} form (@pxref{Adding | |
2866 | Styles}) which can be easily copied to your @file{.emacs}. You will | |
2867 | probably want to edit it first. | |
2868 | ||
2869 | The display of the guessed style contains these elements: | |
2870 | ||
2871 | @table @asis | |
2872 | @item Placeholder Name | |
2873 | You should replace this with a style name of your own. | |
2874 | @item Parent Style | |
2875 | The style current when the guessing began, from which the guessed | |
2876 | style inherits (@pxref{Config Basics}) the settings which weren't | |
2877 | guessed. | |
2878 | @item Guessed Offsets | |
2879 | These are the core result of the guessing process. Each of them is | |
2880 | marked by a comment. | |
2881 | @item Inherited Offsets | |
2882 | These are syntactic offsets which have been taken over from the parent | |
2883 | style. To avoid possible future conflicts, you should remove either | |
2884 | these offsets or the parent style name. | |
2885 | @end table | |
2886 | @end table | |
4009494e GM |
2887 | |
2888 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
847ccf7c | 2889 | @node File Styles, , Guessing the Style, Styles |
4009494e GM |
2890 | @comment node-name, next, previous, up |
2891 | @subsection File Styles | |
2892 | @cindex styles, file local | |
2893 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
2894 | ||
2895 | @cindex file local variables | |
2896 | ||
2897 | The Emacs manual describes how you can customize certain variables on a | |
2898 | per-file basis by including a @dfn{file local variable} block at the end | |
9879e263 | 2899 | of the file (@pxref{File Variables,, Local Variables in Files,@emacsman{}, |
4009494e GM |
2900 | @emacsmantitle{}}). |
2901 | ||
2902 | So far, you've only seen a functional interface for setting styles in | |
2903 | @ccmode{}, and this can't be used here. @ccmode{} fills the gap by | |
2904 | providing two variables for use in a file's local variable list. | |
2905 | Don't use them anywhere else! These allow you to customize the style | |
2906 | on a per-file basis: | |
2907 | ||
2908 | @defvar c-file-style | |
2909 | @vindex file-style (c-) | |
2910 | Set this variable to a style name string in the Local Variables list. | |
2911 | From now on, when you visit the file, @ccmode{} will automatically set | |
2912 | the file's style to this one using @code{c-set-style}. | |
2913 | @end defvar | |
2914 | ||
2915 | @defvar c-file-offsets | |
2916 | @vindex file-offsets (c-) | |
2917 | Set this variable (in the Local Variables list) to an association list | |
2918 | of the same format as @code{c-offsets-alist}. From now on, when you | |
2919 | visit the file, @ccmode{} will automatically institute these offsets | |
2920 | using @code{c-set-offset}. | |
2921 | @end defvar | |
2922 | ||
1df7defd | 2923 | Note that file style settings (i.e., @code{c-file-style}) are applied |
4009494e | 2924 | before file offset settings |
1df7defd | 2925 | (i.e., @code{c-file-offsets})@footnote{Also, if either of these are set |
4009494e GM |
2926 | in a file's local variable section, all the style variable values are |
2927 | made local to that buffer, even if | |
2928 | @code{c-style-variables-are-local-p} is @code{nil}. Since this | |
2929 | variable is virtually always non-@code{nil} anyhow, you're unlikely to | |
2930 | notice this effect.}. | |
2931 | ||
22556bc5 AM |
2932 | If you set any variable by the file local variables mechanism, that |
2933 | setting takes priority over all other settings, even those in your | |
2934 | mode hooks (@pxref{CC Hooks}). Any individual setting of a variable | |
2935 | will override one made through @code{c-file-style} or | |
2936 | @code{c-file-offsets}. | |
4009494e GM |
2937 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
2938 | @node Custom Filling and Breaking, Custom Auto-newlines, Config Basics, Top | |
2939 | @comment node-name, next, previous, up | |
2940 | @chapter Customizing Filling and Line Breaking | |
2941 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
2942 | ||
2943 | Since there's a lot of normal text in comments and string literals, | |
2944 | @ccmode{} provides features to edit these like in text mode. It does | |
2945 | this by hooking in on the different line breaking functions and tuning | |
2946 | relevant variables as necessary. | |
2947 | ||
2948 | @vindex c-comment-prefix-regexp | |
2949 | @vindex comment-prefix-regexp (c-) | |
2950 | @cindex comment line prefix | |
2951 | @vindex comment-start | |
2952 | @vindex comment-end | |
2953 | @vindex comment-start-skip | |
2954 | @vindex paragraph-start | |
2955 | @vindex paragraph-separate | |
2956 | @vindex paragraph-ignore-fill-prefix | |
2957 | @vindex adaptive-fill-mode | |
2958 | @vindex adaptive-fill-regexp | |
2959 | @vindex adaptive-fill-first-line-regexp | |
2960 | To make Emacs recognize comments and treat text in them as normal | |
2961 | paragraphs, @ccmode{} makes several standard | |
2962 | variables@footnote{@code{comment-start}, @code{comment-end}, | |
2963 | @code{comment-start-skip}, @code{paragraph-start}, | |
2964 | @code{paragraph-separate}, @code{paragraph-ignore-fill-prefix}, | |
2965 | @code{adaptive-fill-mode}, @code{adaptive-fill-regexp}, and | |
2966 | @code{adaptive-fill-first-line-regexp}.} buffer-local and modifies them | |
2967 | according to the language syntax and the comment line prefix. | |
2968 | ||
2969 | @defopt c-comment-prefix-regexp | |
2970 | @vindex comment-prefix-regexp (c-) | |
2971 | This style variable contains the regexp used to recognize the | |
2972 | @dfn{comment line prefix}, which is the line decoration that starts | |
2973 | every line in a comment. The variable is either the comment line | |
2974 | prefix itself, or (more usually) an association list with different | |
2975 | values for different languages. The symbol for the major mode is | |
2976 | looked up in the alist to get the regexp for the language, and if it | |
2977 | isn't found then the special symbol @samp{other} is looked up instead. | |
2978 | ||
2979 | When a comment line gets divided by @kbd{M-j} or the like, @ccmode{} | |
2f0c93d1 | 2980 | inserts the comment line prefix from a neighboring line at the start |
4009494e GM |
2981 | of the new line. The default value of c-comment-prefix-regexp is |
2982 | @samp{//+\\|\\**}, which matches C++ style line comments like | |
2983 | ||
2984 | @example | |
2985 | // blah blah | |
2986 | @end example | |
2987 | ||
2988 | @noindent | |
2989 | with two or more slashes in front of them, and the second and | |
2990 | subsequent lines of C style block comments like | |
2991 | ||
2992 | @example | |
2993 | @group | |
2994 | /* | |
2995 | * blah blah | |
2996 | */ | |
2997 | @end group | |
2998 | @end example | |
2999 | ||
3000 | @noindent | |
3001 | with zero or more stars at the beginning of every line. If you change | |
3002 | this variable, please make sure it still matches the comment starter | |
1df7defd | 3003 | (i.e., @code{//}) of line comments @emph{and} the line prefix inside |
4009494e GM |
3004 | block comments. |
3005 | ||
3006 | @findex c-setup-paragraph-variables | |
3007 | @findex setup-paragraph-variables (c-) | |
3008 | Also note that since @ccmode{} uses the value of | |
3009 | @code{c-comment-prefix-regexp} to set up several other variables at | |
3010 | mode initialization, there won't be any effect if you just change it | |
3011 | inside a @ccmode{} buffer. You need to call the command | |
3012 | @code{c-setup-paragraph-variables} too, to update those other | |
3013 | variables. That's also the case if you modify | |
3014 | @code{c-comment-prefix-regexp} in a mode hook, since @ccmode{} will | |
3015 | already have set up these variables before calling the hook. | |
3016 | @end defopt | |
3017 | ||
3018 | In comments, @ccmode{} uses @code{c-comment-prefix-regexp} to adapt | |
3019 | the line prefix from the other lines in the comment. | |
3020 | ||
3021 | @vindex adaptive-fill-mode | |
3022 | @cindex Adaptive Fill mode | |
3023 | @ccmode{} uses adaptive fill mode (@pxref{Adaptive Fill,,, emacs, GNU | |
3024 | Emacs Manual}) to make Emacs correctly keep the line prefix when | |
3025 | filling paragraphs. That also makes Emacs preserve the text | |
1df7defd | 3026 | indentation @emph{inside} the comment line prefix. E.g., in the |
4009494e GM |
3027 | following comment, both paragraphs will be filled with the left |
3028 | margins of the texts kept intact: | |
3029 | ||
3030 | @example | |
3031 | @group | |
3032 | /* Make a balanced b-tree of the nodes in the incoming | |
3033 | * stream. But, to quote the famous words of Donald E. | |
3034 | * Knuth, | |
3035 | * | |
3036 | * Beware of bugs in the above code; I have only | |
3037 | * proved it correct, not tried it. | |
3038 | */ | |
3039 | @end group | |
3040 | @end example | |
3041 | ||
3042 | @findex c-setup-filladapt | |
3043 | @findex setup-filladapt (c-) | |
3044 | @findex filladapt-mode | |
3045 | @vindex filladapt-mode | |
3046 | @cindex Filladapt mode | |
3047 | It's also possible to use other adaptive filling packages, notably Kyle | |
3048 | E. Jones' Filladapt package@footnote{It's available from | |
3049 | @uref{http://www.wonderworks.com/}. As of version 2.12, it does however | |
3050 | lack a feature that makes it work suboptimally when | |
3051 | @code{c-comment-prefix-regexp} matches the empty string (which it does | |
3052 | by default). A patch for that is available from | |
3053 | @uref{http://cc-mode.sourceforge.net/,, the CC Mode web site}.}, | |
3054 | @c 2005/11/22: The above is still believed to be the case. | |
3055 | which handles things like bulleted lists nicely. There's a convenience | |
3056 | function @code{c-setup-filladapt} that tunes the relevant variables in | |
1df7defd | 3057 | Filladapt for use in @ccmode{}. Call it from a mode hook, e.g., with |
4009494e GM |
3058 | something like this in your @file{.emacs}: |
3059 | ||
3060 | @example | |
3061 | (defun my-c-mode-common-hook () | |
3062 | (c-setup-filladapt) | |
3063 | (filladapt-mode 1)) | |
3064 | (add-hook 'c-mode-common-hook 'my-c-mode-common-hook) | |
3065 | @end example | |
3066 | ||
3067 | @defopt c-block-comment-prefix | |
3068 | @vindex block-comment-prefix (c-) | |
3069 | @vindex c-comment-continuation-stars | |
3070 | @vindex comment-continuation-stars (c-) | |
3071 | Normally the comment line prefix inserted for a new line inside a | |
3072 | comment is deduced from other lines in it. However there's one | |
3073 | situation when there's no hint about what the prefix should look like, | |
3074 | namely when a block comment is broken for the first time. This style | |
3075 | variable@footnote{In versions before 5.26, this variable was called | |
3076 | @code{c-comment-continuation-stars}. As a compatibility measure, | |
3077 | @ccmode{} still uses the value on that variable if it's set.} is used | |
3078 | then as the comment prefix. It defaults to @samp{* | |
3079 | }@footnote{Actually, this default setting of | |
3080 | @code{c-block-comment-prefix} typically gets overridden by the default | |
3081 | style @code{gnu}, which sets it to blank. You can see the line | |
3082 | splitting effect described here by setting a different style, | |
1df7defd | 3083 | e.g., @code{k&r} @xref{Choosing a Style}.}, which makes a comment |
4009494e GM |
3084 | |
3085 | @example | |
3086 | /* Got O(n^2) here, which is a Bad Thing. */ | |
3087 | @end example | |
3088 | ||
3089 | @noindent | |
3090 | break into | |
3091 | ||
3092 | @example | |
3093 | @group | |
3094 | /* Got O(n^2) here, which | |
3095 | * is a Bad Thing. */ | |
3096 | @end group | |
3097 | @end example | |
3098 | ||
3099 | Note that it won't work to adjust the indentation by putting leading | |
3100 | spaces in @code{c-block-comment-prefix}, since @ccmode{} still uses the | |
3101 | normal indentation engine to indent the line. Thus, the right way to | |
3102 | fix the indentation is by customizing the @code{c} syntactic symbol. It | |
3103 | defaults to @code{c-lineup-C-comments}, which handles the indentation of | |
3104 | most common comment styles, see @ref{Line-Up Functions}. | |
3105 | @end defopt | |
3106 | ||
3107 | @defopt c-ignore-auto-fill | |
3108 | @vindex ignore-auto-fill (c-) | |
3109 | When auto fill mode is enabled, @ccmode{} can selectively ignore it | |
1df7defd | 3110 | depending on the context the line break would occur in, e.g., to never |
4009494e GM |
3111 | break a line automatically inside a string literal. This variable |
3112 | takes a list of symbols for the different contexts where auto-filling | |
3113 | never should occur: | |
3114 | ||
3115 | @table @code | |
3116 | @item string | |
3117 | Inside a string or character literal. | |
3118 | @item c | |
3119 | Inside a C style block comment. | |
3120 | @item c++ | |
3121 | Inside a C++ style line comment. | |
3122 | @item cpp | |
3123 | Inside a preprocessor directive. | |
3124 | @item code | |
1df7defd | 3125 | Anywhere else, i.e., in normal code. |
4009494e GM |
3126 | @end table |
3127 | ||
3128 | By default, @code{c-ignore-auto-fill} is set to @code{(string cpp | |
3129 | code)}, which means that when auto-fill mode is activated, | |
3130 | auto-filling only occurs in comments. In literals, it's often | |
3131 | desirable to have explicit control over newlines. In preprocessor | |
3132 | directives, the necessary @samp{\} escape character before the newline | |
3133 | is not automatically inserted, so an automatic line break would | |
3134 | produce invalid code. In normal code, line breaks are normally | |
3135 | dictated by some logical structure in the code rather than the last | |
3136 | whitespace character, so automatic line breaks there will produce poor | |
3137 | results in the current implementation. | |
3138 | @end defopt | |
3139 | ||
3140 | @vindex comment-multi-line | |
9879e263 AS |
3141 | If inside a comment and @code{comment-multi-line} (@pxref{Auto |
3142 | Fill,,,@emacsman{}, @emacsmantitle{}} is non-@code{nil}, the | |
3143 | indentation and | |
4009494e GM |
3144 | line prefix are preserved. If inside a comment and |
3145 | @code{comment-multi-line} is @code{nil}, a new comment of the same | |
3146 | type is started on the next line and indented as appropriate for | |
3147 | comments. | |
3148 | ||
3149 | Note that @ccmode{} sets @code{comment-multi-line} to @code{t} at | |
3150 | startup. The reason is that @kbd{M-j} could otherwise produce sequences | |
3151 | of single line block comments for texts that should logically be treated | |
3152 | as one comment, and the rest of the paragraph handling code | |
1df7defd | 3153 | (e.g., @kbd{M-q} and @kbd{M-a}) can't cope with that, which would lead to |
4009494e GM |
3154 | inconsistent behavior. |
3155 | ||
3156 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
3157 | @node Custom Auto-newlines, Clean-ups, Custom Filling and Breaking, Top | |
3158 | @comment node-name, next, previous, up | |
3159 | @chapter Customizing Auto-newlines | |
3160 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
3161 | ||
3162 | @ccmode{} determines whether to insert auto-newlines in two basically | |
3163 | different ways, depending on the character just typed: | |
3164 | ||
3165 | @table @asis | |
3166 | @item Braces and Colons | |
3167 | @ccmode{} first determines the syntactic context of the brace or colon | |
3168 | (@pxref{Syntactic Symbols}), then looks for a corresponding element in | |
f99f1641 | 3169 | an alist. This element specifies where to put newlines: this is any |
4009494e GM |
3170 | combination of before and after the brace or colon. If no alist |
3171 | element is found, newlines are inserted both before and after a brace, | |
3172 | but none are inserted around a colon. See @ref{Hanging Braces} and | |
3173 | @ref{Hanging Colons}. | |
3174 | ||
3175 | @item Semicolons and Commas | |
3176 | The variable @code{c-hanging-semi&comma-criteria} contains a list of | |
3177 | functions which determine whether to insert a newline after a newly | |
3178 | typed semicolon or comma. @xref{Hanging Semicolons and Commas}. | |
3179 | @end table | |
3180 | ||
3181 | The names of these configuration variables contain @samp{hanging} | |
3182 | because they let you @dfn{hang} the pertinent characters. A character | |
3183 | which introduces a C construct is said to @dfn{hang on the right} when | |
3184 | it appears at the end of a line after other code, being separated by a | |
3185 | line break from the construct it introduces, like the opening brace in: | |
3186 | ||
3187 | @example | |
3188 | @group | |
3189 | while (i < MAX) @{ | |
3190 | total += entry[i]; | |
3191 | entry [i++] = 0; | |
3192 | @} | |
3193 | @end group | |
3194 | @end example | |
3195 | ||
3196 | @noindent | |
3197 | A character @dfn{hangs on the left} when it appears at the start of | |
3198 | the line after the construct it closes off, like the above closing | |
3199 | brace. | |
3200 | ||
3201 | The next chapter, ``Clean-ups'', describes how to configure @ccmode{} | |
3202 | to remove these automatically added newlines in certain specific | |
3203 | circumstances. @xref{Clean-ups}. | |
3204 | ||
3205 | @menu | |
3206 | * Hanging Braces:: | |
3207 | * Hanging Colons:: | |
3208 | * Hanging Semicolons and Commas:: | |
3209 | @end menu | |
3210 | ||
3211 | ||
3212 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
3213 | @node Hanging Braces, Hanging Colons, Custom Auto-newlines, Custom Auto-newlines | |
3214 | @comment node-name, next, previous, up | |
3215 | @section Hanging Braces | |
3216 | @cindex hanging braces | |
3217 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
3218 | ||
3219 | To specify which kinds of braces you want auto-newlines put around, | |
3220 | you set the style variable @code{c-hanging-braces-alist}. Its | |
3221 | structure and semantics are described in this section. Details of how | |
3222 | to set it up, and its relationship to CC Mode's style system are given | |
3223 | in @ref{Style Variables}. | |
3224 | ||
3225 | Say you wanted an auto-newline after (but not before) the following | |
3226 | @samp{@{}: | |
3227 | ||
3228 | @example | |
3229 | if (foo < 17) @{ | |
3230 | @end example | |
3231 | ||
3232 | @noindent | |
3233 | First you need to find the @dfn{syntactic context} of the brace---type | |
3234 | a @key{RET} before the brace to get it on a line of its | |
3235 | own@footnote{Also insert a @samp{\} at the end of the previous line if | |
3236 | you're in AWK Mode.}, then type @kbd{C-c C-s}. That will tell you | |
3237 | something like: | |
3238 | ||
3239 | @example | |
3240 | ((substatement-open 1061)) | |
3241 | @end example | |
3242 | ||
3243 | @noindent | |
3244 | So here you need to put the entry @code{(substatement-open . (after))} | |
3245 | into @code{c-hanging-braces-alist}. | |
3246 | ||
3247 | If you don't want any auto-newlines for a particular syntactic symbol, | |
3248 | put this into @code{c-hanging-braces-alist}: | |
3249 | ||
3250 | @example | |
3251 | (brace-entry-open) | |
3252 | @end example | |
3253 | ||
3254 | If some brace syntactic symbol is not in @code{c-hanging-brace-alist}, | |
3255 | its entry is taken by default as @code{(before after)}---insert a | |
3256 | newline both before and after the brace. In place of a | |
3257 | ``before/after'' list you can specify a function in this alist---this | |
3258 | is useful when the auto newlines depend on the code around the brace. | |
3259 | ||
3260 | @defopt c-hanging-braces-alist | |
3261 | @vindex hanging-braces-alist (c-) | |
3262 | ||
3263 | This variable is an association list which maps syntactic symbols to | |
3264 | lists of places to insert a newline. @xref{Association | |
3265 | Lists,,,@lispref{}, @lispreftitle{}}. The key of each element is the | |
3266 | syntactic symbol, the associated value is either @code{nil}, a list, | |
3267 | or a function. | |
3268 | ||
3269 | @table @asis | |
f99f1641 | 3270 | @item The Key: the syntactic symbol |
4009494e GM |
3271 | The syntactic symbols that are useful as keys in this list are |
3272 | @code{brace-list-intro}, @code{statement-cont}, | |
3273 | @code{inexpr-class-open}, @code{inexpr-class-close}, and all the | |
3274 | @code{*-open} and @code{*-close} symbols. @xref{Syntactic Symbols}, | |
3275 | for a more detailed description of these syntactic symbols, except for | |
3276 | @code{inexpr-class-open} and @code{inexpr-class-close}, which aren't | |
3277 | actual syntactic symbols. Elements with any other value as a key get | |
3278 | ignored. | |
3279 | ||
3280 | The braces of anonymous inner classes in Java are given the special | |
3281 | symbols @code{inexpr-class-open} and @code{inexpr-class-close}, so that | |
3282 | they can be distinguished from the braces of normal classes@footnote{The | |
3283 | braces of anonymous classes produce a combination of | |
3284 | @code{inexpr-class}, and @code{class-open} or @code{class-close} in | |
3285 | normal indentation analysis.}. | |
3286 | ||
3287 | Note that the aggregate constructs in Pike mode, @samp{(@{}, @samp{@})}, | |
3288 | @samp{([}, @samp{])}, and @samp{(<}, @samp{>)}, do not count as brace | |
3289 | lists in this regard, even though they do for normal indentation | |
3290 | purposes. It's currently not possible to set automatic newlines on | |
3291 | these constructs. | |
3292 | ||
f99f1641 | 3293 | @item The associated value: the ``ACTION'' list or function |
4009494e GM |
3294 | The value associated with each syntactic symbol in this association |
3295 | list is called an @var{action}, which can be either a list or a | |
3296 | function which returns a list. @xref{Custom Braces}, for how to use | |
3297 | a function as a brace hanging @var{action}. | |
3298 | ||
3299 | The list @var{action} (or the list returned by @var{action} when it's | |
3300 | a function) contains some combination of the symbols @code{before} and | |
3301 | @code{after}, directing @ccmode{} where to put newlines in | |
3302 | relationship to the brace being inserted. Thus, if the list contains | |
3303 | only the symbol @code{after}, then the brace hangs on the right side | |
3304 | of the line, as in: | |
3305 | ||
3306 | @example | |
3307 | // here, open braces always `hang' | |
3308 | void spam( int i ) @{ | |
3309 | if( i == 7 ) @{ | |
3310 | dosomething(i); | |
3311 | @} | |
3312 | @} | |
3313 | @end example | |
3314 | ||
3315 | When the list contains both @code{after} and @code{before}, the braces | |
3316 | will appear on a line by themselves, as shown by the close braces in | |
3317 | the above example. The list can also be empty, in which case newlines | |
3318 | are added neither before nor after the brace. | |
3319 | @end table | |
3320 | ||
3321 | If a syntactic symbol is missing entirely from | |
3322 | @code{c-hanging-braces-alist}, it's treated in the same way as an | |
3323 | @var{action} with a list containing @code{before} and @code{after}, so | |
3324 | that braces by default end up on their own line. | |
3325 | ||
3326 | For example, the default value of @code{c-hanging-braces-alist} is: | |
3327 | ||
3328 | @example | |
3329 | ((brace-list-open) | |
3330 | (brace-entry-open) | |
3331 | (statement-cont) | |
3332 | (substatement-open after) | |
3333 | (block-close . c-snug-do-while) | |
3334 | (extern-lang-open after) | |
3335 | (namespace-open after) | |
3336 | (module-open after) | |
3337 | (composition-open after) | |
3338 | (inexpr-class-open after) | |
3339 | (inexpr-class-close before)) | |
3340 | @end example | |
3341 | ||
3342 | @noindent which says that @code{brace-list-open}, | |
3343 | @code{brace-entry-open} and @code{statement-cont}@footnote{Brace lists | |
3344 | inside statements, such as initializers for static array variables | |
3345 | inside functions in C, are recognized as @code{statement-cont}. All | |
3346 | normal substatement blocks are recognized with other symbols.} braces | |
3347 | should both hang on the right side and allow subsequent text to follow | |
3348 | on the same line as the brace. Also, @code{substatement-open}, | |
3349 | @code{extern-lang-open}, and @code{inexpr-class-open} braces should hang | |
3350 | on the right side, but subsequent text should follow on the next line. | |
3351 | The opposite holds for @code{inexpr-class-close} braces; they won't | |
3352 | hang, but the following text continues on the same line. Here, in the | |
3353 | @code{block-close} entry, you also see an example of using a function as | |
3354 | an @var{action}. In all other cases, braces are put on a line by | |
3355 | themselves. | |
3356 | @end defopt | |
3357 | ||
3358 | @menu | |
3359 | * Custom Braces:: | |
3360 | @end menu | |
3361 | ||
3362 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
3363 | @node Custom Braces, , Hanging Braces, Hanging Braces | |
3364 | @comment node-name, next, previous, up | |
3365 | @subsection Custom Brace Hanging | |
3366 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
3367 | ||
3368 | @vindex c-hanging-braces-alist | |
3369 | @vindex hanging-braces-alist (c-) | |
3370 | @cindex action functions | |
3371 | Syntactic symbols aren't the only place where you can customize | |
3372 | @ccmode{} with the lisp equivalent of callback functions. Remember | |
3373 | that @var{action}s are usually a list containing some combination of | |
3374 | the symbols @code{before} and @code{after} (@pxref{Hanging Braces}). | |
3375 | For more flexibility, you can instead specify brace ``hanginess'' by | |
3376 | giving a syntactic symbol an @dfn{action function} in | |
3377 | @code{c-hanging-braces-alist}; this function determines the | |
3378 | ``hanginess'' of a brace, usually by looking at the code near it. | |
3379 | ||
3380 | @cindex customization, brace hanging | |
3381 | An action function is called with two arguments: the syntactic symbol | |
1df7defd | 3382 | for the brace (e.g., @code{substatement-open}), and the buffer position |
4009494e | 3383 | where the brace has been inserted. Point is undefined on entry to an |
1df7defd | 3384 | action function, but the function must preserve it (e.g., by using |
4009494e GM |
3385 | @code{save-excursion}). The return value should be a list containing |
3386 | some combination of @code{before} and @code{after}, including neither | |
1df7defd | 3387 | of them (i.e., @code{nil}). |
4009494e GM |
3388 | |
3389 | @defvar c-syntactic-context | |
3390 | @vindex syntactic-context (c-) | |
3391 | During the call to the indentation or brace hanging @var{action} | |
3392 | function, this variable is bound to the full syntactic analysis list. | |
3393 | This might be, for example, @samp{((block-close 73))}. Don't ever | |
3394 | give @code{c-syntactic-context} a value yourself---this would disrupt | |
3395 | the proper functioning of @ccmode{}. | |
3396 | ||
3397 | This variable is also bound in three other circumstances: | |
3398 | (i)@w{ }when calling a c-hanging-semi&comma-criteria function | |
3399 | (@pxref{Hanging Semicolons and Commas}); (ii)@w{ }when calling a | |
3400 | line-up function (@pxref{Custom Line-Up}); (iii)@w{ }when calling a | |
3401 | c-special-indent-hook function (@pxref{Other Indentation}). | |
3402 | @end defvar | |
3403 | ||
3404 | As an example, @ccmode{} itself uses this feature to dynamically | |
3405 | determine the hanginess of braces which close ``do-while'' | |
3406 | constructs: | |
3407 | ||
3408 | @example | |
3409 | void do_list( int count, char** atleast_one_string ) | |
3410 | @{ | |
3411 | int i=0; | |
3412 | do @{ | |
3413 | handle_string( atleast_one_string[i] ); | |
3414 | i++; | |
3415 | @} while( i < count ); | |
3416 | @} | |
3417 | @end example | |
3418 | ||
3419 | @ccmode{} assigns the @code{block-close} syntactic symbol to the | |
3420 | brace that closes the @code{do} construct, and normally we'd like the | |
3421 | line that follows a @code{block-close} brace to begin on a separate | |
3422 | line. However, with ``do-while'' constructs, we want the | |
3423 | @code{while} clause to follow the closing brace. To do this, we | |
3424 | associate the @code{block-close} symbol with the @var{action} function | |
3425 | @code{c-snug-do-while}: | |
3426 | ||
3427 | @example | |
3428 | (defun c-snug-do-while (syntax pos) | |
3429 | "Dynamically calculate brace hanginess for do-while statements." | |
3430 | (save-excursion | |
3431 | (let (langelem) | |
3432 | (if (and (eq syntax 'block-close) | |
3433 | (setq langelem (assq 'block-close c-syntactic-context)) | |
3434 | (progn (goto-char (cdr langelem)) | |
3435 | (if (= (following-char) ?@{) | |
3436 | (forward-sexp -1)) | |
3437 | (looking-at "\\<do\\>[^_]"))) | |
3438 | '(before) | |
3439 | '(before after))))) | |
3440 | @end example | |
3441 | ||
3442 | @findex c-snug-do-while | |
3443 | @findex snug-do-while (c-) | |
3444 | This function simply looks to see if the brace closes a ``do-while'' | |
3445 | clause and if so, returns the list @samp{(before)} indicating | |
3446 | that a newline should be inserted before the brace, but not after it. | |
3447 | In all other cases, it returns the list @samp{(before after)} so | |
3448 | that the brace appears on a line by itself. | |
3449 | ||
3450 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
3451 | @node Hanging Colons, Hanging Semicolons and Commas, Hanging Braces, Custom Auto-newlines | |
3452 | @comment node-name, next, previous, up | |
3453 | @section Hanging Colons | |
3454 | @cindex hanging colons | |
3455 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
3456 | ||
3457 | @cindex customization, colon hanging | |
3458 | @vindex c-hanging-colons-alist | |
3459 | @vindex hanging-colons-alist (c-) | |
3460 | ||
3461 | Using a mechanism similar to brace hanging (@pxref{Hanging Braces}), | |
3462 | colons can also be made to hang using the style variable | |
f99f1641 | 3463 | @code{c-hanging-colons-alist}: when a colon is typed, @ccmode |
4009494e GM |
3464 | determines its syntactic context, looks this up in the alist |
3465 | @code{c-changing-colons-alist} and inserts up to two newlines | |
3466 | accordingly. Here, however, If @ccmode fails to find an entry for a | |
3467 | syntactic symbol in the alist, no newlines are inserted around the | |
3468 | newly typed colon. | |
3469 | ||
3470 | @defopt c-hanging-colons-alist | |
3471 | @vindex hanging-colons-alist (c-) | |
3472 | ||
3473 | @table @asis | |
f99f1641 | 3474 | @item The Key: the syntactic symbol |
4009494e GM |
3475 | The syntactic symbols appropriate as keys in this association list |
3476 | are: @code{case-label}, @code{label}, @code{access-label}, | |
3477 | @code{member-init-intro}, and @code{inher-intro}. @xref{Syntactic | |
3478 | Symbols}. Elements with any other value as a key get ignored. | |
3479 | ||
f99f1641 | 3480 | @item The associated value: the ``ACTION'' list |
4009494e GM |
3481 | The @var{action} here is simply a list containing a combination of the |
3482 | symbols @code{before} and @code{after}. Unlike in | |
3483 | @code{c-hanging-braces-alist}, functions as @var{actions} are not | |
f99f1641 | 3484 | supported; there doesn't seem to be any need for them. |
4009494e GM |
3485 | @end table |
3486 | @end defopt | |
3487 | ||
3488 | In C++, double-colons are used as a scope operator but because these | |
3489 | colons always appear right next to each other, newlines before and after | |
3490 | them are controlled by a different mechanism, called @dfn{clean-ups} in | |
3491 | @ccmode{}. @xref{Clean-ups}, for details. | |
3492 | ||
3493 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
3494 | @node Hanging Semicolons and Commas, , Hanging Colons, Custom Auto-newlines | |
3495 | @comment node-name, next, previous, up | |
3496 | @section Hanging Semicolons and Commas | |
3497 | @cindex hanging semicolons | |
3498 | @cindex hanging commas | |
3499 | @cindex customization, semicolon newlines | |
3500 | @cindex customization, comma newlines | |
3501 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
3502 | ||
3503 | @defopt c-hanging-semi&comma-criteria | |
3504 | @vindex hanging-semi&comma-criteria (c-) | |
3505 | This style variable takes a list of functions; these get called when | |
3506 | you type a semicolon or comma. The functions are called in order | |
3507 | without arguments. When these functions are entered, point is just | |
3508 | after the newly inserted @samp{;} or @samp{,} and they must preserve | |
3509 | point (e.g., by using @code{save-excursion}). During the call, the | |
3510 | variable @code{c-syntactic-context} is bound to the syntactic context | |
3511 | of the current line@footnote{This was first introduced in @ccmode{} | |
3512 | 5.31.} @pxref{Custom Braces}. These functions don't insert newlines | |
3513 | themselves, rather they direct @ccmode{} whether or not to do so. | |
3514 | They should return one of the following values: | |
3515 | ||
3516 | @table @code | |
3517 | @item t | |
3518 | A newline is to be inserted after the @samp{;} or @samp{,}, and no | |
3519 | more functions from the list are to be called. | |
3520 | @item stop | |
3521 | No more functions from the list are to be called, and no newline is to | |
3522 | be inserted. | |
3523 | @item nil | |
3524 | No determination has been made, and the next function in the list is | |
3525 | to be called. | |
3526 | @end table | |
3527 | ||
3528 | Note that auto-newlines are never inserted @emph{before} a semicolon | |
3529 | or comma. If every function in the list is called without a | |
3530 | determination being made, then no newline is added. | |
3531 | ||
3532 | In AWK mode, this variable is set by default to @code{nil}. In the | |
3533 | other modes, the default value is a list containing a single function, | |
3534 | @code{c-semi&comma-inside-parenlist}. This inserts newlines after all | |
3535 | semicolons, apart from those separating @code{for}-clause statements. | |
3536 | @end defopt | |
3537 | ||
3538 | @defun c-semi&comma-no-newlines-before-nonblanks | |
3539 | @findex semi&comma-no-newlines-before-nonblanks (c-) | |
3540 | This is an example of a criteria function, provided by @ccmode{}. It | |
3541 | prevents newlines from being inserted after semicolons when there is a | |
3542 | non-blank following line. Otherwise, it makes no determination. To | |
3543 | use, add this function to the front of the | |
3544 | @code{c-hanging-semi&comma-criteria} list. | |
3545 | ||
3546 | @example | |
3547 | (defun c-semi&comma-no-newlines-before-nonblanks () | |
3548 | (save-excursion | |
3549 | (if (and (eq last-command-char ?\;) | |
3550 | (zerop (forward-line 1)) | |
3551 | (not (looking-at "^[ \t]*$"))) | |
3552 | 'stop | |
3553 | nil))) | |
3554 | @end example | |
3555 | @end defun | |
3556 | ||
3557 | @defun c-semi&comma-inside-parenlist | |
3558 | @findex semi&comma-inside-parenlist (c-) | |
3559 | @defunx c-semi&comma-no-newlines-for-oneline-inliners | |
3560 | @findex semi&comma-no-newlines-for-oneline-inliners (c-) | |
3561 | The function @code{c-semi&comma-inside-parenlist} is what prevents | |
3562 | newlines from being inserted inside the parenthesis list of @code{for} | |
3563 | statements. In addition to | |
3564 | @code{c-semi&comma-no-newlines-before-nonblanks} described above, | |
3565 | @ccmode{} also comes with the criteria function | |
3566 | @code{c-semi&comma-no-newlines-for-oneline-inliners}, which suppresses | |
3567 | newlines after semicolons inside one-line inline method definitions | |
1df7defd | 3568 | (e.g., in C++ or Java). |
4009494e GM |
3569 | @end defun |
3570 | ||
3571 | ||
3572 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
3573 | @node Clean-ups, Indentation Engine Basics, Custom Auto-newlines, Top | |
3574 | @comment node-name, next, previous, up | |
3575 | @chapter Clean-ups | |
3576 | @cindex clean-ups | |
3577 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
3578 | ||
3579 | @dfn{Clean-ups} are mechanisms which remove (or exceptionally, add) | |
3580 | whitespace in specific circumstances and are complementary to colon | |
3581 | and brace hanging. You enable a clean-up by adding its symbol into | |
1df7defd | 3582 | @code{c-cleanup-list}, e.g., like this: |
4009494e GM |
3583 | |
3584 | @example | |
3585 | (add-to-list 'c-cleanup-list 'space-before-funcall) | |
3586 | @end example | |
3587 | ||
3588 | On the surface, it would seem that clean-ups overlap the functionality | |
3589 | provided by the @code{c-hanging-*-alist} variables. Clean-ups, | |
1df7defd | 3590 | however, are used to adjust code ``after-the-fact'', i.e., to adjust |
4009494e GM |
3591 | the whitespace in constructs later than when they were typed. |
3592 | ||
3593 | Most of the clean-ups remove automatically inserted newlines, and are | |
3594 | only active when auto-newline minor mode is turned on. Others will | |
3595 | work all the time. Note that clean-ups are only performed when there | |
3596 | is nothing but whitespace appearing between the individual components | |
3597 | of the construct, and (apart from @code{comment-close-slash}) when the | |
3598 | construct does not occur within a literal (@pxref{Auto-newlines}). | |
3599 | ||
3600 | @defopt c-cleanup-list | |
3601 | @vindex cleanup-list (c-) | |
3602 | @cindex literal | |
3603 | ||
3604 | You configure @ccmode{}'s clean-ups by setting the style variable | |
3605 | @code{c-cleanup-list}, which is a list of clean-up symbols. By | |
3606 | default, @ccmode{} cleans up only the @code{scope-operator} construct, | |
3607 | which is necessary for proper C++ support. | |
3608 | @end defopt | |
3609 | ||
3610 | These are the clean-ups that are only active when electric and | |
3611 | auto-newline minor modes are enabled: | |
3612 | ||
3613 | @c TBD: Would like to use some sort of @deffoo here; @table indents a | |
3614 | @c bit too much in dvi output. | |
3615 | @table @code | |
3616 | @item brace-else-brace | |
3617 | Clean up @samp{@} else @{} constructs by placing the entire construct on | |
3618 | a single line. Clean up occurs when the open brace after the | |
3619 | @samp{else} is typed. So for example, this: | |
3620 | ||
3621 | @example | |
3622 | @group | |
3623 | void spam(int i) | |
3624 | @{ | |
3625 | if( i==7 ) @{ | |
3626 | dosomething(); | |
3627 | @} | |
3628 | else | |
3629 | @{ | |
3630 | @end group | |
3631 | @end example | |
3632 | ||
3633 | @noindent | |
3634 | appears like this after the last open brace is typed: | |
3635 | ||
3636 | @example | |
3637 | @group | |
3638 | void spam(int i) | |
3639 | @{ | |
3640 | if( i==7 ) @{ | |
3641 | dosomething(); | |
3642 | @} else @{ | |
3643 | @end group | |
3644 | @end example | |
3645 | ||
3646 | @item brace-elseif-brace | |
3647 | Similar to the @code{brace-else-brace} clean-up, but this cleans up | |
3648 | @samp{@} else if (...) @{} constructs. For example: | |
3649 | ||
3650 | @example | |
3651 | @group | |
3652 | void spam(int i) | |
3653 | @{ | |
3654 | if( i==7 ) @{ | |
3655 | dosomething(); | |
3656 | @} | |
3657 | else if( i==3 ) | |
3658 | @{ | |
3659 | @end group | |
3660 | @end example | |
3661 | ||
3662 | @noindent | |
3663 | appears like this after the last open parenthesis is typed: | |
3664 | ||
3665 | @example | |
3666 | @group | |
3667 | void spam(int i) | |
3668 | @{ | |
3669 | if( i==7 ) @{ | |
3670 | dosomething(); | |
3671 | @} else if( | |
3672 | @end group | |
3673 | @end example | |
3674 | ||
3675 | @noindent | |
3676 | and like this after the last open brace is typed: | |
3677 | ||
3678 | @example | |
3679 | @group | |
3680 | void spam(int i) | |
3681 | @{ | |
3682 | if( i==7 ) @{ | |
3683 | dosomething(); | |
3684 | @} else if( i==3 ) @{ | |
3685 | @end group | |
3686 | @end example | |
3687 | ||
3688 | @item brace-catch-brace | |
3689 | Analogous to @code{brace-elseif-brace}, but cleans up @samp{@} catch | |
3690 | (...) @{} in C++ and Java mode. | |
3691 | ||
3692 | @item empty-defun-braces | |
3693 | Clean up braces following a top-level function or class definition that | |
3694 | contains no body. Clean up occurs when the closing brace is typed. | |
3695 | Thus the following: | |
3696 | ||
3697 | @example | |
3698 | @group | |
3699 | class Spam | |
3700 | @{ | |
3701 | @} | |
3702 | @end group | |
3703 | @end example | |
3704 | ||
3705 | @noindent | |
3706 | is transformed into this when the close brace is typed: | |
3707 | ||
3708 | @example | |
3709 | @group | |
3710 | class Spam | |
3711 | @{@} | |
3712 | @end group | |
3713 | @end example | |
3714 | ||
3715 | @item defun-close-semi | |
3716 | Clean up the terminating semicolon on top-level function or class | |
3717 | definitions when they follow a close brace. Clean up occurs when the | |
3718 | semicolon is typed. So for example, the following: | |
3719 | ||
3720 | @example | |
3721 | @group | |
3722 | class Spam | |
3723 | @{ | |
3724 | ... | |
3725 | @} | |
3726 | ; | |
3727 | @end group | |
3728 | @end example | |
3729 | ||
3730 | @noindent | |
3731 | is transformed into this when the semicolon is typed: | |
3732 | ||
3733 | @example | |
3734 | @group | |
3735 | class Spam | |
3736 | @{ | |
3737 | ... | |
3738 | @}; | |
3739 | @end group | |
3740 | @end example | |
3741 | ||
3742 | @item list-close-comma | |
3743 | Clean up commas following braces in array and aggregate initializers. | |
3744 | Clean up occurs when the comma is typed. The space before the comma | |
3745 | is zapped just like the space before the semicolon in | |
3746 | @code{defun-close-semi}. | |
3747 | ||
3748 | @item scope-operator | |
3749 | Clean up double colons which might designate a C++ scope operator split | |
3750 | across multiple lines@footnote{Certain C++ constructs introduce | |
3751 | ambiguous situations, so @code{scope-operator} clean-ups might not | |
3752 | always be correct. This usually only occurs when scoped identifiers | |
3753 | appear in switch label tags.}. Clean up occurs when the second colon is | |
3754 | typed. You will always want @code{scope-operator} in the | |
3755 | @code{c-cleanup-list} when you are editing C++ code. | |
3756 | ||
3757 | @item one-liner-defun | |
3758 | Clean up a single line of code enclosed by defun braces by removing | |
3759 | the whitespace before and after the code. The clean-up happens when | |
3760 | the closing brace is typed. If the variable | |
3761 | @code{c-max-one-liner-length} is set, the cleanup is only done if the | |
3762 | resulting line would be no longer than the value of that variable. | |
3763 | ||
3764 | For example, consider this AWK code: | |
3765 | ||
3766 | @example | |
3767 | @group | |
3768 | BEGIN @{ | |
3769 | FS = "\t" # use <TAB> as a field separator | |
3770 | @} | |
3771 | @end group | |
3772 | @end example | |
3773 | ||
3774 | @noindent | |
3775 | It gets compacted to the following when the closing brace is typed: | |
3776 | ||
3777 | @example | |
3778 | @group | |
3779 | BEGIN @{FS = "\t"@} # use <TAB> as a field separator | |
3780 | @end group | |
3781 | @end example | |
3782 | ||
3783 | @defopt c-max-one-liner-length | |
3784 | @vindex max-one-liner-length (c-) | |
3785 | The maximum length of the resulting line for which the clean-up | |
3786 | @code{one-liner-defun} will be triggered. This length is that of the entire | |
3787 | line, including any leading whitespace and any trailing comment. Its | |
3788 | default value is 80. If the value is zero or @code{nil}, no limit | |
3789 | applies. | |
3790 | @end defopt | |
3791 | @end table | |
3792 | ||
3793 | The following clean-ups are always active when they occur on | |
3794 | @code{c-cleanup-list}, regardless of whether Electric minor mode or | |
3795 | Auto-newline minor mode are enabled: | |
3796 | ||
3797 | @table @code | |
3798 | @item space-before-funcall | |
3799 | Insert a space between the function name and the opening parenthesis | |
3800 | of a function call. This produces function calls in the style | |
1df7defd | 3801 | mandated by the GNU coding standards, e.g., @samp{signal@w{ }(SIGINT, |
4009494e GM |
3802 | SIG_IGN)} and @samp{abort@w{ }()}. Clean up occurs when the opening |
3803 | parenthesis is typed. This clean-up should never be active in AWK | |
3804 | Mode, since such a space is syntactically invalid for user defined | |
3805 | functions. | |
3806 | ||
3807 | @item compact-empty-funcall | |
3808 | Clean up any space between the function name and the opening parenthesis | |
3809 | of a function call that has no arguments. This is typically used | |
3810 | together with @code{space-before-funcall} if you prefer the GNU function | |
3811 | call style for functions with arguments but think it looks ugly when | |
1df7defd | 3812 | it's only an empty parenthesis pair. I.e., you will get @samp{signal |
4009494e GM |
3813 | (SIGINT, SIG_IGN)}, but @samp{abort()}. Clean up occurs when the |
3814 | closing parenthesis is typed. | |
3815 | ||
3816 | @item comment-close-slash | |
3817 | When inside a block comment, terminate the comment when you type a slash | |
1df7defd | 3818 | at the beginning of a line (i.e., immediately after the comment prefix). |
4009494e GM |
3819 | This clean-up removes whitespace preceding the slash and if needed, |
3820 | inserts a star to complete the token @samp{*/}. Type @kbd{C-q /} in this | |
3821 | situation if you just want a literal @samp{/} inserted. | |
3822 | @end table | |
3823 | ||
3824 | ||
3825 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
3826 | @node Indentation Engine Basics, Customizing Indentation, Clean-ups, Top | |
3827 | @comment node-name, next, previous, up | |
3828 | @chapter Indentation Engine Basics | |
3829 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
3830 | ||
3831 | This chapter will briefly cover how @ccmode{} indents lines of code. | |
3832 | It is helpful to understand the indentation model being used so that | |
3833 | you will know how to customize @ccmode{} for your personal coding | |
3834 | style. All the details are in @ref{Customizing Indentation}. | |
3835 | ||
3836 | @ccmode{} has an indentation engine that provides a flexible and | |
3837 | general mechanism for customizing indentation. When @ccmode{} indents | |
3838 | a line of code, it separates its calculations into two steps: | |
3839 | ||
3840 | @enumerate | |
3841 | @item | |
3842 | @cindex syntactic symbol | |
3843 | @cindex anchor position | |
3844 | It analyzes the line to determine its @dfn{syntactic symbol(s)} (the | |
3845 | kind of language construct it's looking at) and its @dfn{anchor | |
3846 | position} (the position earlier in the file that @ccmode{} will indent | |
3847 | the line relative to). The anchor position might be the location of | |
3848 | an opening brace in the previous line, for example. @xref{Syntactic | |
3849 | Analysis}. | |
3850 | @item | |
3851 | @cindex offsets | |
3852 | @cindex indentation offset specifications | |
3853 | It looks up the syntactic symbol(s) in the configuration to get the | |
3854 | corresponding @dfn{offset(s)}. The symbol @code{+}, which means | |
3855 | ``indent this line one more level'' is a typical offset. @ccmode{} | |
3856 | then applies these offset(s) to the anchor position, giving the | |
3857 | indentation for the line. The different sorts of offsets are | |
3858 | described in @ref{c-offsets-alist}. | |
3859 | @end enumerate | |
3860 | ||
3861 | In exceptional circumstances, the syntax directed indentation | |
3862 | described here may be a nuisance rather than a help. You can disable | |
3863 | it by setting @code{c-syntactic-indentation} to @code{nil}. (To set | |
3864 | the variable interactively, @ref{Minor Modes}). | |
3865 | ||
3866 | @defopt c-syntactic-indentation | |
3867 | @vindex syntactic-indentation (c-) | |
3868 | When this is non-@code{nil} (which it is by default), the indentation | |
3869 | of code is done according to its syntactic structure. When it's | |
3870 | @code{nil}, every line is just indented to the same level as the | |
3871 | previous one, and @kbd{TAB} (@code{c-indent-command}) adjusts the | |
3872 | indentation in steps of @code{c-basic-offset}. The current style | |
3873 | (@pxref{Config Basics}) then has no effect on indentation, nor do any | |
3874 | of the variables associated with indentation, not even | |
3875 | @code{c-special-indent-hook}. | |
3876 | @end defopt | |
3877 | ||
3878 | @menu | |
3879 | * Syntactic Analysis:: | |
3880 | * Syntactic Symbols:: | |
3881 | * Indentation Calculation:: | |
3882 | @end menu | |
3883 | ||
3884 | ||
3885 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
3886 | @node Syntactic Analysis, Syntactic Symbols, Indentation Engine Basics, Indentation Engine Basics | |
3887 | @comment node-name, next, previous, up | |
3888 | @section Syntactic Analysis | |
3889 | @cindex syntactic analysis | |
3890 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
3891 | ||
3892 | @cindex syntactic element | |
3893 | @cindex syntactic context | |
3894 | The first thing @ccmode{} does when indenting a line of code, is to | |
3895 | analyze the line, determining the @dfn{syntactic context} of the | |
3896 | (first) construct on that line. It's a list of @dfn{syntactic | |
3897 | elements}, where each syntactic element in turn is a list@footnote{In | |
3898 | @ccmode 5.28 and earlier, a syntactic element was a dotted pair; the | |
3899 | cons was the syntactic symbol and the cdr was the anchor position. | |
3900 | For compatibility's sake, the parameter passed to a line-up function | |
3901 | still has this dotted pair form (@pxref{Custom Line-Up}).} Here is a | |
3902 | brief and typical example: | |
3903 | ||
3904 | @example | |
3905 | ((defun-block-intro 1959)) | |
3906 | @end example | |
3907 | ||
3908 | @cindex syntactic symbol | |
3909 | @noindent | |
3910 | The first thing inside each syntactic element is always a | |
3911 | @dfn{syntactic symbol}. It describes the kind of construct that was | |
1df7defd | 3912 | recognized, e.g., @code{statement}, @code{substatement}, |
4009494e GM |
3913 | @code{class-open}, @code{class-close}, etc. @xref{Syntactic Symbols}, |
3914 | for a complete list of currently recognized syntactic symbols and | |
3915 | their semantics. The remaining entries are various data associated | |
f99f1641 | 3916 | with the recognized construct; there might be zero or more. |
4009494e GM |
3917 | |
3918 | @cindex anchor position | |
3919 | Conceptually, a line of code is always indented relative to some | |
3920 | position higher up in the buffer (typically the indentation of the | |
3921 | previous line). That position is the @dfn{anchor position} in the | |
3922 | syntactic element. If there is an entry after the syntactic symbol in | |
3923 | the syntactic element list then it's either nil or that anchor position. | |
3924 | ||
3925 | Here is an example. Suppose we had the following code as the only thing | |
3926 | in a C++ buffer @footnote{The line numbers in this and future examples | |
3927 | don't actually appear in the buffer, of course!}: | |
3928 | ||
3929 | @example | |
3930 | 1: void swap( int& a, int& b ) | |
3931 | 2: @{ | |
3932 | 3: int tmp = a; | |
3933 | 4: a = b; | |
3934 | 5: b = tmp; | |
3935 | 6: @} | |
3936 | @end example | |
3937 | ||
3938 | @noindent | |
3939 | We can use @kbd{C-c C-s} (@code{c-show-syntactic-information}) to | |
3940 | report what the syntactic analysis is for the current line: | |
3941 | ||
3942 | @table @asis | |
3943 | @item @kbd{C-c C-s} (@code{c-show-syntactic-information}) | |
3944 | @kindex C-c C-s | |
3945 | @findex c-show-syntactic-information | |
3946 | @findex show-syntactic-information (c-) | |
3947 | This command calculates the syntactic analysis of the current line and | |
3948 | displays it in the minibuffer. The command also highlights the anchor | |
3949 | position(s). | |
3950 | @end table | |
3951 | ||
3952 | Running this command on line 4 of this example, we'd see in the echo | |
1df7defd | 3953 | area@footnote{With a universal argument (i.e., @kbd{C-u C-c C-s}) the |
4009494e GM |
3954 | analysis is inserted into the buffer as a comment on the current |
3955 | line.}: | |
3956 | ||
3957 | @example | |
3958 | ((statement 35)) | |
3959 | @end example | |
3960 | ||
3961 | @noindent | |
3962 | and the @samp{i} of @code{int} on line 3 would be highlighted. This | |
3963 | tells us that the line is a statement and it is indented relative to | |
3964 | buffer position 35, the highlighted position. If you were to move | |
3965 | point to line 3 and hit @kbd{C-c C-s}, you would see: | |
3966 | ||
3967 | @example | |
3968 | ((defun-block-intro 29)) | |
3969 | @end example | |
3970 | ||
3971 | @noindent | |
3972 | This indicates that the @samp{int} line is the first statement in a top | |
3973 | level function block, and is indented relative to buffer position 29, | |
3974 | which is the brace just after the function header. | |
3975 | ||
3976 | Here's another example: | |
3977 | ||
3978 | @example | |
3979 | 1: int add( int val, int incr, int doit ) | |
3980 | 2: @{ | |
3981 | 3: if( doit ) | |
3982 | 4: @{ | |
3983 | 5: return( val + incr ); | |
3984 | 6: @} | |
3985 | 7: return( val ); | |
3986 | 8: @} | |
3987 | @end example | |
3988 | ||
3989 | @noindent | |
3990 | Hitting @kbd{C-c C-s} on line 4 gives us: | |
3991 | ||
3992 | @example | |
3993 | ((substatement-open 46)) | |
3994 | @end example | |
3995 | ||
3996 | @cindex substatement | |
3997 | @cindex substatement block | |
3998 | @noindent | |
3999 | which tells us that this is a brace that @emph{opens} a substatement | |
4000 | block. @footnote{A @dfn{substatement} is the line after a | |
4001 | conditional statement, such as @code{if}, @code{else}, @code{while}, | |
4002 | @code{do}, @code{switch}, etc. A @dfn{substatement | |
4003 | block} is a brace block following one of these conditional statements.} | |
4004 | ||
4005 | @cindex comment-only line | |
4006 | Syntactic contexts can contain more than one element, and syntactic | |
4007 | elements need not have anchor positions. The most common example of | |
4008 | this is a @dfn{comment-only line}: | |
4009 | ||
4010 | @example | |
4011 | 1: void draw_list( List<Drawables>& drawables ) | |
4012 | 2: @{ | |
4013 | 3: // call the virtual draw() method on each element in list | |
4014 | 4: for( int i=0; i < drawables.count(), ++i ) | |
4015 | 5: @{ | |
4016 | 6: drawables[i].draw(); | |
4017 | 7: @} | |
4018 | 8: @} | |
4019 | @end example | |
4020 | ||
4021 | @noindent | |
4022 | Hitting @kbd{C-c C-s} on line 3 of this example gives: | |
4023 | ||
4024 | @example | |
4025 | ((comment-intro) (defun-block-intro 46)) | |
4026 | @end example | |
4027 | ||
4028 | @noindent | |
4029 | and you can see that the syntactic context contains two syntactic | |
4030 | elements. Notice that the first element, @samp{(comment-intro)}, has no | |
4031 | anchor position. | |
4032 | ||
4033 | ||
4034 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
4035 | @node Syntactic Symbols, Indentation Calculation, Syntactic Analysis, Indentation Engine Basics | |
4036 | @comment node-name, next, previous, up | |
4037 | @section Syntactic Symbols | |
4038 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
4039 | ||
4040 | @cindex syntactic symbols, brief list | |
4041 | @vindex c-offsets-alist | |
4042 | @vindex offsets-alist (c-) | |
4043 | This section is a complete list of the syntactic symbols which appear | |
4044 | in the @code{c-offsets-alist} style variable, along with brief | |
4045 | descriptions. The previous section (@pxref{Syntactic Analysis}) | |
4046 | states what syntactic symbols are and how the indentation engine uses | |
4047 | them. | |
4048 | ||
4049 | More detailed descriptions of these symbols, together with snippets of | |
4050 | source code to which they apply, appear in the examples in the | |
4051 | subsections below. Note that, in the interests of brevity, the anchor | |
4052 | position associated with most syntactic symbols is @emph{not} | |
4053 | specified. In cases of doubt, type @kbd{C-c C-s} on a pertinent | |
4054 | line---this highlights the anchor position. | |
4055 | ||
4056 | @ssindex -open symbols | |
4057 | @ssindex -close symbols | |
4058 | @ssindex -block-intro symbols | |
4059 | The syntactic symbols which indicate brace constructs follow a general | |
4060 | naming convention. When a line begins with an open or close brace, | |
4061 | its syntactic symbol will contain the suffix @code{-open} or | |
4062 | @code{-close} respectively. The first line within the brace block | |
4063 | construct will contain the suffix @code{-block-intro}. | |
4064 | ||
4065 | @ssindex -intro symbols | |
4066 | @ssindex -cont symbols | |
4067 | In constructs which can span several lines, a distinction is usually | |
4068 | made between the first line that introduces the construct and the | |
4069 | lines that continue it. The syntactic symbols that indicate these | |
4070 | lines will contain the suffixes @code{-intro} or @code{-cont} | |
4071 | respectively. | |
4072 | ||
4073 | The best way to understand how all this works is by looking at some | |
4074 | examples. Remember that you can see the syntax of any source code | |
4075 | line by using @kbd{C-c C-s}. | |
4076 | ||
4077 | @table @code | |
4078 | @item string | |
4079 | Inside a multiline string. @ref{Literal Symbols}. | |
4080 | @item c | |
4081 | Inside a multiline C style block comment. @ref{Literal Symbols}. | |
4082 | @item defun-open | |
4083 | Brace that opens a top-level function definition. @ref{Function | |
4084 | Symbols}. | |
4085 | @item defun-close | |
4086 | Brace that closes a top-level function definition. @ref{Function | |
4087 | Symbols}. | |
4088 | @item defun-block-intro | |
4089 | The first line in a top-level defun. @ref{Function Symbols}. | |
4090 | @item class-open | |
4091 | Brace that opens a class definition. @ref{Class Symbols}. | |
4092 | @item class-close | |
4093 | Brace that closes a class definition. @ref{Class Symbols}. | |
4094 | @item inline-open | |
4095 | Brace that opens an in-class inline method. @ref{Class Symbols}. | |
4096 | @item inline-close | |
4097 | Brace that closes an in-class inline method. @ref{Class Symbols}. | |
4098 | @item func-decl-cont | |
4099 | The region between a function definition's argument list and the | |
4100 | function opening brace (excluding K&R argument declarations). In C, | |
4101 | you cannot put anything but whitespace and comments in this region, | |
4102 | however in C++ and Java, @code{throws} declarations and other things | |
4103 | can appear here. @ref{Literal Symbols}. @c @emph{FIXME!!! Can it not | |
4104 | @c go somewhere better?} | |
4105 | @item knr-argdecl-intro | |
4106 | First line of a K&R C argument declaration. @ref{K&R Symbols}. | |
4107 | @item knr-argdecl | |
4108 | Subsequent lines in a K&R C argument declaration. @ref{K&R Symbols}. | |
4109 | @item topmost-intro | |
4110 | The first line in a ``topmost'' definition. @ref{Function Symbols}. | |
4111 | @item topmost-intro-cont | |
4112 | Topmost definition continuation lines. This is only used in the parts | |
4113 | that aren't covered by other symbols such as @code{func-decl-cont} and | |
4114 | @code{knr-argdecl}. @ref{Function Symbols}. | |
5cee0a9c AM |
4115 | @item annotation-top-cont |
4116 | Topmost definition continuation lines where all previous items are | |
4117 | annotations. @ref{Java Symbols}. | |
4009494e GM |
4118 | @item member-init-intro |
4119 | First line in a member initialization list. @ref{Class Symbols}. | |
4120 | @item member-init-cont | |
4121 | Subsequent member initialization list lines. @ref{Class Symbols}. | |
4122 | @item inher-intro | |
4123 | First line of a multiple inheritance list. @ref{Class Symbols}. | |
4124 | @item inher-cont | |
4125 | Subsequent multiple inheritance lines. @ref{Class Symbols}. | |
4126 | @item block-open | |
4127 | Statement block open brace. @ref{Literal Symbols}. | |
4128 | @item block-close | |
4129 | Statement block close brace. @ref{Conditional Construct Symbols}. | |
4130 | @item brace-list-open | |
4131 | Open brace of an enum or static array list. @ref{Brace List Symbols}. | |
4132 | @item brace-list-close | |
4133 | Close brace of an enum or static array list. @ref{Brace List Symbols}. | |
4134 | @item brace-list-intro | |
4135 | First line in an enum or static array list. @ref{Brace List Symbols}. | |
4136 | @item brace-list-entry | |
4137 | Subsequent lines in an enum or static array list. @ref{Brace List | |
4138 | Symbols}. | |
4139 | @item brace-entry-open | |
4140 | Subsequent lines in an enum or static array list where the line begins | |
4141 | with an open brace. @ref{Brace List Symbols}. | |
4142 | @item statement | |
4143 | A statement. @ref{Function Symbols}. | |
4144 | @item statement-cont | |
4145 | A continuation of a statement. @ref{Function Symbols}. | |
5cee0a9c AM |
4146 | @item annotation-var-cont |
4147 | A continuation of a statement where all previous items are | |
4148 | annotations. @ref{Java Symbols}. | |
4009494e GM |
4149 | @item statement-block-intro |
4150 | The first line in a new statement block. @ref{Conditional Construct | |
4151 | Symbols}. | |
4152 | @item statement-case-intro | |
4153 | The first line in a case block. @ref{Switch Statement Symbols}. | |
4154 | @item statement-case-open | |
4155 | The first line in a case block that starts with a brace. @ref{Switch | |
4156 | Statement Symbols}. | |
4157 | @item substatement | |
4158 | The first line after a conditional or loop construct. | |
4159 | @ref{Conditional Construct Symbols}. | |
4160 | @item substatement-open | |
4161 | The brace that opens a substatement block. @ref{Conditional Construct | |
4162 | Symbols}. | |
4163 | @item substatement-label | |
4164 | The first line after a conditional or loop construct if it's a label. | |
4165 | @ref{Conditional Construct Symbols}. | |
4166 | @item case-label | |
4167 | A label in a @code{switch} block. @ref{Switch Statement Symbols}. | |
4168 | @item access-label | |
4169 | C++ access control label. @ref{Class Symbols}. | |
4170 | @item label | |
4171 | Any other label. @ref{Literal Symbols}. | |
4172 | @item do-while-closure | |
4173 | The @code{while} line that ends a @code{do}-@code{while} construct. | |
4174 | @ref{Conditional Construct Symbols}. | |
4175 | @item else-clause | |
4176 | The @code{else} line of an @code{if}-@code{else} construct. | |
4177 | @ref{Conditional Construct Symbols}. | |
4178 | @item catch-clause | |
4179 | The @code{catch} or @code{finally} (in Java) line of a | |
4180 | @code{try}-@code{catch} construct. @ref{Conditional Construct | |
4181 | Symbols}. | |
4182 | @item comment-intro | |
4183 | A line containing only a comment introduction. @ref{Literal Symbols}. | |
4184 | @item arglist-intro | |
4185 | The first line in an argument list. @ref{Paren List Symbols}. | |
4186 | @item arglist-cont | |
4187 | Subsequent argument list lines when no arguments follow on the same | |
4188 | line as the arglist opening paren. @ref{Paren List Symbols}. | |
4189 | @item arglist-cont-nonempty | |
4190 | Subsequent argument list lines when at least one argument follows on | |
4191 | the same line as the arglist opening paren. @ref{Paren List Symbols}. | |
4192 | @item arglist-close | |
4193 | The solo close paren of an argument list. @ref{Paren List Symbols}. | |
4194 | @item stream-op | |
4195 | Lines continuing a stream operator (C++ only). @ref{Literal | |
4196 | Symbols}. @c @emph{FIXME!!! Can this not be moved somewhere better?} | |
4197 | @item inclass | |
4198 | The line is nested inside a class definition. @ref{Class Symbols}. | |
4199 | @item cpp-macro | |
4200 | The start of a preprocessor macro definition. @ref{Literal Symbols}. | |
4201 | @item cpp-define-intro | |
4202 | The first line inside a multiline preprocessor macro if | |
4203 | @code{c-syntactic-indentation-in-macros} is set. @ref{Multiline Macro | |
4204 | Symbols}. | |
4205 | @item cpp-macro-cont | |
4206 | All lines inside multiline preprocessor macros if | |
4207 | @code{c-syntactic-indentation-in-macros} is @code{nil}. | |
4208 | @ref{Multiline Macro Symbols}. | |
4209 | @item friend | |
4210 | A C++ friend declaration. @ref{Class Symbols}. | |
4211 | @item objc-method-intro | |
4212 | The first line of an Objective-C method definition. @ref{Objective-C | |
4213 | Method Symbols}. | |
4214 | @item objc-method-args-cont | |
4215 | Lines continuing an Objective-C method definition. @ref{Objective-C | |
4216 | Method Symbols}. | |
4217 | @item objc-method-call-cont | |
4218 | Lines continuing an Objective-C method call. @ref{Objective-C Method | |
4219 | Symbols}. | |
4220 | @item extern-lang-open | |
1df7defd | 4221 | Brace that opens an @code{extern} block (e.g., @code{extern "C" |
4009494e GM |
4222 | @{...@}}). @ref{External Scope Symbols}. |
4223 | @item extern-lang-close | |
4224 | Brace that closes an @code{extern} block. @ref{External Scope | |
4225 | Symbols}. | |
4226 | @item inextern-lang | |
4227 | Analogous to @code{inclass} syntactic symbol, but used inside | |
4228 | @code{extern} blocks. @ref{External Scope Symbols}. | |
4229 | @item namespace-open | |
4230 | @itemx namespace-close | |
4231 | @itemx innamespace | |
4232 | These are analogous to the three @code{extern-lang} symbols above, but | |
4233 | are returned for C++ namespace blocks. @ref{External Scope Symbols}. | |
4234 | @item module-open | |
4235 | @itemx module-close | |
4236 | @itemx inmodule | |
4237 | Analogous to the above, but for CORBA IDL @code{module} blocks. | |
4238 | @ref{External Scope Symbols}. | |
4239 | @item composition-open | |
4240 | @itemx composition-close | |
4241 | @itemx incomposition | |
4242 | Analogous to the above, but for CORBA CIDL @code{composition} blocks. | |
4243 | @ref{External Scope Symbols}. | |
4244 | @item template-args-cont | |
4245 | C++ template argument list continuations. @ref{Class Symbols}. | |
4246 | @item inlambda | |
4247 | Analogous to @code{inclass} syntactic symbol, but used inside lambda | |
1df7defd | 4248 | (i.e., anonymous) functions. Only used in Pike mode. @ref{Statement |
4009494e GM |
4249 | Block Symbols}. |
4250 | @item lambda-intro-cont | |
1df7defd | 4251 | Lines continuing the header of a lambda function, i.e., between the |
4009494e GM |
4252 | @code{lambda} keyword and the function body. Only used in Pike mode. |
4253 | @ref{Statement Block Symbols}. | |
4254 | @item inexpr-statement | |
4255 | A statement block inside an expression. The gcc C and C++ extension | |
4256 | for this is recognized. It's also used for the special functions that | |
4257 | take a statement block as an argument in Pike. @ref{Statement Block | |
4258 | Symbols}. | |
4259 | @item inexpr-class | |
4260 | A class definition inside an expression. This is used for anonymous | |
4261 | classes in Java. It's also used for anonymous array initializers in | |
5cee0a9c | 4262 | Java. @ref{Java Symbols}. |
4009494e GM |
4263 | @end table |
4264 | ||
4265 | @menu | |
91af3942 PE |
4266 | * Function Symbols:: |
4267 | * Class Symbols:: | |
4268 | * Conditional Construct Symbols:: | |
4269 | * Switch Statement Symbols:: | |
4270 | * Brace List Symbols:: | |
4271 | * External Scope Symbols:: | |
4272 | * Paren List Symbols:: | |
4273 | * Literal Symbols:: | |
4274 | * Multiline Macro Symbols:: | |
4275 | * Objective-C Method Symbols:: | |
5cee0a9c | 4276 | * Java Symbols:: |
91af3942 PE |
4277 | * Statement Block Symbols:: |
4278 | * K&R Symbols:: | |
4009494e GM |
4279 | @end menu |
4280 | ||
4281 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
4282 | @node Function Symbols, Class Symbols, Syntactic Symbols, Syntactic Symbols | |
4283 | @comment node-name, next, previous, up | |
4284 | @subsection Function Symbols | |
4285 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
4286 | ||
4287 | This example shows a typical function declaration. | |
4288 | ||
4289 | @example | |
4290 | 1: void | |
4291 | 2: swap( int& a, int& b ) | |
4292 | 3: @{ | |
4293 | 4: int tmp = a; | |
4294 | 5: a = b; | |
4295 | 6: b = tmp; | |
4296 | 7: int ignored = | |
4297 | 8: a + b; | |
4298 | 9: @} | |
4299 | @end example | |
4300 | ||
4301 | @ssindex topmost-intro | |
4302 | @ssindex topmost-intro-cont | |
4303 | @ssindex defun-open | |
4304 | @ssindex defun-close | |
4305 | @ssindex defun-block-intro | |
4306 | Line 1 shows a @code{topmost-intro} since it is the first line that | |
4307 | introduces a top-level construct. Line 2 is a continuation of the | |
4308 | top-level construct introduction so it has the syntax | |
4309 | @code{topmost-intro-cont}. Line 3 shows a @code{defun-open} since it is | |
4310 | the brace that opens a top-level function definition. Line 9 is the | |
4311 | corresponding | |
4312 | @code{defun-close} since it contains the brace that closes the top-level | |
1df7defd | 4313 | function definition. Line 4 is a @code{defun-block-intro}, i.e., it is |
4009494e GM |
4314 | the first line of a brace-block, enclosed in a |
4315 | top-level function definition. | |
4316 | ||
4317 | @ssindex statement | |
4318 | @ssindex statement-cont | |
4319 | Lines 5, 6, and 7 are all given @code{statement} syntax since there | |
4320 | isn't much special about them. Note however that line 8 is given | |
4321 | @code{statement-cont} syntax since it continues the statement begun | |
4322 | on the previous line. | |
4323 | ||
4324 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
4325 | @node Class Symbols, Conditional Construct Symbols, Function Symbols, Syntactic Symbols | |
4326 | @comment node-name, next, previous, up | |
4327 | @subsection Class related Symbols | |
4328 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
4329 | ||
4330 | Here's an example which illustrates some C++ class syntactic symbols: | |
4331 | ||
4332 | @example | |
4333 | 1: class Bass | |
4334 | 2: : public Guitar, | |
4335 | 3: public Amplifiable | |
4336 | 4: @{ | |
4337 | 5: public: | |
4338 | 6: Bass() | |
4339 | 7: : eString( new BassString( 0.105 )), | |
4340 | 8: aString( new BassString( 0.085 )), | |
4341 | 9: dString( new BassString( 0.065 )), | |
4342 | 10: gString( new BassString( 0.045 )) | |
4343 | 11: @{ | |
4344 | 12: eString.tune( 'E' ); | |
4345 | 13: aString.tune( 'A' ); | |
4346 | 14: dString.tune( 'D' ); | |
4347 | 15: gString.tune( 'G' ); | |
4348 | 16: @} | |
4349 | 17: friend class Luthier; | |
4350 | 18: @}; | |
4351 | @end example | |
4352 | ||
4353 | @ssindex class-open | |
4354 | @ssindex class-close | |
4355 | As in the previous example, line 1 has the @code{topmost-intro} syntax. | |
4356 | Here however, the brace that opens a C++ class definition on line 4 is | |
4357 | assigned the @code{class-open} syntax. Note that in C++, classes, | |
4358 | structs, and unions are essentially equivalent syntactically (and are | |
4359 | very similar semantically), so replacing the @code{class} keyword in the | |
4360 | example above with @code{struct} or @code{union} would still result in a | |
4361 | syntax of @code{class-open} for line 4 @footnote{This is the case even | |
1df7defd | 4362 | for C and Objective-C@. For consistency, structs in all supported |
4009494e GM |
4363 | languages are syntactically equivalent to classes. Note however that |
4364 | the keyword @code{class} is meaningless in C and Objective-C.}. | |
4365 | Similarly, line 18 is assigned @code{class-close} syntax. | |
4366 | ||
4367 | @ssindex inher-intro | |
4368 | @ssindex inher-cont | |
4369 | Line 2 introduces the inheritance list for the class so it is assigned | |
4370 | the @code{inher-intro} syntax, and line 3, which continues the | |
4371 | inheritance list is given @code{inher-cont} syntax. | |
4372 | ||
4373 | @ssindex access-label | |
4374 | @ssindex inclass | |
4375 | Hitting @kbd{C-c C-s} on line 5 shows the following analysis: | |
4376 | ||
4377 | @example | |
4378 | ((inclass 58) (access-label 58)) | |
4379 | @end example | |
4380 | ||
4381 | @noindent | |
4382 | The primary syntactic symbol for this line is @code{access-label} as | |
5cee0a9c | 4383 | this is a label keyword that specifies access protection in C++. However, |
4009494e GM |
4384 | because this line is also a top-level construct inside a class |
4385 | definition, the analysis actually shows two syntactic symbols. The | |
4386 | other syntactic symbol assigned to this line is @code{inclass}. | |
4387 | Similarly, line 6 is given both @code{inclass} and @code{topmost-intro} | |
4388 | syntax: | |
4389 | ||
4390 | @example | |
4391 | ((inclass 58) (topmost-intro 60)) | |
4392 | @end example | |
4393 | ||
4394 | @ssindex member-init-intro | |
4395 | @ssindex member-init-cont | |
4396 | Line 7 introduces a C++ member initialization list and as such is given | |
4397 | @code{member-init-intro} syntax. Note that in this case it is | |
4398 | @emph{not} assigned @code{inclass} since this is not considered a | |
4399 | top-level construct. Lines 8 through 10 are all assigned | |
4400 | @code{member-init-cont} since they continue the member initialization | |
4401 | list started on line 7. | |
4402 | ||
4403 | @cindex in-class inline methods | |
4404 | @ssindex inline-open | |
4405 | @ssindex inline-close | |
4406 | Line 11's analysis is a bit more complicated: | |
4407 | ||
4408 | @example | |
4409 | ((inclass 58) (inline-open)) | |
4410 | @end example | |
4411 | ||
4412 | This line is assigned a syntax of both @code{inline-open} and | |
4413 | @code{inclass} because it opens an @dfn{in-class} C++ inline method | |
4414 | definition. This is distinct from, but related to, the C++ notion of an | |
4415 | inline function in that its definition occurs inside an enclosing class | |
4416 | definition, which in C++ implies that the function should be inlined. | |
4417 | However, if the definition of the @code{Bass} constructor appeared | |
4418 | outside the class definition, the construct would be given the | |
4419 | @code{defun-open} syntax, even if the keyword @code{inline} appeared | |
4420 | before the method name, as in: | |
4421 | ||
4422 | @example | |
4423 | 1: class Bass | |
4424 | 2: : public Guitar, | |
4425 | 3: public Amplifiable | |
4426 | 4: @{ | |
4427 | 5: public: | |
4428 | 6: Bass(); | |
4429 | 7: @}; | |
4430 | 8: | |
4431 | 9: inline | |
4432 | 10: Bass::Bass() | |
4433 | 11: : eString( new BassString( 0.105 )), | |
4434 | 12: aString( new BassString( 0.085 )), | |
4435 | 13: dString( new BassString( 0.065 )), | |
4436 | 14: gString( new BassString( 0.045 )) | |
4437 | 15: @{ | |
4438 | 16: eString.tune( 'E' ); | |
4439 | 17: aString.tune( 'A' ); | |
4440 | 18: dString.tune( 'D' ); | |
4441 | 19: gString.tune( 'G' ); | |
4442 | 20: @} | |
4443 | @end example | |
4444 | ||
4445 | @ssindex friend | |
4446 | Returning to the previous example, line 16 is given @code{inline-close} | |
4447 | syntax, while line 12 is given @code{defun-block-open} syntax, and lines | |
4448 | 13 through 15 are all given @code{statement} syntax. Line 17 is | |
4449 | interesting in that its syntactic analysis list contains three | |
4450 | elements: | |
4451 | ||
4452 | @example | |
4453 | ((inclass 58) (topmost-intro 380) (friend)) | |
4454 | @end example | |
4455 | ||
4456 | The @code{friend} and @code{inline-open} syntactic symbols are | |
4457 | modifiers that do not have anchor positions. | |
4458 | ||
4459 | @ssindex template-args-cont | |
4460 | Template definitions introduce yet another syntactic symbol: | |
4461 | ||
4462 | @example | |
4463 | 1: ThingManager <int, | |
4464 | 2: Framework::Callback *, | |
4465 | 3: Mutex> framework_callbacks; | |
4466 | @end example | |
4467 | ||
4468 | Here, line 1 is analyzed as a @code{topmost-intro}, but lines 2 and 3 | |
4469 | are both analyzed as @code{template-args-cont} lines. | |
4470 | ||
4471 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
4472 | @node Conditional Construct Symbols, Switch Statement Symbols, Class Symbols, Syntactic Symbols | |
4473 | @comment node-name, next, previous, up | |
4474 | @subsection Conditional Construct Symbols | |
4475 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
4476 | ||
4477 | Here is a (totally contrived) example which illustrates how syntax is | |
4478 | assigned to various conditional constructs: | |
4479 | ||
4480 | @example | |
4481 | 1: void spam( int index ) | |
4482 | 2: @{ | |
4483 | 3: for( int i=0; i<index; i++ ) | |
4484 | 4: @{ | |
4485 | 5: if( i == 10 ) | |
4486 | 6: do_something_special(); | |
4487 | 7: else | |
4488 | 8: silly_label: | |
4489 | 9: do_something( i ); | |
4490 | 10: @} | |
4491 | 11: do @{ | |
4492 | 12: another_thing( i-- ); | |
4493 | 13: @} | |
4494 | 14: while( i > 0 ); | |
4495 | 15: @} | |
4496 | @end example | |
4497 | ||
4498 | Only the lines that illustrate new syntactic symbols will be discussed. | |
4499 | ||
4500 | @ssindex substatement-open | |
4501 | @ssindex statement-block-intro | |
4502 | @ssindex block-close | |
4503 | Line 4 has a brace which opens a conditional's substatement block. It | |
4504 | is thus assigned @code{substatement-open} syntax, and since line 5 is | |
4505 | the first line in the substatement block, it is assigned | |
4506 | @code{statement-block-intro} syntax. Line 10 contains the brace | |
4507 | that closes the inner substatement block, and is therefore given the | |
4508 | syntax @code{block-close}@footnote{@code{block-open} is used only for | |
4509 | ``free-standing'' blocks, and is somewhat rare (@pxref{Literal | |
4510 | Symbols} for an example.)}. Line 13 is treated the same way. | |
4511 | ||
4512 | @ssindex substatement | |
4513 | Lines 6 and 9 are also substatements of conditionals, but since they | |
4514 | don't start blocks they are given @code{substatement} syntax | |
4515 | instead of @code{substatement-open}. | |
4516 | ||
4517 | @ssindex substatement-label | |
4518 | Line 8 contains a label, which is normally given @code{label} syntax. | |
4519 | This one is however a bit special since it's between a conditional and | |
4520 | its substatement. It's analyzed as @code{substatement-label} to let you | |
4521 | handle this rather odd case differently from normal labels. | |
4522 | ||
4523 | @ssindex else-clause | |
4524 | @ssindex catch-clause | |
4525 | Line 7 start with an @code{else} that matches the @code{if} statement on | |
4526 | line 5. It is therefore given the @code{else-clause} syntax and is | |
4527 | anchored on the matching @code{if}. The @code{try}-@code{catch} | |
4528 | constructs in C++ and Java are treated this way too, except that | |
4529 | @code{catch} and (in Java) @code{finally}, are marked with | |
4530 | @code{catch-clause}. | |
4531 | ||
4532 | @ssindex do-while-closure | |
4533 | The @code{while} construct on line 14 that closes a @code{do} | |
4534 | conditional is given the special syntax @code{do-while-closure} if it | |
4535 | appears on a line by itself. Note that if the @code{while} appeared on | |
4536 | the same line as the preceding close brace, that line would still have | |
4537 | @code{block-close} syntax. | |
4538 | ||
4539 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
4540 | @node Switch Statement Symbols, Brace List Symbols, Conditional Construct Symbols, Syntactic Symbols | |
4541 | @comment node-name, next, previous, up | |
4542 | @subsection Switch Statement Symbols | |
4543 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
4544 | ||
4545 | Switch statements have their own set of syntactic symbols. Here's an | |
4546 | example: | |
4547 | ||
4548 | @example | |
4549 | 1: void spam( enum Ingredient i ) | |
4550 | 2: @{ | |
4551 | 3: switch( i ) @{ | |
4552 | 4: case Ham: | |
4553 | 5: be_a_pig(); | |
4554 | 6: break; | |
4555 | 7: case Salt: | |
4556 | 8: drink_some_water(); | |
4557 | 9: break; | |
4558 | 10: default: | |
4559 | 11: @{ | |
4560 | 12: what_is_it(); | |
4561 | 13: break; | |
4562 | 14: @} | |
4563 | 15: @} | |
4564 | 14: @} | |
4565 | @end example | |
4566 | ||
4567 | @ssindex case-label | |
4568 | @ssindex statement-case-intro | |
4569 | @ssindex statement-case-open | |
4570 | Here, lines 4, 7, and 10 are all assigned @code{case-label} syntax, | |
4571 | while lines 5 and 8 are assigned @code{statement-case-intro}. Line 11 | |
4572 | is treated slightly differently since it contains a brace that opens a | |
f99f1641 | 4573 | block; it is given @code{statement-case-open} syntax. |
4009494e GM |
4574 | |
4575 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
4576 | @node Brace List Symbols, External Scope Symbols, Switch Statement Symbols, Syntactic Symbols | |
4577 | @comment node-name, next, previous, up | |
4578 | @subsection Brace List Symbols | |
4579 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
4580 | ||
4581 | @cindex brace lists | |
4582 | There are a set of syntactic symbols that are used to recognize | |
4583 | constructs inside of brace lists. A brace list is defined as an | |
4584 | @code{enum} or aggregate initializer list, such as might statically | |
4585 | initialize an array of structs. The three special aggregate constructs | |
4586 | in Pike, @code{(@{ @})}, @code{([ ])} and @code{(< >)}, are treated as | |
4587 | brace lists too. An example: | |
4588 | ||
4589 | @example | |
4590 | 1: static char* ingredients[] = | |
4591 | 2: @{ | |
4592 | 3: "Ham", | |
4593 | 4: "Salt", | |
4594 | 5: NULL | |
4595 | 6: @}; | |
4596 | @end example | |
4597 | ||
4598 | @ssindex brace-list-open | |
4599 | @ssindex brace-list-intro | |
4600 | @ssindex brace-list-close | |
4601 | @ssindex brace-list-entry | |
4602 | Following convention, line 2 in this example is assigned | |
4603 | @code{brace-list-open} syntax, and line 3 is assigned | |
4604 | @code{brace-list-intro} syntax. Likewise, line 6 is assigned | |
4605 | @code{brace-list-close} syntax. Lines 4 and 5 however, are assigned | |
4606 | @code{brace-list-entry} syntax, as would all subsequent lines in this | |
4607 | initializer list. | |
4608 | ||
4609 | @ssindex brace-entry-open | |
4610 | Your static initializer might be initializing nested structures, for | |
4611 | example: | |
4612 | ||
4613 | @example | |
4614 | 1: struct intpairs[] = | |
4615 | 2: @{ | |
4616 | 3: @{ 1, 2 @}, | |
4617 | 4: @{ | |
4618 | 5: 3, | |
4619 | 6: 4 | |
4620 | 7: @} | |
4621 | 8: @{ 1, | |
4622 | 9: 2 @}, | |
4623 | 10: @{ 3, 4 @} | |
4624 | 11: @}; | |
4625 | @end example | |
4626 | ||
4627 | Here, you've already seen the analysis of lines 1, 2, 3, and 11. On | |
4628 | line 4, things get interesting; this line is assigned | |
4629 | @code{brace-entry-open} syntactic symbol because it's a bracelist entry | |
4630 | line that starts with an open brace. Lines 5 and 6 (and line 9) are | |
4631 | pretty standard, and line 7 is a @code{brace-list-close} as you'd | |
4632 | expect. Once again, line 8 is assigned as @code{brace-entry-open} as is | |
4633 | line 10. | |
4634 | ||
4635 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
4636 | @node External Scope Symbols, Paren List Symbols, Brace List Symbols, Syntactic Symbols | |
4637 | @comment node-name, next, previous, up | |
4638 | @subsection External Scope Symbols | |
4639 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
4640 | ||
4641 | External language definition blocks also have their own syntactic | |
4642 | symbols. In this example: | |
4643 | ||
4644 | @example | |
4645 | 1: extern "C" | |
4646 | 2: @{ | |
4647 | 3: int thing_one( int ); | |
4648 | 4: int thing_two( double ); | |
4649 | 5: @} | |
4650 | @end example | |
4651 | ||
4652 | @ssindex extern-lang-open | |
4653 | @ssindex extern-lang-close | |
4654 | @ssindex inextern-lang | |
4655 | @ssindex inclass | |
4656 | @noindent | |
4657 | line 2 is given the @code{extern-lang-open} syntax, while line 5 is given | |
4658 | the @code{extern-lang-close} syntax. The analysis for line 3 yields: | |
4659 | ||
4660 | @example | |
4661 | ((inextern-lang) (topmost-intro 14)) | |
4662 | @end example | |
4663 | ||
4664 | @noindent | |
4665 | where @code{inextern-lang} is a modifier similar in purpose to | |
4666 | @code{inclass}. | |
4667 | ||
4668 | There are various other top level blocks like @code{extern}, and they | |
4669 | are all treated in the same way except that the symbols are named after | |
1df7defd | 4670 | the keyword that introduces the block. E.g., C++ namespace blocks get |
4009494e GM |
4671 | the three symbols @code{namespace-open}, @code{namespace-close} and |
4672 | @code{innamespace}. The currently recognized top level blocks are: | |
4673 | ||
4674 | @table @asis | |
4675 | @item @code{extern-lang-open}, @code{extern-lang-close}, @code{inextern-lang} | |
4676 | @code{extern} blocks in C and C++.@footnote{These should logically be | |
4677 | named @code{extern-open}, @code{extern-close} and @code{inextern}, but | |
4678 | that isn't the case for historical reasons.} | |
4679 | ||
4680 | @item @code{namespace-open}, @code{namespace-close}, @code{innamespace} | |
4681 | @ssindex namespace-open | |
4682 | @ssindex namespace-close | |
4683 | @ssindex innamespace | |
4684 | @code{namespace} blocks in C++. | |
4685 | ||
4686 | @item @code{module-open}, @code{module-close}, @code{inmodule} | |
4687 | @ssindex module-open | |
4688 | @ssindex module-close | |
4689 | @ssindex inmodule | |
4690 | @code{module} blocks in CORBA IDL. | |
4691 | ||
4692 | @item @code{composition-open}, @code{composition-close}, @code{incomposition} | |
4693 | @ssindex composition-open | |
4694 | @ssindex composition-close | |
4695 | @ssindex incomposition | |
4696 | @code{composition} blocks in CORBA CIDL. | |
4697 | @end table | |
4698 | ||
4699 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
4700 | @node Paren List Symbols, Literal Symbols, External Scope Symbols, Syntactic Symbols | |
4701 | @comment node-name, next, previous, up | |
4702 | @subsection Parenthesis (Argument) List Symbols | |
4703 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
4704 | ||
4705 | A number of syntactic symbols are associated with parenthesis lists, | |
4706 | a.k.a argument lists, as found in function declarations and function | |
4707 | calls. This example illustrates these: | |
4708 | ||
4709 | @example | |
4710 | 1: void a_function( int line1, | |
4711 | 2: int line2 ); | |
4712 | 3: | |
4713 | 4: void a_longer_function( | |
4714 | 5: int line1, | |
4715 | 6: int line2 | |
4716 | 7: ); | |
4717 | 8: | |
4718 | 9: void call_them( int line1, int line2 ) | |
4719 | 10: @{ | |
4720 | 11: a_function( | |
4721 | 12: line1, | |
4722 | 13: line2 | |
4723 | 14: ); | |
4724 | 15: | |
4725 | 16: a_longer_function( line1, | |
4726 | 17: line2 ); | |
4727 | 18: @} | |
4728 | @end example | |
4729 | ||
4730 | @ssindex arglist-intro | |
4731 | @ssindex arglist-close | |
4732 | Lines 5 and 12 are assigned @code{arglist-intro} syntax since they are | |
4733 | the first line following the open parenthesis, and lines 7 and 14 are | |
4734 | assigned @code{arglist-close} syntax since they contain the parenthesis | |
4735 | that closes the argument list. | |
4736 | ||
4737 | @ssindex arglist-cont-nonempty | |
4738 | @ssindex arglist-cont | |
4739 | Lines that continue argument lists can be assigned one of two syntactic | |
4740 | symbols. For example, Lines 2 and 17 | |
4741 | are assigned @code{arglist-cont-nonempty} syntax. What this means | |
4742 | is that they continue an argument list, but that the line containing the | |
4743 | parenthesis that opens the list is @emph{not empty} following the open | |
4744 | parenthesis. Contrast this against lines 6 and 13 which are assigned | |
4745 | @code{arglist-cont} syntax. This is because the parenthesis that opens | |
4746 | their argument lists is the last character on that line. | |
4747 | ||
4748 | Syntactic elements with @code{arglist-intro}, | |
4749 | @code{arglist-cont-nonempty}, and @code{arglist-close} contain two | |
4750 | buffer positions: the anchor position (the beginning of the | |
4751 | declaration or statement) and the position of the open parenthesis. | |
4752 | The latter position can be used in a line-up function (@pxref{Line-Up | |
4753 | Functions}). | |
4754 | ||
4755 | Note that there is no @code{arglist-open} syntax. This is because any | |
4756 | parenthesis that opens an argument list, appearing on a separate line, | |
4757 | is assigned the @code{statement-cont} syntax instead. | |
4758 | ||
4759 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
4760 | @node Literal Symbols, Multiline Macro Symbols, Paren List Symbols, Syntactic Symbols | |
4761 | @comment node-name, next, previous, up | |
4762 | @subsection Comment String Label and Macro Symbols | |
4763 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
4764 | ||
4765 | A few miscellaneous syntactic symbols that haven't been previously | |
4766 | covered are illustrated by this C++ example: | |
4767 | ||
4768 | @example | |
4769 | 1: void Bass::play( int volume ) | |
4770 | 2: const | |
4771 | 3: @{ | |
4772 | 4: /* this line starts a multiline | |
4773 | 5: * comment. This line should get `c' syntax */ | |
4774 | 6: | |
4775 | 7: char* a_multiline_string = "This line starts a multiline \ | |
4776 | 8: string. This line should get `string' syntax."; | |
4777 | 9: | |
4778 | 10: note: | |
4779 | 11: @{ | |
4780 | 12: #ifdef LOCK | |
4781 | 13: Lock acquire(); | |
4782 | 14: #endif // LOCK | |
4783 | 15: slap_pop(); | |
4784 | 16: cout << "I played " | |
4785 | 17: << "a note\n"; | |
4786 | 18: @} | |
4787 | 19: @} | |
4788 | @end example | |
4789 | ||
4790 | The lines to note in this example include: | |
4791 | ||
4792 | @itemize @bullet | |
4793 | @item | |
4794 | @ssindex func-decl-cont | |
4795 | Line 2 is assigned the @code{func-decl-cont} syntax. | |
4796 | ||
4797 | @item | |
4798 | @ssindex comment-intro | |
4799 | Line 4 is assigned both @code{defun-block-intro} @emph{and} | |
4800 | @code{comment-intro} syntax. A syntactic element with | |
f99f1641 | 4801 | @code{comment-intro} has no anchor point. It is always accompanied |
4009494e GM |
4802 | by another syntactic element which does have one. |
4803 | ||
4804 | @item | |
4805 | @ssindex c | |
4806 | Line 5 is assigned @code{c} syntax. | |
4807 | ||
4808 | @item | |
4809 | @cindex syntactic whitespace | |
4810 | Line 6 which, even though it contains nothing but whitespace, is | |
4811 | assigned @code{defun-block-intro}. Note that the appearance of the | |
4812 | comment on lines 4 and 5 do not cause line 6 to be assigned | |
4813 | @code{statement} syntax because comments are considered to be | |
4814 | @dfn{syntactic whitespace}, which are ignored when analyzing | |
4815 | code. | |
4816 | ||
4817 | @item | |
4818 | @ssindex string | |
4819 | Line 8 is assigned @code{string} syntax. | |
4820 | ||
4821 | @item | |
4822 | @ssindex label | |
4823 | Line 10 is assigned @code{label} syntax. | |
4824 | ||
4825 | @item | |
4826 | @ssindex block-open | |
4827 | Line 11 is assigned @code{block-open} as well as @code{statement} | |
4828 | syntax. A @code{block-open} syntactic element doesn't have an anchor | |
4829 | position, since it always appears with another syntactic element which | |
4830 | does have one. | |
4831 | ||
4832 | @item | |
4833 | @ssindex cpp-macro | |
4834 | Lines 12 and 14 are assigned @code{cpp-macro} syntax in addition to the | |
4835 | normal syntactic symbols (@code{statement-block-intro} and | |
4836 | @code{statement}, respectively). Normally @code{cpp-macro} is | |
4837 | configured to cancel out the normal syntactic context to make all | |
4838 | preprocessor directives stick to the first column, but that's easily | |
4839 | changed if you want preprocessor directives to be indented like the rest | |
4840 | of the code. Like @code{comment-intro}, a syntactic element with | |
4841 | @code{cpp-macro} doesn't contain an anchor position. | |
4842 | ||
4843 | @item | |
4844 | @ssindex stream-op | |
4845 | Line 17 is assigned @code{stream-op} syntax. | |
4846 | @end itemize | |
4847 | ||
4848 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
4849 | @node Multiline Macro Symbols, Objective-C Method Symbols, Literal Symbols, Syntactic Symbols | |
4850 | @comment node-name, next, previous, up | |
4851 | @subsection Multiline Macro Symbols | |
4852 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
4853 | ||
4854 | @cindex multiline macros | |
4855 | @cindex syntactic whitespace | |
4856 | @ssindex cpp-define-intro | |
4857 | @ssindex cpp-macro-cont | |
4858 | Multiline preprocessor macro definitions are normally handled just like | |
1df7defd | 4859 | other code, i.e., the lines inside them are indented according to the |
4009494e | 4860 | syntactic analysis of the preceding lines inside the macro. The first |
1df7defd | 4861 | line inside a macro definition (i.e., the line after the starting line of |
4009494e GM |
4862 | the cpp directive itself) gets @code{cpp-define-intro}. In this example: |
4863 | ||
4864 | @example | |
4865 | 1: #define LIST_LOOP(cons, listp) \ | |
4866 | 2: for (cons = listp; !NILP (cons); cons = XCDR (cons)) \ | |
4867 | 3: if (!CONSP (cons)) \ | |
4868 | 4: signal_error ("Invalid list format", listp); \ | |
4869 | 5: else | |
4870 | @end example | |
4871 | ||
4872 | @noindent | |
4873 | line 1 is given the syntactic symbol @code{cpp-macro}. The first line | |
4874 | of a cpp directive is always given that symbol. Line 2 is given | |
4875 | @code{cpp-define-intro}, so that you can give the macro body as a whole | |
4876 | some extra indentation. Lines 3 through 5 are then analyzed as normal | |
1df7defd | 4877 | code, i.e., @code{substatement} on lines 3 and 4, and @code{else-clause} |
4009494e GM |
4878 | on line 5. |
4879 | ||
4880 | The syntactic analysis inside macros can be turned off with | |
4881 | @code{c-syntactic-indentation-in-macros} (@pxref{Custom Macros}). In | |
4882 | that case, lines 2 through 5 would all be given @code{cpp-macro-cont} | |
4883 | with an anchor position pointing to the @code{#} which starts the cpp | |
4884 | directive@footnote{This is how @ccmode{} 5.28 and earlier analyzed | |
4885 | macros.}. | |
4886 | ||
4887 | @xref{Custom Macros}, for more info about the treatment of macros. | |
4888 | ||
4889 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5cee0a9c | 4890 | @node Objective-C Method Symbols, Java Symbols, Multiline Macro Symbols, Syntactic Symbols |
4009494e GM |
4891 | @comment node-name, next, previous, up |
4892 | @subsection Objective-C Method Symbols | |
4893 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
4894 | ||
4895 | In Objective-C buffers, there are three additional syntactic symbols | |
4896 | assigned to various message calling constructs. Here's an example | |
4897 | illustrating these: | |
4898 | ||
4899 | @example | |
4900 | 1: - (void)setDelegate:anObject | |
4901 | 2: withStuff:stuff | |
4902 | 3: @{ | |
4903 | 4: [delegate masterWillRebind:self | |
4904 | 5: toDelegate:anObject | |
4905 | 6: withExtraStuff:stuff]; | |
4906 | 7: @} | |
4907 | @end example | |
4908 | ||
4909 | @ssindex objc-method-intro | |
4910 | @ssindex objc-method-args-cont | |
4911 | @ssindex objc-method-call-cont | |
4912 | Here, line 1 is assigned @code{objc-method-intro} syntax, and line 2 is | |
4913 | assigned @code{objc-method-args-cont} syntax. Lines 5 and 6 are both | |
4914 | assigned @code{objc-method-call-cont} syntax. | |
4915 | ||
4916 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5cee0a9c | 4917 | @node Java Symbols, Statement Block Symbols, Objective-C Method Symbols, Syntactic Symbols |
4009494e | 4918 | @comment node-name, next, previous, up |
5cee0a9c | 4919 | @subsection Java Symbols |
4009494e GM |
4920 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
4921 | ||
4922 | Java has a concept of anonymous classes which can look something like | |
4923 | this: | |
4924 | ||
4925 | @example | |
5cee0a9c AM |
4926 | 1: @@Test |
4927 | 2: public void watch(Observable o) @{ | |
4928 | 3: @@NonNull | |
4929 | 4: Observer obs = new Observer() @{ | |
4930 | 5: public void update(Observable o, Object arg) @{ | |
4931 | 6: history.addElement(arg); | |
4932 | 7: @} | |
4933 | 8: @}; | |
4934 | 9: o.addObserver(obs); | |
4935 | 10: @} | |
4009494e GM |
4936 | @end example |
4937 | ||
4938 | @ssindex inexpr-class | |
4939 | The brace following the @code{new} operator opens the anonymous class. | |
5cee0a9c | 4940 | Lines 5 and 8 are assigned the @code{inexpr-class} syntax, besides the |
4009494e GM |
4941 | @code{inclass} symbol used in normal classes. Thus, the class will be |
4942 | indented just like a normal class, with the added indentation given to | |
4943 | @code{inexpr-class}. An @code{inexpr-class} syntactic element doesn't | |
4944 | have an anchor position. | |
4945 | ||
5cee0a9c AM |
4946 | @ssindex annotation-top-cont |
4947 | @ssindex annotation-var-cont | |
4948 | Line 2 is assigned the @code{annotation-top-cont} syntax, due to it being a | |
4949 | continuation of a topmost introduction with an annotation symbol preceding | |
4950 | the current line. Similarly, line 4 is assigned the @code{annotation-var-cont} | |
4951 | syntax due to it being a continuation of a variable declaration where preceding | |
4952 | the declaration is an annotation. | |
4953 | ||
4009494e | 4954 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
5cee0a9c | 4955 | @node Statement Block Symbols, K&R Symbols, Java Symbols, Syntactic Symbols |
4009494e GM |
4956 | @comment node-name, next, previous, up |
4957 | @subsection Statement Block Symbols | |
4958 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
4959 | ||
4960 | There are a few occasions where a statement block might be used inside | |
4961 | an expression. One is in C or C++ code using the gcc extension for | |
65e7ca35 | 4962 | this, e.g.: |
4009494e GM |
4963 | |
4964 | @example | |
4965 | 1: int res = (@{ | |
4966 | 2: int y = foo (); int z; | |
4967 | 3: if (y > 0) z = y; else z = - y; | |
4968 | 4: z; | |
4969 | 5: @}); | |
4970 | @end example | |
4971 | ||
4972 | @ssindex inexpr-statement | |
4973 | Lines 2 and 5 get the @code{inexpr-statement} syntax, besides the | |
4974 | symbols they'd get in a normal block. Therefore, the indentation put on | |
4975 | @code{inexpr-statement} is added to the normal statement block | |
4976 | indentation. An @code{inexpr-statement} syntactic element doesn't | |
4977 | contain an anchor position. | |
4978 | ||
4979 | In Pike code, there are a few other situations where blocks occur inside | |
4980 | statements, as illustrated here: | |
4981 | ||
4982 | @example | |
4983 | 1: array itgob() | |
4984 | 2: @{ | |
4985 | 3: string s = map (backtrace()[-2][3..], | |
4986 | 4: lambda | |
4987 | 5: (mixed arg) | |
4988 | 6: @{ | |
4989 | 7: return sprintf ("%t", arg); | |
4990 | 8: @}) * ", " + "\n"; | |
4991 | 9: return catch @{ | |
4992 | 10: write (s + "\n"); | |
4993 | 11: @}; | |
4994 | 12: @} | |
4995 | @end example | |
4996 | ||
4997 | @ssindex inlambda | |
4998 | @ssindex lambda-intro-cont | |
4999 | Lines 4 through 8 contain a lambda function, which @ccmode{} recognizes | |
5000 | by the @code{lambda} keyword. If the function argument list is put | |
5001 | on a line of its own, as in line 5, it gets the @code{lambda-intro-cont} | |
5002 | syntax. The function body is handled as an inline method body, with the | |
5003 | addition of the @code{inlambda} syntactic symbol. This means that line | |
5004 | 6 gets @code{inlambda} and @code{inline-open}, and line 8 gets | |
5005 | @code{inline-close}@footnote{You might wonder why it doesn't get | |
5006 | @code{inlambda} too. It's because the closing brace is relative to the | |
5007 | opening brace, which stands on its own line in this example. If the | |
5008 | opening brace was hanging on the previous line, then the closing brace | |
5009 | would get the @code{inlambda} syntax too to be indented correctly.}. | |
5010 | ||
5011 | @ssindex inexpr-statement | |
5012 | On line 9, @code{catch} is a special function taking a statement block | |
5013 | as its argument. The block is handled as an in-expression statement | |
5014 | with the @code{inexpr-statement} syntax, just like the gcc extended C | |
5015 | example above. The other similar special function, @code{gauge}, is | |
5016 | handled like this too. | |
5017 | ||
5018 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5019 | @node K&R Symbols, , Statement Block Symbols, Syntactic Symbols | |
5020 | @comment node-name, next, previous, up | |
5021 | @subsection K&R Symbols | |
5022 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5023 | ||
5024 | @ssindex knr-argdecl-intro | |
5025 | @ssindex knr-argdecl | |
5026 | Two other syntactic symbols can appear in old style, non-prototyped C | |
1df7defd | 5027 | code @footnote{a.k.a.@: K&R C, or Kernighan & Ritchie C}: |
4009494e GM |
5028 | |
5029 | @example | |
5030 | 1: int add_three_integers(a, b, c) | |
5031 | 2: int a; | |
5032 | 3: int b; | |
5033 | 4: int c; | |
5034 | 5: @{ | |
5035 | 6: return a + b + c; | |
5036 | 7: @} | |
5037 | @end example | |
5038 | ||
5039 | Here, line 2 is the first line in an argument declaration list and so is | |
5040 | given the @code{knr-argdecl-intro} syntactic symbol. Subsequent lines | |
1df7defd | 5041 | (i.e., lines 3 and 4 in this example), are given @code{knr-argdecl} |
4009494e GM |
5042 | syntax. |
5043 | ||
5044 | ||
5045 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5046 | @node Indentation Calculation, , Syntactic Symbols, Indentation Engine Basics | |
5047 | @comment node-name, next, previous, up | |
5048 | @section Indentation Calculation | |
5049 | @cindex indentation | |
5050 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5051 | ||
5052 | Indentation for a line is calculated from the syntactic context | |
5053 | (@pxref{Syntactic Analysis}). | |
5054 | ||
5055 | First, a buffer position is found whose column will be the base for the | |
5056 | indentation calculation. It's the anchor position in the first | |
5057 | syntactic element that provides one that is used. If no syntactic | |
5058 | element has an anchor position then column zero is used. | |
5059 | ||
5060 | Second, the syntactic symbols in each syntactic element are looked up | |
5061 | in the @code{c-offsets-alist} style variable | |
5062 | (@pxref{c-offsets-alist}), which is an association list of syntactic | |
5063 | symbols and the offsets to apply for those symbols. These offsets are | |
5064 | added together with the base column to produce the new indentation | |
5065 | column. | |
5066 | ||
5067 | Let's use our two code examples above to see how this works. Here is | |
5068 | our first example again: | |
5069 | ||
5070 | @example | |
5071 | 1: void swap( int& a, int& b ) | |
5072 | 2: @{ | |
5073 | 3: int tmp = a; | |
5074 | 4: a = b; | |
5075 | 5: b = tmp; | |
5076 | 6: @} | |
5077 | @end example | |
5078 | ||
5079 | Let's say point is on line 3 and we hit the @key{TAB} key to reindent | |
5080 | the line. The syntactic context for that line is: | |
5081 | ||
5082 | @example | |
5083 | ((defun-block-intro 29)) | |
5084 | @end example | |
5085 | ||
5086 | @noindent | |
5087 | Since buffer position 29 is the first and only anchor position in the | |
5088 | list, @ccmode{} goes there and asks for the current column. This brace | |
5089 | is in column zero, so @ccmode{} uses @samp{0} as the base column. | |
5090 | ||
5091 | Next, @ccmode{} looks up @code{defun-block-intro} in the | |
5092 | @code{c-offsets-alist} style variable. Let's say it finds the value | |
5093 | @samp{4}; it adds this to the base column @samp{0}, yielding a running | |
5094 | total indentation of 4 spaces. | |
5095 | ||
5096 | Since there is only one syntactic element on the list for this line, | |
5097 | indentation calculation is complete, and the total indentation for the | |
5098 | line is 4 spaces. | |
5099 | ||
5100 | Here's another example: | |
5101 | ||
5102 | @example | |
5103 | 1: int add( int val, int incr, int doit ) | |
5104 | 2: @{ | |
5105 | 3: if( doit ) | |
5106 | 4: @{ | |
5107 | 5: return( val + incr ); | |
5108 | 6: @} | |
5109 | 7: return( val ); | |
5110 | 8: @} | |
5111 | @end example | |
5112 | ||
5113 | If we were to hit @kbd{TAB} on line 4 in the above example, the same | |
5114 | basic process is performed, despite the differences in the syntactic | |
5115 | context. The context for this line is: | |
5116 | ||
5117 | @example | |
5118 | ((substatement-open 46)) | |
5119 | @end example | |
5120 | ||
5121 | Here, @ccmode{} goes to buffer position 46, which is the @samp{i} in | |
5122 | @code{if} on line 3. This character is in the fourth column on that | |
5123 | line so the base column is @samp{4}. Then @ccmode{} looks up the | |
5124 | @code{substatement-open} symbol in @code{c-offsets-alist}. Let's say it | |
5125 | finds the value @samp{4}. It's added with the base column and yields an | |
5126 | indentation for the line of 8 spaces. | |
5127 | ||
5128 | Simple, huh? | |
5129 | ||
5130 | Actually, it's a bit more complicated than that since the entries on | |
5131 | @code{c-offsets-alist} can be much more than plain offsets. | |
5132 | @xref{c-offsets-alist}, for the full story. | |
5133 | ||
5134 | Anyway, the mode usually just does The Right Thing without you having to | |
5135 | think about it in this much detail. But when customizing indentation, | |
5136 | it's helpful to understand the general indentation model being used. | |
5137 | ||
5138 | As you configure @ccmode{}, you might want to set the variable | |
5139 | @code{c-echo-syntactic-information-p} to non-@code{nil} so that the | |
5140 | syntactic context and calculated offset always is echoed in the | |
5141 | minibuffer when you hit @kbd{TAB}. | |
5142 | ||
5143 | ||
5144 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5145 | @node Customizing Indentation, Custom Macros, Indentation Engine Basics, Top | |
5146 | @comment node-name, next, previous, up | |
5147 | @chapter Customizing Indentation | |
5148 | @cindex customization, indentation | |
5149 | @cindex indentation | |
5150 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5151 | ||
5152 | The principal variable for customizing indentation is the style | |
5153 | variable @code{c-offsets-alist}, which gives an @dfn{offset} (an | |
5154 | indentation rule) for each syntactic symbol. Its structure and | |
5155 | semantics are completely described in @ref{c-offsets-alist}. The | |
5156 | various ways you can set the variable, including the use of the | |
5157 | @ccmode{} style system, are described in @ref{Config Basics} and its | |
5158 | sections, in particular @ref{Style Variables}. | |
5159 | ||
5160 | The simplest and most used kind of ``offset'' setting in | |
5161 | @code{c-offsets-alist} is in terms of multiples of | |
5162 | @code{c-basic-offset}: | |
5163 | ||
5164 | @defopt c-basic-offset | |
5165 | @vindex basic-offset (c-) | |
5166 | This style variable holds the basic offset between indentation levels. | |
5167 | It's factory default is 4, but all the built-in styles set it | |
5168 | themselves, to some value between 2 (for @code{gnu} style) and 8 (for | |
5169 | @code{bsd}, @code{linux}, and @code{python} styles). | |
5170 | @end defopt | |
5171 | ||
5172 | The most flexible ``offset'' setting you can make in | |
5173 | @code{c-offsets-alist} is a line-up function (or even a list of them), | |
5174 | either one supplied by @ccmode{} (@pxref{Line-Up Functions}) or one | |
5175 | you write yourself (@pxref{Custom Line-Up}). | |
5176 | ||
5177 | Finally, in @ref{Other Indentation} you'll find the tool of last | |
5178 | resort: a hook which is called after a line has been indented. You | |
5179 | can install functions here to make ad-hoc adjustments to any line's | |
5180 | indentation. | |
5181 | ||
5182 | @menu | |
5183 | * c-offsets-alist:: | |
5184 | * Interactive Customization:: | |
5185 | * Line-Up Functions:: | |
5186 | * Custom Line-Up:: | |
5187 | * Other Indentation:: | |
5188 | @end menu | |
5189 | ||
5190 | ||
5191 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5192 | @node c-offsets-alist, Interactive Customization, Customizing Indentation, Customizing Indentation | |
5193 | @comment node-name, next, previous, up | |
5194 | @section c-offsets-alist | |
5195 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5196 | ||
5197 | This section explains the structure and semantics of the style | |
932de51c | 5198 | variable @code{c-offsets-alist}, the principal variable for configuring |
4009494e GM |
5199 | indentation. Details of how to set it up, and its relationship to |
5200 | @ccmode{}'s style system are given in @ref{Style Variables}. | |
5201 | ||
5202 | @defopt c-offsets-alist | |
5203 | @vindex offsets-alist (c-) | |
5204 | This is an alist which associates an offset with each syntactic | |
5205 | symbol. This @dfn{offset} is a rule specifying how to indent a line | |
5206 | whose syntactic context matches the symbol. @xref{Syntactic | |
5207 | Analysis}. | |
5208 | ||
5209 | Note that the buffer-local binding of this alist in a @ccmode{} buffer | |
5210 | contains an entry for @emph{every} syntactic symbol. Its global | |
5211 | binding and its settings within style specifications usually contain | |
5212 | only a few entries. @xref{Style Variables}. | |
5213 | ||
5214 | The offset specification associated with any particular syntactic | |
5215 | symbol can be an integer, a variable name, a vector, a function or | |
5216 | lambda expression, a list, or one of the following special symbols: | |
5217 | @code{+}, @code{-}, @code{++}, @code{--}, @code{*}, or @code{/}. The | |
5218 | meanings of these values are described in detail below. | |
5219 | ||
5220 | Here is an example fragment of a @code{c-offsets-alist}, showing some | |
5221 | of these kinds of offsets: | |
5222 | ||
5223 | @example | |
5224 | ((statement . 0) | |
5225 | (substatement . +) | |
5226 | (cpp-macro . [0]) | |
5227 | (topmost-intro-cont . c-lineup-topmost-intro-cont) | |
5228 | (statement-block-intro . (add c-lineup-whitesmith-in-block | |
5229 | c-indent-multi-line-block)) | |
5230 | @dots{} | |
5231 | @*) | |
5232 | @end example | |
5233 | @end defopt | |
5234 | ||
5235 | @deffn Command c-set-offset (@kbd{C-c C-o}) | |
5236 | @findex set-offset (c-) | |
5237 | @kindex C-c C-o | |
5238 | This command changes the entry for a syntactic symbol in the current | |
5239 | binding of @code{c-offsets-alist}, or it inserts a new entry if there | |
5240 | isn't already one for that syntactic symbol. | |
5241 | ||
5242 | You can use @code{c-set-offsets} interactively within a @ccmode{} | |
5243 | buffer to make experimental changes to your indentation settings. | |
5244 | @kbd{C-c C-o} prompts you for the syntactic symbol to change | |
5245 | (defaulting to that of the current line) and the new offset | |
5246 | (defaulting to the current offset). | |
5247 | ||
5248 | @code{c-set-offsets} takes two arguments when used programmatically: | |
5249 | @var{symbol}, the syntactic element symbol to change and @var{offset}, | |
5250 | the new offset for that syntactic element. You can call the command | |
5251 | in your @file{.emacs} to change the global binding of | |
5252 | @code{c-offsets-alist} (@pxref{Style Variables}); you can use it in a | |
5253 | hook function to make changes from the current style. @ccmode{} | |
5254 | itself uses this function when initializing styles. | |
5255 | @end deffn | |
5256 | ||
5257 | @cindex offset specification | |
5258 | The ``offset specifications'' in @code{c-offsets-alist} can be any of | |
5259 | the following: | |
5260 | ||
5261 | @table @asis | |
5262 | @item An integer | |
5263 | The integer specifies a relative offset. All relative | |
5264 | offsets@footnote{The syntactic context @code{@w{((defun-block-intro | |
5265 | 2724) (comment-intro))}} would likely have two relative offsets.} will | |
5266 | be added together and used to calculate the indentation relative to an | |
5267 | anchor position earlier in the buffer. @xref{Indentation | |
5268 | Calculation}, for details. Most of the time, it's probably better to | |
5269 | use one of the special symbols like @code{+} than an integer (apart | |
5270 | from zero). | |
5271 | ||
5272 | @item One of the symbols @code{+}, @code{-}, @code{++}, @code{--}, @code{*}, or @code{/} | |
5273 | These special symbols describe a relative offset in multiples of | |
5274 | @code{c-basic-offset}: | |
5275 | ||
5276 | By defining a style's indentation in terms of @code{c-basic-offset}, | |
5277 | you can change the amount of whitespace given to an indentation level | |
5278 | while maintaining the same basic shape of your code. Here are the | |
5279 | values that the special symbols correspond to: | |
5280 | ||
5281 | @table @code | |
5282 | @item + | |
5283 | @code{c-basic-offset} times 1 | |
5284 | @item - | |
f99f1641 | 5285 | @code{c-basic-offset} times @minus{}1 |
4009494e GM |
5286 | @item ++ |
5287 | @code{c-basic-offset} times 2 | |
5288 | @item -- | |
f99f1641 | 5289 | @code{c-basic-offset} times @minus{}2 |
4009494e GM |
5290 | @item * |
5291 | @code{c-basic-offset} times 0.5 | |
5292 | @item / | |
f99f1641 | 5293 | @code{c-basic-offset} times @minus{}0.5 |
4009494e GM |
5294 | @end table |
5295 | ||
5296 | @item A vector | |
5297 | The first element of the vector, an integer, sets the absolute | |
5298 | indentation column. This will override any previously calculated | |
5299 | indentation, but won't override relative indentation calculated from | |
5300 | syntactic elements later on in the syntactic context of the line being | |
5301 | indented. @xref{Indentation Calculation}. Any elements in the vector | |
5302 | beyond the first will be ignored. | |
5303 | ||
5304 | @item A function or lambda expression | |
5305 | The function will be called and its return value will in turn be | |
5306 | evaluated as an offset specification. Functions are useful when more | |
5307 | context than just the syntactic symbol is needed to get the desired | |
5308 | indentation. @xref{Line-Up Functions}, and @ref{Custom Line-Up}, for | |
5309 | details about them. | |
5310 | ||
5311 | @item A symbol with a variable binding | |
5312 | If the symbol also has a function binding, the function takes | |
5313 | precedence over the variable. Otherwise the value of the variable is | |
5314 | used. It must be an integer (which is used as relative offset) or a | |
5315 | vector (an absolute offset). | |
5316 | ||
5317 | @item A list | |
5318 | The offset can also be a list containing several offset | |
5319 | specifications; these are evaluated recursively and combined. A list | |
5320 | is typically only useful when some of the offsets are line-up | |
5321 | functions. A common strategy is calling a sequence of functions in | |
5322 | turn until one of them recognizes that it is appropriate for the | |
5323 | source line and returns a non-@code{nil} value. | |
5324 | ||
5325 | @code{nil} values are always ignored when the offsets are combined. | |
5326 | The first element of the list specifies the method of combining the | |
5327 | non-@code{nil} offsets from the remaining elements: | |
5328 | ||
5329 | @table @code | |
5330 | @item first | |
5331 | Use the first offset that doesn't evaluate to @code{nil}. Subsequent | |
5332 | elements of the list don't get evaluated. | |
5333 | @item min | |
5334 | Use the minimum of all the offsets. All must be either relative or | |
f99f1641 | 5335 | absolute; they can't be mixed. |
4009494e GM |
5336 | @item max |
5337 | Use the maximum of all the offsets. All must be either relative or | |
f99f1641 | 5338 | absolute; they can't be mixed. |
4009494e GM |
5339 | @item add |
5340 | Add all the evaluated offsets together. Exactly one of them may be | |
5341 | absolute, in which case the result is absolute. Any relative offsets | |
5342 | that preceded the absolute one in the list will be ignored in that case. | |
5343 | @end table | |
5344 | ||
5345 | As a compatibility measure, if the first element is none of the above | |
5346 | then it too will be taken as an offset specification and the whole list | |
5347 | will be combined according to the method @code{first}. | |
5348 | @end table | |
5349 | ||
5350 | @vindex c-strict-syntax-p | |
5351 | @vindex strict-syntax-p (c-) | |
5352 | If an offset specification evaluates to @code{nil}, then a relative | |
5353 | offset of 0 (zero) is used@footnote{There is however a variable | |
5354 | @code{c-strict-syntax-p} that when set to non-@code{nil} will cause an | |
5355 | error to be signaled in that case. It's now considered obsolete since | |
5356 | it doesn't work well with some of the alignment functions that return | |
5357 | @code{nil} instead of zero. You should therefore leave | |
5358 | @code{c-strict-syntax-p} set to @code{nil}.}. | |
5359 | ||
5360 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5361 | @node Interactive Customization, Line-Up Functions, c-offsets-alist, Customizing Indentation | |
5362 | @comment node-name, next, previous, up | |
5363 | @section Interactive Customization | |
5364 | @cindex customization, interactive | |
5365 | @cindex interactive customization | |
5366 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5367 | ||
5368 | As an example of how to customize indentation, let's change the | |
5369 | style of this example@footnote{In this and subsequent examples, the | |
5370 | original code is formatted using the @samp{gnu} style unless otherwise | |
5371 | indicated. @xref{Styles}.}: | |
5372 | ||
5373 | @example | |
5374 | @group | |
5375 | 1: int add( int val, int incr, int doit ) | |
5376 | 2: @{ | |
5377 | 3: if( doit ) | |
5378 | 4: @{ | |
5379 | 5: return( val + incr ); | |
5380 | 6: @} | |
5381 | 7: return( val ); | |
5382 | 8: @} | |
5383 | @end group | |
5384 | @end example | |
5385 | ||
5386 | @noindent | |
5387 | to: | |
5388 | ||
5389 | @example | |
5390 | @group | |
5391 | 1: int add( int val, int incr, int doit ) | |
5392 | 2: @{ | |
5393 | 3: if( doit ) | |
5394 | 4: @{ | |
5395 | 5: return( val + incr ); | |
5396 | 6: @} | |
5397 | 7: return( val ); | |
5398 | 8: @} | |
5399 | @end group | |
5400 | @end example | |
5401 | ||
5402 | In other words, we want to change the indentation of braces that open a | |
5403 | block following a condition so that the braces line up under the | |
5404 | conditional, instead of being indented. Notice that the construct we | |
5405 | want to change starts on line 4. To change the indentation of a line, | |
5406 | we need to see which syntactic symbols affect the offset calculations | |
5407 | for that line. Hitting @kbd{C-c C-s} on line 4 yields: | |
5408 | ||
5409 | @example | |
5410 | ((substatement-open 44)) | |
5411 | @end example | |
5412 | ||
5413 | @noindent | |
5414 | so we know that to change the offset of the open brace, we need to | |
5415 | change the indentation for the @code{substatement-open} syntactic | |
5416 | symbol. | |
5417 | ||
5418 | To do this interactively, just hit @kbd{C-c C-o}. This prompts | |
5419 | you for the syntactic symbol to change, providing a reasonable default. | |
5420 | In this case, the default is @code{substatement-open}, which is just the | |
5421 | syntactic symbol we want to change! | |
5422 | ||
5423 | After you hit return, @ccmode{} will then prompt you for the new | |
5424 | offset value, with the old value as the default. The default in this | |
5425 | case is @samp{+}, but we want no extra indentation so enter | |
5426 | @samp{0} and @kbd{RET}. This will associate the offset 0 with the | |
5427 | syntactic symbol @code{substatement-open}. | |
5428 | ||
5429 | To check your changes quickly, just hit @kbd{C-c C-q} | |
5430 | (@code{c-indent-defun}) to reindent the entire function. The example | |
5431 | should now look like: | |
5432 | ||
5433 | @example | |
5434 | @group | |
5435 | 1: int add( int val, int incr, int doit ) | |
5436 | 2: @{ | |
5437 | 3: if( doit ) | |
5438 | 4: @{ | |
5439 | 5: return( val + incr ); | |
5440 | 6: @} | |
5441 | 7: return( val ); | |
5442 | 8: @} | |
5443 | @end group | |
5444 | @end example | |
5445 | ||
5446 | Notice how just changing the open brace offset on line 4 is all we | |
5447 | needed to do. Since the other affected lines are indented relative to | |
5448 | line 4, they are automatically indented the way you'd expect. For more | |
5449 | complicated examples, this might not always work. The general approach | |
5450 | to take is to always start adjusting offsets for lines higher up in the | |
5451 | file, then reindent and see if any following lines need further | |
5452 | adjustments. | |
5453 | ||
5454 | @c Move this bit to "Styles" (2005/10/7) | |
5455 | @deffn Command c-set-offset symbol offset | |
5456 | @findex set-offset (c-) | |
5457 | @kindex C-c C-o | |
5458 | This is the command bound to @kbd{C-c C-o}. It provides a convenient | |
5459 | way to set offsets on @code{c-offsets-alist} both interactively (see | |
5460 | the example above) and from your mode hook. | |
5461 | ||
5462 | It takes two arguments when used programmatically: @var{symbol} is the | |
5463 | syntactic element symbol to change and @var{offset} is the new offset | |
5464 | for that syntactic element. | |
5465 | @end deffn | |
5466 | @c End of MOVE THIS BIT. | |
5467 | ||
5468 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5469 | @node Line-Up Functions, Custom Line-Up, Interactive Customization, Customizing Indentation | |
5470 | @comment node-name, next, previous, up | |
5471 | @section Line-Up Functions | |
5472 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5473 | ||
5474 | @cindex line-up function | |
5475 | @cindex indentation function | |
5476 | Often there are cases when a simple offset setting on a syntactic | |
5477 | symbol isn't enough to get the desired indentation---for example, you | |
5478 | might want to line up a closing parenthesis with the matching opening | |
5479 | one rather than indenting relative to its ``anchor point''. @ccmode{} | |
5480 | provides this flexibility with @dfn{line-up functions}. | |
5481 | ||
5482 | The way you associate a line-up function with a syntactic symbol is | |
5483 | described in @ref{c-offsets-alist}. @ccmode{} comes with many | |
5484 | predefined line-up functions for common situations. If none of these | |
5485 | does what you want, you can write your own. @xref{Custom Line-Up}. | |
5486 | Sometimes, it is easier to tweak the standard indentation by adding a | |
5487 | function to @code{c-special-indent-hook} (@pxref{Other Indentation}). | |
5488 | ||
5489 | The line-up functions haven't been adapted for AWK buffers or tested | |
5490 | with them. Some of them might work serendipitously. There shouldn't be | |
5491 | any problems writing custom line-up functions for AWK mode. | |
5492 | ||
5493 | The calling convention for line-up functions is described fully in | |
5494 | @ref{Custom Line-Up}. Roughly speaking, the return value is either an | |
5495 | offset itself (such as @code{+} or @code{[0]}) or it's @code{nil}, | |
f99f1641 | 5496 | meaning ``this function is inappropriate in this case; try a |
4009494e GM |
5497 | different one''. @xref{c-offsets-alist}. |
5498 | ||
5499 | The subsections below describe all the standard line-up functions, | |
5500 | categorized by the sort of token the lining-up centers around. For | |
5501 | each of these functions there is a ``works with'' list that indicates | |
5502 | which syntactic symbols the function is intended to be used with. | |
5503 | ||
5504 | @macro workswith | |
5505 | @emph{Works with:@ } | |
5506 | @end macro | |
5507 | @ifinfo | |
5508 | @unmacro workswith | |
5509 | @macro workswith | |
5510 | Works with: | |
5511 | @end macro | |
5512 | @end ifinfo | |
5513 | ||
5514 | @macro sssTBasicOffset | |
5515 | <--> @i{c-basic-offset}@c | |
5516 | @end macro | |
5517 | ||
5518 | @macro sssTsssTBasicOffset | |
5519 | <--><--> @i{c-basic-offset}@c | |
5520 | @end macro | |
5521 | ||
5522 | @macro hereFn{func} | |
5523 | <- @i{\func\}@c | |
5524 | @end macro | |
5525 | ||
5526 | @c The TeX backend seems to insert extra spaces around the argument. :P | |
5527 | @iftex | |
5528 | @unmacro hereFn | |
5529 | @macro hereFn{func} | |
5530 | <-@i{\func\}@c | |
5531 | @end macro | |
5532 | @end iftex | |
5533 | ||
5534 | @menu | |
5535 | * Brace/Paren Line-Up:: | |
5536 | * List Line-Up:: | |
5537 | * Operator Line-Up:: | |
5538 | * Comment Line-Up:: | |
5539 | * Misc Line-Up:: | |
5540 | @end menu | |
5541 | ||
5542 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5543 | @node Brace/Paren Line-Up, List Line-Up, Line-Up Functions, Line-Up Functions | |
5544 | @comment node-name, next, previous, up | |
5545 | @subsection Brace and Parenthesis Line-Up Functions | |
5546 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5547 | ||
5548 | The line-up functions here calculate the indentation for braces, | |
5549 | parentheses and statements within brace blocks. | |
5550 | ||
5551 | @defun c-lineup-close-paren | |
5552 | @findex lineup-close-paren (c-) | |
5553 | Line up the closing paren under its corresponding open paren if the | |
5554 | open paren is followed by code. If the open paren ends its line, no | |
65e7ca35 | 5555 | indentation is added. E.g.: |
4009494e GM |
5556 | |
5557 | @example | |
5558 | @group | |
5559 | main (int, | |
5560 | char ** | |
5561 | ) @hereFn{c-lineup-close-paren} | |
5562 | @end group | |
5563 | @end example | |
5564 | ||
5565 | @noindent | |
5566 | and | |
5567 | ||
5568 | @example | |
5569 | @group | |
5570 | main ( | |
5571 | int, char ** | |
5572 | ) @hereFn{c-lineup-close-paren} | |
5573 | @end group | |
5574 | @end example | |
5575 | ||
5576 | As a special case, if a brace block is opened at the same line as the | |
5577 | open parenthesis of the argument list, the indentation is | |
5578 | @code{c-basic-offset} instead of the open paren column. See | |
5579 | @code{c-lineup-arglist} for further discussion of this ``DWIM'' measure. | |
5580 | ||
5581 | @workswith All @code{*-close} symbols. | |
5582 | @end defun | |
5583 | ||
5584 | @comment ------------------------------------------------------------ | |
5585 | ||
5586 | @anchor{c-lineup-arglist-close-under-paren} | |
5587 | @defun c-lineup-arglist-close-under-paren | |
5588 | @findex lineup-arglist-close-under-paren (c-) | |
5589 | Set your @code{arglist-close} syntactic symbol to this line-up function | |
5590 | so that parentheses that close argument lists will line up under the | |
5591 | parenthesis that opened the argument list. It can also be used with | |
5592 | @code{arglist-cont} and @code{arglist-cont-nonempty} to line up all | |
5593 | lines inside a parenthesis under the open paren. | |
5594 | ||
5595 | As a special case, if a brace block is opened at the same line as the | |
5596 | open parenthesis of the argument list, the indentation is | |
5597 | @code{c-basic-offset} only. See @code{c-lineup-arglist} for further | |
5598 | discussion of this ``DWIM'' measure. | |
5599 | ||
5600 | @workswith Almost all symbols, but are typically most useful on | |
5601 | @code{arglist-close}, @code{brace-list-close}, @code{arglist-cont} and | |
5602 | @code{arglist-cont-nonempty}. | |
5603 | @end defun | |
5604 | ||
5605 | @comment ------------------------------------------------------------ | |
5606 | ||
5607 | @defun c-indent-one-line-block | |
5608 | @findex indent-one-line-block (c-) | |
65e7ca35 | 5609 | Indent a one line block @code{c-basic-offset} extra. E.g.: |
4009494e GM |
5610 | |
5611 | @example | |
5612 | @group | |
5613 | if (n > 0) | |
5614 | @{m+=n; n=0;@} @hereFn{c-indent-one-line-block} | |
5615 | @sssTBasicOffset{} | |
5616 | @end group | |
5617 | @end example | |
5618 | ||
5619 | @noindent | |
5620 | and | |
5621 | ||
5622 | @example | |
5623 | @group | |
5624 | if (n > 0) | |
5625 | @{ @hereFn{c-indent-one-line-block} | |
5626 | m+=n; n=0; | |
5627 | @} | |
5628 | @end group | |
5629 | @end example | |
5630 | ||
5631 | The block may be surrounded by any kind of parenthesis characters. | |
5632 | @code{nil} is returned if the line doesn't start with a one line block, | |
5633 | which makes the function usable in list expressions. | |
5634 | ||
5635 | @workswith Almost all syntactic symbols, but most useful on the | |
5636 | @code{-open} symbols. | |
5637 | @end defun | |
5638 | ||
5639 | @comment ------------------------------------------------------------ | |
5640 | ||
5641 | @defun c-indent-multi-line-block | |
5642 | @findex indent-multi-line-block (c-) | |
65e7ca35 | 5643 | Indent a multiline block @code{c-basic-offset} extra. E.g.: |
4009494e GM |
5644 | |
5645 | @example | |
5646 | @group | |
5647 | int *foo[] = @{ | |
5648 | NULL, | |
5649 | @{17@}, @hereFn{c-indent-multi-line-block} | |
5650 | @end group | |
5651 | @end example | |
5652 | ||
5653 | @noindent | |
5654 | and | |
5655 | ||
5656 | @example | |
5657 | @group | |
5658 | int *foo[] = @{ | |
5659 | NULL, | |
5660 | @{ @hereFn{c-indent-multi-line-block} | |
5661 | 17 | |
5662 | @}, | |
5663 | @sssTBasicOffset{} | |
5664 | @end group | |
5665 | @end example | |
5666 | ||
5667 | The block may be surrounded by any kind of parenthesis characters. | |
5668 | @code{nil} is returned if the line doesn't start with a multiline | |
5669 | block, which makes the function usable in list expressions. | |
5670 | ||
5671 | @workswith Almost all syntactic symbols, but most useful on the | |
5672 | @code{-open} symbols. | |
5673 | @end defun | |
5674 | ||
5675 | @comment ------------------------------------------------------------ | |
5676 | ||
5677 | @defun c-lineup-runin-statements | |
5678 | @findex lineup-runin-statements (c-) | |
5679 | Line up statements for coding standards which place the first statement | |
5680 | in a block on the same line as the block opening brace@footnote{Run-in | |
5681 | style doesn't really work too well. You might need to write your own | |
65e7ca35 | 5682 | custom line-up functions to better support this style.}. E.g.: |
4009494e GM |
5683 | |
5684 | @example | |
5685 | @group | |
5686 | int main() | |
5687 | @{ puts ("Hello!"); | |
5688 | return 0; @hereFn{c-lineup-runin-statements} | |
5689 | @} | |
5690 | @end group | |
5691 | @end example | |
5692 | ||
5693 | If there is no statement after the opening brace to align with, | |
5694 | @code{nil} is returned. This makes the function usable in list | |
5695 | expressions. | |
5696 | ||
5697 | @workswith The @code{statement} syntactic symbol. | |
5698 | @end defun | |
5699 | ||
5700 | @comment ------------------------------------------------------------ | |
5701 | ||
5702 | @defun c-lineup-inexpr-block | |
5703 | @findex lineup-inexpr-block (c-) | |
5704 | This can be used with the in-expression block symbols to indent the | |
1df7defd | 5705 | whole block to the column where the construct is started. E.g., for Java |
4009494e GM |
5706 | anonymous classes, this lines up the class under the @samp{new} keyword, |
5707 | and in Pike it lines up the lambda function body under the @samp{lambda} | |
5708 | keyword. Returns @code{nil} if the block isn't part of such a | |
5709 | construct. | |
5710 | ||
5711 | @workswith @code{inlambda}, @code{inexpr-statement}, | |
5712 | @code{inexpr-class}. | |
5713 | @end defun | |
5714 | ||
5715 | @comment ------------------------------------------------------------ | |
5716 | ||
5717 | @defun c-lineup-after-whitesmith-blocks | |
5718 | @findex lineup-after-whitesmith-blocks (c-) | |
5719 | Compensate for Whitesmith style indentation of blocks. Due to the way | |
5720 | @ccmode{} calculates anchor positions for normal lines inside blocks, | |
5721 | this function is necessary for those lines to get correct Whitesmith | |
5722 | style indentation. Consider the following examples: | |
5723 | ||
5724 | @example | |
5725 | @group | |
5726 | int foo() | |
5727 | @{ | |
5728 | a; | |
5729 | x; @hereFn{c-lineup-after-whitesmith-blocks} | |
5730 | @end group | |
5731 | @end example | |
5732 | ||
5733 | @example | |
5734 | @group | |
5735 | int foo() | |
5736 | @{ | |
5737 | @{ | |
5738 | a; | |
5739 | @} | |
5740 | x; @hereFn{c-lineup-after-whitesmith-blocks} | |
5741 | @end group | |
5742 | @end example | |
5743 | ||
5744 | The fact that the line with @code{x} is preceded by a Whitesmith style | |
5745 | indented block in the latter case and not the first should not affect | |
5746 | its indentation. But since CC Mode in cases like this uses the | |
5747 | indentation of the preceding statement as anchor position, the @code{x} | |
5748 | would in the second case be indented too much if the offset for | |
5749 | @code{statement} was set simply to zero. | |
5750 | ||
5751 | This lineup function corrects for this situation by detecting if the | |
5752 | anchor position is at an open paren character. In that case, it instead | |
5753 | indents relative to the surrounding block just like | |
5754 | @code{c-lineup-whitesmith-in-block}. | |
5755 | ||
5756 | @workswith @code{brace-list-entry}, @code{brace-entry-open}, | |
5757 | @code{statement}, @code{arglist-cont}. | |
5758 | @end defun | |
5759 | ||
5760 | @comment ------------------------------------------------------------ | |
5761 | ||
5762 | @defun c-lineup-whitesmith-in-block | |
5763 | @findex lineup-whitesmith-in-block (c-) | |
5764 | Line up lines inside a block in Whitesmith style. It's done in a way | |
65e7ca35 | 5765 | that works both when the opening brace hangs and when it doesn't. E.g.: |
4009494e GM |
5766 | |
5767 | @example | |
5768 | @group | |
5769 | something | |
5770 | @{ | |
5771 | foo; @hereFn{c-lineup-whitesmith-in-block} | |
5772 | @} | |
5773 | @end group | |
5774 | @end example | |
5775 | ||
5776 | @noindent | |
5777 | and | |
5778 | ||
5779 | @example | |
5780 | @group | |
5781 | something @{ | |
5782 | foo; @hereFn{c-lineup-whitesmith-in-block} | |
5783 | @} | |
5784 | @sssTBasicOffset{} | |
5785 | @end group | |
5786 | @end example | |
5787 | ||
5788 | In the first case the indentation is kept unchanged, in the second | |
5789 | @code{c-basic-offset} is added. | |
5790 | ||
5791 | @workswith @code{defun-close}, @code{defun-block-intro}, | |
5792 | @code{inline-close}, @code{block-close}, @code{brace-list-close}, | |
5793 | @code{brace-list-intro}, @code{statement-block-intro}, | |
5794 | @code{arglist-intro}, @code{arglist-cont-nonempty}, | |
1df7defd | 5795 | @code{arglist-close}, and all @code{in*} symbols, e.g., @code{inclass} |
4009494e GM |
5796 | and @code{inextern-lang}. |
5797 | @end defun | |
5798 | ||
5799 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5800 | @node List Line-Up, Operator Line-Up, Brace/Paren Line-Up, Line-Up Functions | |
5801 | @comment node-name, next, previous, up | |
5802 | @subsection List Line-Up Functions | |
5803 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
5804 | ||
5805 | The line-up functions here calculate the indentation for lines which | |
5806 | form lists of items, usually separated by commas. | |
5807 | ||
5808 | The function @ref{c-lineup-arglist-close-under-paren}, which is mainly | |
5809 | for indenting a close parenthesis, is also useful for the lines | |
5810 | contained within parentheses. | |
5811 | ||
5812 | @defun c-lineup-arglist | |
5813 | @findex lineup-arglist (c-) | |
5814 | Line up the current argument line under the first argument. | |
5815 | ||
5816 | As a special case, if an argument on the same line as the open | |
5817 | parenthesis starts with a brace block opener, the indentation is | |
5818 | @code{c-basic-offset} only. This is intended as a ``DWIM'' measure in | |
65e7ca35 | 5819 | cases like macros that contain statement blocks, e.g.: |
4009494e GM |
5820 | |
5821 | @example | |
5822 | @group | |
5823 | A_VERY_LONG_MACRO_NAME (@{ | |
5824 | some (code, with + long, lines * in[it]); | |
5825 | @}); | |
5826 | @sssTBasicOffset{} | |
5827 | @end group | |
5828 | @end example | |
5829 | ||
5830 | This is motivated partly because it's more in line with how code | |
5831 | blocks are handled, and partly since it approximates the behavior of | |
5832 | earlier CC Mode versions, which due to inaccurate analysis tended to | |
5833 | indent such cases this way. | |
5834 | ||
5835 | @workswith @code{arglist-cont-nonempty}, @code{arglist-close}. | |
5836 | @end defun | |
5837 | ||
5838 | @comment ------------------------------------------------------------ | |
5839 | ||
5840 | @defun c-lineup-arglist-intro-after-paren | |
5841 | @findex lineup-arglist-intro-after-paren (c-) | |
5842 | Line up a line to just after the open paren of the surrounding paren or | |
5843 | brace block. | |
5844 | ||
5845 | @workswith @code{defun-block-intro}, @code{brace-list-intro}, | |
5846 | @code{statement-block-intro}, @code{statement-case-intro}, | |
5847 | @code{arglist-intro}. | |
5848 | @end defun | |
5849 | ||
5850 | @comment ------------------------------------------------------------ | |
5851 | ||
5852 | @defun c-lineup-multi-inher | |
5853 | @findex lineup-multi-inher (c-) | |
5854 | Line up the classes in C++ multiple inheritance clauses and member | |
65e7ca35 | 5855 | initializers under each other. E.g.: |
4009494e GM |
5856 | |
5857 | @example | |
5858 | @group | |
5859 | Foo::Foo (int a, int b): | |
5860 | Cyphr (a), | |
5861 | Bar (b) @hereFn{c-lineup-multi-inher} | |
5862 | @end group | |
5863 | @end example | |
5864 | ||
5865 | @noindent | |
5866 | and | |
5867 | ||
5868 | @example | |
5869 | @group | |
5870 | class Foo | |
5871 | : public Cyphr, | |
5872 | public Bar @hereFn{c-lineup-multi-inher} | |
5873 | @end group | |
5874 | @end example | |
5875 | ||
5876 | @noindent | |
5877 | and | |
5878 | ||
5879 | @example | |
5880 | @group | |
5881 | Foo::Foo (int a, int b) | |
5882 | : Cyphr (a) | |
5883 | , Bar (b) @hereFn{c-lineup-multi-inher} | |
5884 | @end group | |
5885 | @end example | |
5886 | ||
5887 | @workswith @code{inher-cont}, @code{member-init-cont}. | |
5888 | @end defun | |
5889 | ||
5890 | @comment ------------------------------------------------------------ | |
5891 | ||
5892 | @defun c-lineup-java-inher | |
5893 | @findex lineup-java-inher (c-) | |
5894 | Line up Java implements and extends declarations. If class names | |
5895 | follow on the same line as the @samp{implements}/@samp{extends} | |
5896 | keyword, they are lined up under each other. Otherwise, they are | |
5897 | indented by adding @code{c-basic-offset} to the column of the keyword. | |
65e7ca35 | 5898 | E.g.: |
4009494e GM |
5899 | |
5900 | @example | |
5901 | @group | |
5902 | class Foo | |
5903 | extends | |
5904 | Bar @hereFn{c-lineup-java-inher} | |
5905 | @sssTBasicOffset{} | |
5906 | @end group | |
5907 | @end example | |
5908 | ||
5909 | @noindent | |
5910 | and | |
5911 | ||
5912 | @example | |
5913 | @group | |
5914 | class Foo | |
5915 | extends Cyphr, | |
5916 | Bar @hereFn{c-lineup-java-inher} | |
5917 | @end group | |
5918 | @end example | |
5919 | ||
5920 | @workswith @code{inher-cont}. | |
5921 | @end defun | |
5922 | ||
5923 | @comment ------------------------------------------------------------ | |
5924 | ||
5925 | @defun c-lineup-java-throws | |
5926 | @findex lineup-java-throws (c-) | |
5927 | Line up Java throws declarations. If exception names follow on the | |
5928 | same line as the throws keyword, they are lined up under each other. | |
5929 | Otherwise, they are indented by adding @code{c-basic-offset} to the | |
5930 | column of the @samp{throws} keyword. The @samp{throws} keyword itself | |
5931 | is also indented by @code{c-basic-offset} from the function declaration | |
65e7ca35 | 5932 | start if it doesn't hang. E.g.: |
4009494e GM |
5933 | |
5934 | @example | |
5935 | @group | |
5936 | int foo() | |
5937 | throws @hereFn{c-lineup-java-throws} | |
5938 | Bar @hereFn{c-lineup-java-throws} | |
5939 | @sssTsssTBasicOffset{} | |
5940 | @end group | |
5941 | @end example | |
5942 | ||
5943 | @noindent | |
5944 | and | |
5945 | ||
5946 | @example | |
5947 | @group | |
5948 | int foo() throws Cyphr, | |
5949 | Bar, @hereFn{c-lineup-java-throws} | |
5950 | Vlod @hereFn{c-lineup-java-throws} | |
5951 | @end group | |
5952 | @end example | |
5953 | ||
5954 | @workswith @code{func-decl-cont}. | |
5955 | @end defun | |
5956 | ||
5957 | @comment ------------------------------------------------------------ | |
5958 | ||
5959 | @defun c-lineup-template-args | |
5960 | @findex lineup-template-args (c-) | |
5961 | Line up the arguments of a template argument list under each other, but | |
5962 | only in the case where the first argument is on the same line as the | |
5963 | opening @samp{<}. | |
5964 | ||
5965 | To allow this function to be used in a list expression, @code{nil} is | |
5966 | returned if there's no template argument on the first line. | |
5967 | ||
5968 | @workswith @code{template-args-cont}. | |
5969 | @end defun | |
5970 | ||
5971 | @comment ------------------------------------------------------------ | |
5972 | ||
5973 | @defun c-lineup-ObjC-method-call | |
5974 | @findex lineup-ObjC-method-call (c-) | |
5975 | For Objective-C code, line up selector args as Emacs Lisp mode does | |
5976 | with function args: go to the position right after the message receiver, | |
5977 | and if you are at the end of the line, indent the current line | |
5978 | c-basic-offset columns from the opening bracket; otherwise you are | |
5979 | looking at the first character of the first method call argument, so | |
5980 | lineup the current line with it. | |
5981 | ||
5982 | @workswith @code{objc-method-call-cont}. | |
5983 | @end defun | |
5984 | ||
5985 | @comment ------------------------------------------------------------ | |
5986 | ||
5987 | @defun c-lineup-ObjC-method-args | |
5988 | @findex lineup-ObjC-method-args (c-) | |
5989 | For Objective-C code, line up the colons that separate args. The colon | |
5990 | on the current line is aligned with the one on the first line. | |
5991 | ||
5992 | @workswith @code{objc-method-args-cont}. | |
5993 | @end defun | |
5994 | ||
5995 | @comment ------------------------------------------------------------ | |
5996 | ||
5997 | @defun c-lineup-ObjC-method-args-2 | |
5998 | @findex lineup-ObjC-method-args-2 (c-) | |
5999 | Similar to @code{c-lineup-ObjC-method-args} but lines up the colon on | |
6000 | the current line with the colon on the previous line. | |
6001 | ||
6002 | @workswith @code{objc-method-args-cont}. | |
6003 | @end defun | |
6004 | ||
6005 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6006 | @node Operator Line-Up, Comment Line-Up, List Line-Up, Line-Up Functions | |
6007 | @comment node-name, next, previous, up | |
6008 | @subsection Operator Line-Up Functions | |
6009 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6010 | ||
6011 | The line-up functions here calculate the indentation for lines which | |
6012 | start with an operator, by lining it up with something on the previous | |
6013 | line. | |
6014 | ||
6015 | @defun c-lineup-argcont | |
6016 | @findex lineup-argcont (c-) | |
65e7ca35 | 6017 | Line up a continued argument. E.g.: |
4009494e GM |
6018 | |
6019 | @example | |
6020 | @group | |
6021 | foo (xyz, aaa + bbb + ccc | |
6022 | + ddd + eee + fff); @hereFn{c-lineup-argcont} | |
6023 | @end group | |
6024 | @end example | |
6025 | ||
6026 | Only continuation lines like this are touched, @code{nil} is returned on | |
6027 | lines which are the start of an argument. | |
6028 | ||
2f0c93d1 | 6029 | Within a gcc @code{asm} block, @code{:} is recognized as an argument |
4009494e GM |
6030 | separator, but of course only between operand specifications, not in the |
6031 | expressions for the operands. | |
6032 | ||
6033 | @workswith @code{arglist-cont}, @code{arglist-cont-nonempty}. | |
6034 | @end defun | |
6035 | ||
6036 | @comment ------------------------------------------------------------ | |
6037 | ||
6038 | @defun c-lineup-arglist-operators | |
6039 | @findex lineup-arglist-operators (c-) | |
6040 | Line up lines starting with an infix operator under the open paren. | |
6041 | Return @code{nil} on lines that don't start with an operator, to leave | |
6042 | those cases to other line-up functions. Example: | |
6043 | ||
6044 | @example | |
6045 | @group | |
6046 | if ( x < 10 | |
6047 | || at_limit (x, @hereFn{c-lineup-arglist-operators} | |
6048 | list) @hereFn{c-lineup-arglist-operators@r{ returns nil}} | |
6049 | ) | |
6050 | @end group | |
6051 | @end example | |
6052 | ||
6053 | Since this function doesn't do anything for lines without an infix | |
6054 | operator you typically want to use it together with some other lineup | |
1df7defd | 6055 | settings, e.g., as follows (the @code{arglist-close} setting is just a |
4009494e GM |
6056 | suggestion to get a consistent style): |
6057 | ||
6058 | @example | |
6059 | (c-set-offset 'arglist-cont | |
6060 | '(c-lineup-arglist-operators 0)) | |
6061 | (c-set-offset 'arglist-cont-nonempty | |
6062 | '(c-lineup-arglist-operators c-lineup-arglist)) | |
6063 | (c-set-offset 'arglist-close | |
6064 | '(c-lineup-arglist-close-under-paren)) | |
6065 | @end example | |
6066 | ||
6067 | @workswith @code{arglist-cont}, @code{arglist-cont-nonempty}. | |
6068 | @end defun | |
6069 | ||
6070 | @comment ------------------------------------------------------------ | |
6071 | ||
6072 | @defun c-lineup-assignments | |
6073 | @findex lineup-assignments (c-) | |
6074 | Line up the current line after the assignment operator on the first line | |
6075 | in the statement. If there isn't any, return nil to allow stacking with | |
6076 | other line-up functions. If the current line contains an assignment | |
6077 | operator too, try to align it with the first one. | |
6078 | ||
6079 | @workswith @code{topmost-intro-cont}, @code{statement-cont}, | |
6080 | @code{arglist-cont}, @code{arglist-cont-nonempty}. | |
6081 | ||
6082 | @end defun | |
6083 | ||
6084 | @comment ------------------------------------------------------------ | |
6085 | ||
6086 | @defun c-lineup-math | |
6087 | @findex lineup-math (c-) | |
6088 | Like @code{c-lineup-assignments} but indent with @code{c-basic-offset} | |
1df7defd | 6089 | if no assignment operator was found on the first line. I.e., this |
4009494e GM |
6090 | function is the same as specifying a list @code{(c-lineup-assignments |
6091 | +)}. It's provided for compatibility with old configurations. | |
6092 | ||
6093 | @workswith @code{topmost-intro-cont}, @code{statement-cont}, | |
6094 | @code{arglist-cont}, @code{arglist-cont-nonempty}. | |
6095 | @end defun | |
6096 | ||
6097 | @comment ------------------------------------------------------------ | |
6098 | ||
6099 | @defun c-lineup-cascaded-calls | |
6100 | @findex lineup-cascaded-calls (c-) | |
6101 | Line up ``cascaded calls'' under each other. If the line begins with | |
6102 | @code{->} or @code{.} and the preceding line ends with one or more | |
6103 | function calls preceded by the same token, then the arrow is lined up | |
65e7ca35 | 6104 | with the first of those tokens. E.g.: |
4009494e GM |
6105 | |
6106 | @example | |
6107 | @group | |
6108 | r = proc->add(17)->add(18) | |
6109 | ->add(19) + @hereFn{c-lineup-cascaded-calls} | |
6110 | offset; @hereFn{c-lineup-cascaded-calls@r{ (inactive)}} | |
6111 | @end group | |
6112 | @end example | |
6113 | ||
6114 | In any other situation @code{nil} is returned to allow use in list | |
6115 | expressions. | |
6116 | ||
6117 | @workswith @code{topmost-intro-cont}, @code{statement-cont}, | |
6118 | @code{arglist-cont}, @code{arglist-cont-nonempty}. | |
6119 | @end defun | |
6120 | ||
6121 | @comment ------------------------------------------------------------ | |
6122 | ||
6123 | @defun c-lineup-streamop | |
6124 | @findex lineup-streamop (c-) | |
1df7defd | 6125 | Line up C++ stream operators (i.e., @samp{<<} and @samp{>>}). |
4009494e GM |
6126 | |
6127 | @workswith @code{stream-op}. | |
6128 | @end defun | |
6129 | ||
6130 | @comment ------------------------------------------------------------ | |
6131 | ||
6132 | @defun c-lineup-string-cont | |
6133 | @findex lineup-string-cont (c-) | |
6134 | Line up a continued string under the one it continues. A continued | |
6135 | string in this sense is where a string literal follows directly after | |
65e7ca35 | 6136 | another one. E.g.: |
4009494e GM |
6137 | |
6138 | @example | |
6139 | @group | |
6140 | result = prefix + "A message " | |
6141 | "string."; @hereFn{c-lineup-string-cont} | |
6142 | @end group | |
6143 | @end example | |
6144 | ||
6145 | @code{nil} is returned in other situations, to allow stacking with other | |
6146 | lineup functions. | |
6147 | ||
6148 | @workswith @code{topmost-intro-cont}, @code{statement-cont}, | |
6149 | @code{arglist-cont}, @code{arglist-cont-nonempty}. | |
6150 | @end defun | |
6151 | ||
6152 | ||
6153 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6154 | @node Comment Line-Up, Misc Line-Up, Operator Line-Up, Line-Up Functions | |
6155 | @comment node-name, next, previous, up | |
6156 | @subsection Comment Line-Up Functions | |
6157 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6158 | ||
6159 | The lineup functions here calculate the indentation for several types | |
6160 | of comment structure. | |
6161 | ||
6162 | @defun c-lineup-C-comments | |
6163 | @findex lineup-C-comments (c-) | |
6164 | Line up C block comment continuation lines. Various heuristics are used | |
6165 | to handle most of the common comment styles. Some examples: | |
6166 | ||
6167 | @example | |
6168 | @group | |
6169 | /* /** /* | |
6170 | * text * text text | |
6171 | */ */ */ | |
6172 | @end group | |
6173 | @end example | |
6174 | ||
6175 | @example | |
6176 | @group | |
6177 | /* text /* /** | |
6178 | text ** text ** text | |
6179 | */ */ */ | |
6180 | @end group | |
6181 | @end example | |
6182 | ||
6183 | @example | |
6184 | @group | |
6185 | /************************************************** | |
6186 | * text | |
6187 | *************************************************/ | |
6188 | @end group | |
6189 | @end example | |
6190 | ||
6191 | @vindex comment-start-skip | |
6192 | @example | |
6193 | @group | |
6194 | /************************************************** | |
6195 | Free form text comments: | |
6196 | In comments with a long delimiter line at the | |
6197 | start, the indentation is kept unchanged for lines | |
6198 | that start with an empty comment line prefix. The | |
6199 | delimiter line is whatever matches the | |
6200 | @code{comment-start-skip} regexp. | |
6201 | **************************************************/ | |
6202 | @end group | |
6203 | @end example | |
6204 | ||
6205 | The style variable @code{c-comment-prefix-regexp} is used to recognize | |
1df7defd | 6206 | the comment line prefix, e.g., the @samp{*} that usually starts every |
4009494e GM |
6207 | line inside a comment. |
6208 | ||
6209 | @workswith The @code{c} syntactic symbol. | |
6210 | @end defun | |
6211 | ||
6212 | @comment ------------------------------------------------------------ | |
6213 | ||
6214 | @defun c-lineup-comment | |
6215 | @findex lineup-comment (c-) | |
6216 | Line up a comment-only line according to the style variable | |
6217 | @code{c-comment-only-line-offset}. If the comment is lined up with a | |
6218 | comment starter on the previous line, that alignment is preserved. | |
6219 | ||
6220 | @defopt c-comment-only-line-offset | |
6221 | @vindex comment-only-line-offset (c-) | |
6222 | This style variable specifies the extra offset for the line. It can | |
6223 | contain an integer or a cons cell of the form | |
6224 | ||
6225 | @example | |
6226 | (@r{@var{non-anchored-offset}} . @r{@var{anchored-offset}}) | |
6227 | @end example | |
6228 | ||
6229 | @noindent | |
6230 | where @var{non-anchored-offset} is the amount of offset given to | |
6231 | non-column-zero anchored lines, and @var{anchored-offset} is the amount | |
6232 | of offset to give column-zero anchored lines. Just an integer as value | |
6233 | is equivalent to @code{(@r{@var{value}} . -1000)}. | |
6234 | @end defopt | |
6235 | ||
6236 | @workswith @code{comment-intro}. | |
6237 | @end defun | |
6238 | ||
6239 | @comment ------------------------------------------------------------ | |
6240 | ||
6241 | @defun c-lineup-knr-region-comment | |
6242 | @findex lineup-knr-region-comment (c-) | |
6243 | Line up a comment in the ``K&R region'' with the declaration. That is | |
6244 | the region between the function or class header and the beginning of the | |
65e7ca35 | 6245 | block. E.g.: |
4009494e GM |
6246 | |
6247 | @example | |
6248 | @group | |
6249 | int main() | |
6250 | /* Called at startup. */ @hereFn{c-lineup-knr-region-comment} | |
6251 | @{ | |
6252 | return 0; | |
6253 | @} | |
6254 | @end group | |
6255 | @end example | |
6256 | ||
6257 | Return @code{nil} if called in any other situation, to be useful in list | |
6258 | expressions. | |
6259 | ||
6260 | @workswith @code{comment-intro}. | |
6261 | @end defun | |
6262 | ||
6263 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6264 | @node Misc Line-Up, , Comment Line-Up, Line-Up Functions | |
6265 | @comment node-name, next, previous, up | |
6266 | @subsection Miscellaneous Line-Up Functions | |
6267 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6268 | ||
6269 | The line-up functions here are the odds and ends which didn't fit into | |
6270 | any earlier category. | |
6271 | ||
6272 | @defun c-lineup-dont-change | |
6273 | @findex lineup-dont-change (c-) | |
6274 | This lineup function makes the line stay at whatever indentation it | |
6275 | already has; think of it as an identity function for lineups. | |
6276 | ||
6277 | @workswith Any syntactic symbol. | |
6278 | @end defun | |
6279 | ||
6280 | @comment ------------------------------------------------------------ | |
6281 | ||
6282 | @defun c-lineup-cpp-define | |
6283 | @findex lineup-cpp-define (c-) | |
6284 | Line up macro continuation lines according to the indentation of the | |
65e7ca35 | 6285 | construct preceding the macro. E.g.: |
4009494e GM |
6286 | |
6287 | @example | |
6288 | @group | |
6289 | const char msg[] = @hereFn{@r{The beginning of the preceding construct.}} | |
6290 | \"Some text.\"; | |
6291 | ||
6292 | #define X(A, B) \ | |
6293 | do @{ \ @hereFn{c-lineup-cpp-define} | |
6294 | printf (A, B); \ | |
6295 | @} while (0) | |
6296 | @end group | |
6297 | @end example | |
6298 | ||
6299 | @noindent | |
6300 | and: | |
6301 | ||
6302 | @example | |
6303 | @group | |
6304 | int dribble() @{ | |
6305 | if (!running) @hereFn{@r{The beginning of the preceding construct.}} | |
6306 | error(\"Not running!\"); | |
6307 | ||
6308 | #define X(A, B) \ | |
6309 | do @{ \ @hereFn{c-lineup-cpp-define} | |
6310 | printf (A, B); \ | |
6311 | @} while (0) | |
6312 | @end group | |
6313 | @end example | |
6314 | ||
6315 | If @code{c-syntactic-indentation-in-macros} is non-@code{nil}, the | |
6316 | function returns the relative indentation to the macro start line to | |
1df7defd | 6317 | allow accumulation with other offsets. E.g., in the following cases, |
4009494e GM |
6318 | @code{cpp-define-intro} is combined with the |
6319 | @code{statement-block-intro} that comes from the @samp{do @{} that hangs | |
6320 | on the @samp{#define} line: | |
6321 | ||
6322 | @example | |
6323 | @group | |
6324 | const char msg[] = | |
6325 | \"Some text.\"; | |
6326 | ||
6327 | #define X(A, B) do @{ \ | |
6328 | printf (A, B); \ @hereFn{c-lineup-cpp-define} | |
6329 | this->refs++; \ | |
6330 | @} while (0) @hereFn{c-lineup-cpp-define} | |
6331 | @end group | |
6332 | @end example | |
6333 | ||
6334 | @noindent | |
6335 | and: | |
6336 | ||
6337 | @example | |
6338 | @group | |
6339 | int dribble() @{ | |
6340 | if (!running) | |
6341 | error(\"Not running!\"); | |
6342 | ||
6343 | #define X(A, B) do @{ \ | |
6344 | printf (A, B); \ @hereFn{c-lineup-cpp-define} | |
6345 | this->refs++; \ | |
6346 | @} while (0) @hereFn{c-lineup-cpp-define} | |
6347 | @end group | |
6348 | @end example | |
6349 | ||
6350 | The relative indentation returned by @code{c-lineup-cpp-define} is zero | |
6351 | and two, respectively, on the two lines in each of these examples. They | |
6352 | are then added to the two column indentation that | |
6353 | @code{statement-block-intro} gives in both cases here. | |
6354 | ||
6355 | If the relative indentation is zero, then @code{nil} is returned | |
6356 | instead. That is useful in a list expression to specify the default | |
6357 | indentation on the top level. | |
6358 | ||
6359 | If @code{c-syntactic-indentation-in-macros} is @code{nil} then this | |
6360 | function keeps the current indentation, except for empty lines (ignoring | |
6361 | the ending backslash) where it takes the indentation from the closest | |
6362 | preceding nonempty line in the macro. If there's no such line in the | |
6363 | macro then the indentation is taken from the construct preceding it, as | |
6364 | described above. | |
6365 | ||
6366 | @workswith @code{cpp-define-intro}. | |
6367 | @end defun | |
6368 | ||
6369 | @comment ------------------------------------------------------------ | |
6370 | ||
6371 | @defun c-lineup-gcc-asm-reg | |
6372 | @findex lineup-gcc-asm-reg (c-) | |
6373 | Line up a gcc asm register under one on a previous line. | |
6374 | ||
6375 | @example | |
6376 | @group | |
6377 | asm ("foo %1, %0\n" | |
6378 | "bar %0, %1" | |
6379 | : "=r" (w), | |
6380 | "=r" (x) | |
6381 | : "0" (y), | |
6382 | "1" (z)); | |
6383 | @end group | |
6384 | @end example | |
6385 | ||
6386 | The @samp{x} line is aligned to the text after the @samp{:} on the | |
6387 | @samp{w} line, and similarly @samp{z} under @samp{y}. | |
6388 | ||
6389 | This is done only in an @samp{asm} or @samp{__asm__} block, and only to | |
6390 | those lines mentioned. Anywhere else @code{nil} is returned. The usual | |
6391 | arrangement is to have this routine as an extra feature at the start of | |
1df7defd | 6392 | arglist lineups, e.g.: |
4009494e GM |
6393 | |
6394 | @example | |
6395 | (c-lineup-gcc-asm-reg c-lineup-arglist) | |
6396 | @end example | |
6397 | ||
6398 | @workswith @code{arglist-cont}, @code{arglist-cont-nonempty}. | |
6399 | @end defun | |
6400 | ||
6401 | @comment ------------------------------------------------------------ | |
6402 | ||
6403 | @defun c-lineup-topmost-intro-cont | |
6404 | @findex lineup-topmost-intro-cont (c-) | |
6405 | Line up declaration continuation lines zero or one indentation | |
6406 | step@footnote{This function is mainly provided to mimic the behavior of | |
6407 | CC Mode 5.28 and earlier where this case wasn't handled consistently so | |
6408 | that those lines could be analyzed as either topmost-intro-cont or | |
6409 | statement-cont. It's used for @code{topmost-intro-cont} by default, but | |
6410 | you might consider using @code{+} instead.}. For lines preceding a | |
6411 | definition, zero is used. For other lines, @code{c-basic-offset} is | |
65e7ca35 | 6412 | added to the indentation. E.g.: |
4009494e GM |
6413 | |
6414 | @example | |
6415 | @group | |
6416 | int | |
6417 | neg (int i) @hereFn{c-lineup-topmost-intro-cont} | |
6418 | @{ | |
6419 | return -i; | |
6420 | @} | |
6421 | @end group | |
6422 | @end example | |
6423 | ||
6424 | @noindent | |
6425 | and | |
6426 | ||
6427 | @example | |
6428 | @group | |
6429 | struct | |
6430 | larch @hereFn{c-lineup-topmost-intro-cont} | |
6431 | @{ | |
6432 | double height; | |
6433 | @} | |
6434 | the_larch, @hereFn{c-lineup-topmost-intro-cont} | |
6435 | another_larch; @hereFn{c-lineup-topmost-intro-cont} | |
6436 | @sssTBasicOffset{} | |
6437 | @end group | |
6438 | @end example | |
6439 | ||
6440 | @noindent | |
6441 | and | |
6442 | ||
6443 | @example | |
6444 | @group | |
6445 | struct larch | |
6446 | the_larch, @hereFn{c-lineup-topmost-intro-cont} | |
6447 | another_larch; @hereFn{c-lineup-topmost-intro-cont} | |
6448 | @end group | |
6449 | @end example | |
6450 | ||
6451 | @workswith @code{topmost-intro-cont}. | |
6452 | @end defun | |
6453 | ||
6454 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6455 | @node Custom Line-Up, Other Indentation, Line-Up Functions, Customizing Indentation | |
6456 | @comment node-name, next, previous, up | |
6457 | @section Custom Line-Up Functions | |
6458 | @cindex customization, indentation functions | |
6459 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6460 | ||
6461 | The most flexible way to customize indentation is by writing custom | |
6462 | line-up functions, and associating them with specific syntactic | |
6463 | symbols (@pxref{c-offsets-alist}). Depending on the effect you want, | |
6464 | it might be better to write a @code{c-special-indent-hook} function | |
6465 | rather than a line-up function (@pxref{Other Indentation}). | |
6466 | ||
6467 | @ccmode{} comes with an extensive set of predefined line-up functions, | |
6468 | not all of which are used by the default styles. So there's a good | |
6469 | chance the function you want already exists. @xref{Line-Up | |
6470 | Functions}, for a list of them. If you write your own line-up | |
6471 | function, it's probably a good idea to start working from one of these | |
6472 | predefined functions, which can be found in the file | |
6473 | @file{cc-align.el}. If you have written a line-up function that you | |
6474 | think is generally useful, you're very welcome to contribute it; | |
6475 | please contact @email{bug-cc-mode@@gnu.org}. | |
6476 | ||
6477 | Line-up functions are passed a single argument, the syntactic | |
33d1e2f5 AM |
6478 | element (see below). At the time of the call, point will be somewhere |
6479 | on the line being indented. The return value is a | |
6480 | @code{c-offsets-alist} offset specification: for example, an integer, | |
6481 | a symbol such as @code{+}, a vector, @code{nil}@footnote{Returning | |
6482 | @code{nil} is useful when the offset specification for a syntactic | |
6483 | element is a list containing the line-up function | |
6484 | (@pxref{c-offsets-alist}).}, or even another line-up function. Full | |
6485 | details of these are in @ref{c-offsets-alist}. | |
4009494e GM |
6486 | |
6487 | Line-up functions must not move point or change the content of the | |
6488 | buffer (except temporarily). They are however allowed to do | |
1df7defd | 6489 | @dfn{hidden buffer changes}, i.e., setting text properties for caching |
4009494e GM |
6490 | purposes etc. Buffer undo recording is disabled while they run. |
6491 | ||
6492 | The syntactic element passed as the parameter to a line-up function is | |
6493 | a cons cell of the form | |
6494 | ||
6495 | @example | |
6496 | (@r{@var{syntactic-symbol}} . @r{@var{anchor-position}}) | |
6497 | @end example | |
6498 | ||
6499 | @noindent | |
6500 | @c FIXME!!! The following sentence might be better omitted, since the | |
6501 | @c information is in the cross reference "Syntactic Analysis". 2005/10/2. | |
6502 | where @var{syntactic-symbol} is the symbol that the function was | |
6503 | called for, and @var{anchor-position} is the anchor position (if any) | |
6504 | for the construct that triggered the syntactic symbol | |
6505 | (@pxref{Syntactic Analysis}). This cons cell is how the syntactic | |
6506 | element of a line used to be represented in @ccmode{} 5.28 and | |
6507 | earlier. Line-up functions are still passed this cons cell, so as to | |
6508 | preserve compatibility with older configurations. In the future, we | |
6509 | may decide to convert to using the full list format---you can prepare | |
6510 | your setup for this by using the access functions | |
65e7ca35 | 6511 | (@code{c-langelem-sym}, etc.)@: described below. |
4009494e GM |
6512 | |
6513 | @vindex c-syntactic-element | |
6514 | @vindex syntactic-element (c-) | |
6515 | @vindex c-syntactic-context | |
6516 | @vindex syntactic-context (c-) | |
1df7defd | 6517 | Some syntactic symbols, e.g., @code{arglist-cont-nonempty}, have more |
f99f1641 | 6518 | info in the syntactic element: typically other positions that can be |
4009494e GM |
6519 | interesting besides the anchor position. That info can't be accessed |
6520 | through the passed argument, which is a cons cell. Instead, you can | |
6521 | get this information from the variable @code{c-syntactic-element}, | |
6522 | which is dynamically bound to the complete syntactic element. The | |
f99f1641 | 6523 | variable @code{c-syntactic-context} might also be useful: it gets |
4009494e GM |
6524 | dynamically bound to the complete syntactic context. @xref{Custom |
6525 | Braces}. | |
6526 | ||
6527 | @ccmode{} provides a few functions to access parts of syntactic | |
6528 | elements in a more abstract way. Besides making the code easier to | |
6529 | read, they also hide the difference between the old cons cell form | |
6530 | used in the line-up function argument and the new list form used in | |
6531 | @code{c-syntactic-element} and everywhere else. The functions are: | |
6532 | ||
6533 | @defun c-langelem-sym langelem | |
6534 | @findex langelem-sym (c-) | |
6535 | Return the syntactic symbol in @var{langelem}. | |
6536 | @end defun | |
6537 | ||
6538 | @defun c-langelem-pos langelem | |
6539 | @findex langelem-pos (c-) | |
6540 | Return the anchor position in @var{langelem}, or nil if there is none. | |
6541 | @end defun | |
6542 | ||
6543 | @defun c-langelem-col langelem &optional preserve-point | |
6544 | @findex langelem-col (c-) | |
6545 | Return the column of the anchor position in @var{langelem}. Also move | |
6546 | the point to that position unless @var{preserve-point} is | |
6547 | non-@code{nil}. | |
6548 | @end defun | |
6549 | ||
6550 | @defun c-langelem-2nd-pos langelem | |
6551 | @findex langelem-2nd-pos (c-) | |
6552 | Return the secondary position in @var{langelem}, or @code{nil} if there | |
6553 | is none. | |
6554 | ||
6555 | Note that the return value of this function is always @code{nil} if | |
6556 | @var{langelem} is in the old cons cell form. Thus this function is | |
6557 | only meaningful when used on syntactic elements taken from | |
6558 | @code{c-syntactic-element} or @code{c-syntactic-context}. | |
6559 | @end defun | |
6560 | ||
6561 | Custom line-up functions can be as simple or as complex as you like, and | |
6562 | any syntactic symbol that appears in @code{c-offsets-alist} can have a | |
6563 | custom line-up function associated with it. | |
6564 | ||
6565 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6566 | @node Other Indentation, , Custom Line-Up, Customizing Indentation | |
6567 | @comment node-name, next, previous, up | |
6568 | @section Other Special Indentations | |
6569 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6570 | ||
536610a4 AM |
6571 | To configure macros which you invoke without a terminating @samp{;}, |
6572 | see @xref{Macros with ;}. | |
6573 | ||
4009494e GM |
6574 | Here are the remaining odds and ends regarding indentation: |
6575 | ||
6576 | @defopt c-label-minimum-indentation | |
6577 | @vindex label-minimum-indentation (c-) | |
6578 | In @samp{gnu} style (@pxref{Built-in Styles}), a minimum indentation is | |
6579 | imposed on lines inside code blocks. This minimum indentation is | |
6580 | controlled by this style variable. The default value is 1. | |
6581 | ||
6582 | @findex c-gnu-impose-minimum | |
6583 | @findex gnu-impose-minimum (c-) | |
6584 | It's the function @code{c-gnu-impose-minimum} that enforces this minimum | |
6585 | indentation. It must be present on @code{c-special-indent-hook} to | |
6586 | work. | |
6587 | @end defopt | |
6588 | ||
6589 | @defopt c-special-indent-hook | |
6590 | @vindex special-indent-hook (c-) | |
6591 | This style variable is a standard hook variable that is called after | |
6592 | every line is indented by @ccmode{}. It is called only if | |
6593 | @code{c-syntactic-indentation} is non-@code{nil} (which it is by | |
6594 | default (@pxref{Indentation Engine Basics})). You can put a function | |
6595 | on this hook to do any special indentation or ad hoc line adjustments | |
6596 | your style dictates, such as adding extra indentation to constructors | |
6597 | or destructor declarations in a class definition, etc. Sometimes it | |
6598 | is better to write a custom Line-up Function instead (@pxref{Custom | |
6599 | Line-Up}). | |
6600 | ||
6601 | When the indentation engine calls this hook, the variable | |
6602 | @code{c-syntactic-context} is bound to the current syntactic context | |
1df7defd | 6603 | (i.e., what you would get by typing @kbd{C-c C-s} on the source line. |
4009494e | 6604 | @xref{Custom Braces}.). Note that you should not change point or mark |
1df7defd | 6605 | inside a @code{c-special-indent-hook} function, i.e., you'll probably |
4009494e GM |
6606 | want to wrap your function in a @code{save-excursion}@footnote{The |
6607 | numerical value returned by @code{point} will change if you change the | |
6608 | indentation of the line within a @code{save-excursion} form, but point | |
6609 | itself will still be over the same piece of text.}. | |
6610 | ||
6611 | Setting @code{c-special-indent-hook} in style definitions is handled | |
6612 | slightly differently from other variables---A style can only add | |
6613 | functions to this hook, not remove them. @xref{Style Variables}. | |
6614 | @end defopt | |
6615 | ||
6616 | ||
6617 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6618 | @node Custom Macros, Odds and Ends, Customizing Indentation, Top | |
6619 | @comment node-name, next, previous, up | |
6620 | @chapter Customizing Macros | |
6621 | @cindex macros | |
6622 | @cindex preprocessor directives | |
6623 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6624 | ||
536610a4 AM |
6625 | Preprocessor macros in C, C++, and Objective C (introduced by |
6626 | @code{#define}) have a syntax different from the main language---for | |
6627 | example, a macro declaration is not terminated by a semicolon, and if | |
6628 | it is more than a line long, line breaks in it must be escaped with | |
6629 | backslashes. @ccmode{} has some commands to manipulate these, see | |
6630 | @ref{Macro Backslashes}. | |
6631 | ||
4009494e | 6632 | Normally, the lines in a multi-line macro are indented relative to |
a1bf7841 | 6633 | each other as though they were code. You can suppress this behavior |
4009494e GM |
6634 | by setting the following user option: |
6635 | ||
6636 | @defopt c-syntactic-indentation-in-macros | |
6637 | @vindex syntactic-indentation-in-macros (c-) | |
6638 | Enable syntactic analysis inside macros, which is the default. If this | |
6639 | is @code{nil}, all lines inside macro definitions are analyzed as | |
6640 | @code{cpp-macro-cont}. | |
6641 | @end defopt | |
6642 | ||
536610a4 AM |
6643 | Because a macro can expand into anything at all, near where one is |
6644 | invoked @ccmode{} can only indent and fontify code heuristically. | |
6645 | Sometimes it gets it wrong. Usually you should try to design your | |
6646 | macros so that they ''look like ordinary code'' when you invoke them. | |
6647 | However, one situation is so common that @ccmode{} handles it | |
6648 | specially: that is when certain macros needn't (or mustn't) be | |
6649 | followed by a @samp{;}. You need to configure @ccmode{} to handle | |
6650 | these macros properly, see @ref{Macros with ;}. | |
6651 | ||
6652 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6653 | @menu | |
91af3942 PE |
6654 | * Macro Backslashes:: |
6655 | * Macros with ;:: | |
536610a4 AM |
6656 | @end menu |
6657 | ||
6658 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6659 | @node Macro Backslashes, Macros with ;, Custom Macros, Custom Macros | |
6660 | @comment node-name, next, previous, up | |
6661 | @section Customizing Macro Backslashes | |
b207a4ec | 6662 | @cindex @code{#define} |
536610a4 AM |
6663 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
6664 | ||
4009494e GM |
6665 | @ccmode{} provides some tools to help keep the line continuation |
6666 | backslashes in macros neat and tidy. Their precise action is | |
6667 | customized with these variables: | |
6668 | ||
6669 | @defopt c-backslash-column | |
6670 | @vindex backslash-column (c-) | |
6671 | @defoptx c-backslash-max-column | |
6672 | @vindex backslash-max-column (c-) | |
6673 | These variables control the alignment columns for line continuation | |
6674 | backslashes in multiline macros. They are used by the functions that | |
6675 | automatically insert or align such backslashes, | |
1df7defd | 6676 | e.g., @code{c-backslash-region} and @code{c-context-line-break}. |
4009494e GM |
6677 | |
6678 | @code{c-backslash-column} specifies the minimum column for the | |
6679 | backslashes. If any line in the macro goes past this column, then the | |
1df7defd | 6680 | next tab stop (i.e., next multiple of @code{tab-width}) in that line is |
4009494e GM |
6681 | used as the alignment column for all the backslashes, so that they |
6682 | remain in a single column. However, if any lines go past | |
6683 | @code{c-backslash-max-column} then the backslashes in the rest of the | |
6684 | macro will be kept at that column, so that the lines which are too | |
6685 | long ``stick out'' instead. | |
6686 | ||
6687 | Don't ever set these variables to @code{nil}. If you want to disable | |
6688 | the automatic alignment of backslashes, use | |
6689 | @code{c-auto-align-backslashes}. | |
6690 | @end defopt | |
6691 | ||
6692 | @defopt c-auto-align-backslashes | |
6693 | @vindex auto-align-backslashes (c-) | |
6694 | Align automatically inserted line continuation backslashes if | |
6695 | non-@code{nil}. When line continuation backslashes are inserted | |
1df7defd | 6696 | automatically for line breaks in multiline macros, e.g., by |
4009494e GM |
6697 | @code{c-context-line-break}, they are aligned with the other |
6698 | backslashes in the same macro if this flag is set. | |
6699 | ||
6700 | If @code{c-auto-align-backslashes} is @code{nil}, automatically | |
6701 | inserted backslashes are preceded by a single space, and backslashes | |
6702 | get aligned only when you explicitly invoke the command | |
6703 | @code{c-backslash-region} (@kbd{C-c C-\}). | |
6704 | @end defopt | |
6705 | ||
536610a4 AM |
6706 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
6707 | @node Macros with ;, , Macro Backslashes, Custom Macros | |
6708 | @comment node-name, next, previous, up | |
6709 | @section Macros with semicolons | |
6710 | @cindex macros with semicolons | |
6711 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6712 | Macros which needn't (or mustn't) be followed by a semicolon when you | |
6713 | invoke them, @dfn{macros with semicolons}, are very common. These can | |
6714 | cause @ccmode{} to parse the next line wrongly as a | |
6715 | @code{statement-cont} (@pxref{Function Symbols}) and thus mis-indent | |
6716 | it. | |
6717 | ||
6718 | You can prevent this by specifying which macros have semicolons. It | |
6719 | doesn't matter whether or not such a macro has a parameter list: | |
6720 | ||
6721 | @defopt c-macro-names-with-semicolon | |
6722 | @vindex macro-names-with-semicolon (c-) | |
6723 | This buffer-local variable specifies which macros have semicolons. | |
6724 | After setting its value, you need to call | |
6725 | @code{c-make-macro-with-semi-re} for it to take effect. It should be | |
6726 | set to one of these values: | |
6727 | ||
6728 | @table @asis | |
6729 | @item nil | |
6730 | There are no macros with semicolons. | |
6731 | @item a list of strings | |
6732 | Each string is the name of a macro with a semicolon. Only valid | |
6733 | @code{#define} names are allowed here. For example, to set the | |
6734 | default value, you could write the following into your @file{.emacs}: | |
6735 | ||
6736 | @example | |
6737 | (setq c-macro-names-with-semicolon | |
6738 | '("Q_OBJECT" "Q_PROPERTY" "Q_DECLARE" "Q_ENUMS")) | |
6739 | @end example | |
6740 | ||
6741 | @item a regular expression | |
6742 | This matches each symbol which is a macro with a semicolon. It must | |
6743 | not match any string which isn't a valid @code{#define} name. For | |
6744 | example: | |
6745 | ||
6746 | @example | |
6747 | (setq c-macro-names-with-semicolon | |
6748 | "\\<\\(CLEAN_UP_AND_RETURN\\|Q_[[:upper:]]+\\)\\>") | |
6749 | @end example | |
6750 | @end table | |
6751 | @end defopt | |
6752 | ||
6753 | @defun c-make-macro-with-semi-re | |
6754 | @findex make-macro-with-semi-re (c-) | |
6755 | Call this (non-interactive) function, which sets internal variables, | |
6756 | each time you change the value of | |
6757 | @code{c-macro-names-with-semicolon}. It takes no arguments, and its | |
6758 | return value has no meaning. This function is called by @ccmode{}'s | |
6759 | initialization code. | |
6760 | @end defun | |
6761 | ||
4009494e | 6762 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
55f612f0 | 6763 | @node Odds and Ends, Sample Init File, Custom Macros, Top |
4009494e GM |
6764 | @comment node-name, next, previous, up |
6765 | @chapter Odds and Ends | |
6766 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6767 | ||
6768 | The stuff that didn't fit in anywhere else is documented here. | |
6769 | ||
6770 | @defopt c-require-final-newline | |
6771 | @vindex require-final-newline (c-) | |
6772 | Controls whether a final newline is enforced when the file is saved. | |
6773 | The value is an association list that for each language mode specifies | |
6774 | the value to give to @code{require-final-newline} (@pxref{Saving | |
9879e263 | 6775 | Buffers,,,@lispref{}, @lispreftitle{}}) at mode initialization. If a |
4009494e GM |
6776 | language isn't present on the association list, CC Mode won't touch |
6777 | @code{require-final-newline} in buffers for that language. | |
6778 | ||
6779 | The default is to set @code{require-final-newline} to @code{t} in the | |
6780 | languages that mandate that source files should end with newlines. | |
6781 | These are C, C++ and Objective-C. | |
6782 | @end defopt | |
6783 | ||
6784 | @defopt c-echo-syntactic-information-p | |
6785 | @vindex echo-syntactic-information-p (c-) | |
6786 | If non-@code{nil}, the syntactic analysis for the current line is shown | |
6787 | in the echo area when it's indented (unless | |
6788 | @code{c-syntactic-indentation} is @code{nil}). That's useful when | |
6789 | finding out which syntactic symbols to modify to get the indentation you | |
6790 | want. | |
6791 | @end defopt | |
6792 | ||
6793 | @defopt c-report-syntactic-errors | |
6794 | @vindex report-syntactic-errors (c-) | |
6795 | If non-@code{nil}, certain syntactic errors are reported with a ding and | |
6796 | a message, for example when an @code{else} is indented for which there | |
6797 | is no corresponding @code{if}. | |
6798 | ||
6799 | Note however that @ccmode{} doesn't make any special effort to check for | |
6800 | syntactic errors; that's the job of the compiler. The reason it can | |
6801 | report cases like the one above is that it can't find the correct | |
6802 | anchoring position to indent the line in that case. | |
6803 | @end defopt | |
6804 | ||
6805 | ||
6806 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
55f612f0 | 6807 | @node Sample Init File, Performance Issues, Odds and Ends, Top |
4009494e | 6808 | @comment node-name, next, previous, up |
55f612f0 | 6809 | @appendix Sample Init File |
4009494e GM |
6810 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
6811 | ||
6812 | Here's a sample .emacs file fragment that might help you along the way. | |
6813 | Just copy this region and paste it into your .emacs file. You might want | |
6814 | to change some of the actual values. | |
6815 | ||
6816 | @verbatim | |
6817 | ;; Make a non-standard key binding. We can put this in | |
6818 | ;; c-mode-base-map because c-mode-map, c++-mode-map, and so on, | |
6819 | ;; inherit from it. | |
6820 | (defun my-c-initialization-hook () | |
6821 | (define-key c-mode-base-map "\C-m" 'c-context-line-break)) | |
6822 | (add-hook 'c-initialization-hook 'my-c-initialization-hook) | |
6823 | ||
6824 | ;; offset customizations not in my-c-style | |
6825 | ;; This will take precedence over any setting of the syntactic symbol | |
6826 | ;; made by a style. | |
6827 | (setq c-offsets-alist '((member-init-intro . ++))) | |
6828 | ||
6829 | ;; Create my personal style. | |
6830 | (defconst my-c-style | |
6831 | '((c-tab-always-indent . t) | |
6832 | (c-comment-only-line-offset . 4) | |
6833 | (c-hanging-braces-alist . ((substatement-open after) | |
6834 | (brace-list-open))) | |
6835 | (c-hanging-colons-alist . ((member-init-intro before) | |
6836 | (inher-intro) | |
6837 | (case-label after) | |
6838 | (label after) | |
6839 | (access-label after))) | |
6840 | (c-cleanup-list . (scope-operator | |
6841 | empty-defun-braces | |
6842 | defun-close-semi)) | |
6843 | (c-offsets-alist . ((arglist-close . c-lineup-arglist) | |
6844 | (substatement-open . 0) | |
6845 | (case-label . 4) | |
6846 | (block-open . 0) | |
6847 | (knr-argdecl-intro . -))) | |
6848 | (c-echo-syntactic-information-p . t)) | |
6849 | "My C Programming Style") | |
6850 | (c-add-style "PERSONAL" my-c-style) | |
6851 | ||
6852 | ;; Customizations for all modes in CC Mode. | |
6853 | (defun my-c-mode-common-hook () | |
6854 | ;; set my personal style for the current buffer | |
6855 | (c-set-style "PERSONAL") | |
6856 | ;; other customizations | |
6857 | (setq tab-width 8 | |
6858 | ;; this will make sure spaces are used instead of tabs | |
6859 | indent-tabs-mode nil) | |
6860 | ;; we like auto-newline, but not hungry-delete | |
6861 | (c-toggle-auto-newline 1)) | |
6862 | (add-hook 'c-mode-common-hook 'my-c-mode-common-hook) | |
6863 | @end verbatim | |
6864 | ||
6865 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
55f612f0 | 6866 | @node Performance Issues, Limitations and Known Bugs, Sample Init File, Top |
4009494e GM |
6867 | @comment node-name, next, previous, up |
6868 | @chapter Performance Issues | |
6869 | @cindex performance | |
6870 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6871 | ||
6872 | @comment FIXME: (ACM, 2003/5/24). Check whether AWK needs mentioning here. | |
6873 | ||
6874 | C and its derivative languages are highly complex creatures. Often, | |
6875 | ambiguous code situations arise that require @ccmode{} to scan large | |
6876 | portions of the buffer to determine syntactic context. Such | |
6877 | pathological code can cause @ccmode{} to perform fairly badly. This | |
6878 | section gives some insight in how @ccmode{} operates, how that interacts | |
6879 | with some coding styles, and what you can use to improve performance. | |
6880 | ||
1df7defd | 6881 | The overall goal is that @ccmode{} shouldn't be overly slow (i.e., take |
4009494e | 6882 | more than a fraction of a second) in any interactive operation. |
1df7defd | 6883 | I.e., it's tuned to limit the maximum response time in single operations, |
4009494e GM |
6884 | which is sometimes at the expense of batch-like operations like |
6885 | reindenting whole blocks. If you find that @ccmode{} gradually gets | |
6886 | slower and slower in certain situations, perhaps as the file grows in | |
6887 | size or as the macro or comment you're editing gets bigger, then chances | |
6888 | are that something isn't working right. You should consider reporting | |
6889 | it, unless it's something that's mentioned in this section. | |
6890 | ||
6891 | Because @ccmode{} has to scan the buffer backwards from the current | |
6892 | insertion point, and because C's syntax is fairly difficult to parse in | |
6893 | the backwards direction, @ccmode{} often tries to find the nearest | |
6894 | position higher up in the buffer from which to begin a forward scan | |
6895 | (it's typically an opening or closing parenthesis of some kind). The | |
6896 | farther this position is from the current insertion point, the slower it | |
6897 | gets. | |
6898 | ||
6899 | @findex beginning-of-defun | |
6900 | In earlier versions of @ccmode{}, we used to recommend putting the | |
1df7defd | 6901 | opening brace of a top-level construct@footnote{E.g., a function in C, |
4009494e GM |
6902 | or outermost class definition in C++ or Java.} into the leftmost |
6903 | column. Earlier still, this used to be a rigid Emacs constraint, as | |
6904 | embodied in the @code{beginning-of-defun} function. @ccmode now | |
6905 | caches syntactic information much better, so that the delay caused by | |
6906 | searching for such a brace when it's not in column 0 is minimal, | |
6907 | except perhaps when you've just moved a long way inside the file. | |
6908 | ||
6909 | @findex defun-prompt-regexp | |
6910 | @vindex c-Java-defun-prompt-regexp | |
6911 | @vindex Java-defun-prompt-regexp (c-) | |
6912 | A special note about @code{defun-prompt-regexp} in Java mode: The common | |
6913 | style is to hang the opening braces of functions and classes on the | |
6914 | right side of the line, and that doesn't work well with the Emacs | |
6915 | approach. @ccmode{} comes with a constant | |
6916 | @code{c-Java-defun-prompt-regexp} which tries to define a regular | |
6917 | expression usable for this style, but there are problems with it. In | |
6918 | some cases it can cause @code{beginning-of-defun} to hang@footnote{This | |
6919 | has been observed in Emacs 19.34 and XEmacs 19.15.}. For this reason, | |
6920 | it is not used by default, but if you feel adventurous, you can set | |
6921 | @code{defun-prompt-regexp} to it in your mode hook. In any event, | |
6922 | setting and relying on @code{defun-prompt-regexp} will definitely slow | |
6923 | things down because (X)Emacs will be doing regular expression searches a | |
6924 | lot, so you'll probably be taking a hit either way! | |
6925 | ||
6926 | @ccmode{} maintains a cache of the opening parentheses of the blocks | |
6927 | surrounding the point, and it adapts that cache as the point is moved | |
6928 | around. That means that in bad cases it can take noticeable time to | |
6929 | indent a line in a new surrounding, but after that it gets fast as long | |
6930 | as the point isn't moved far off. The farther the point is moved, the | |
6931 | less useful is the cache. Since editing typically is done in ``chunks'' | |
6932 | rather than on single lines far apart from each other, the cache | |
6933 | typically gives good performance even when the code doesn't fit the | |
6934 | Emacs approach to finding the defun starts. | |
6935 | ||
6936 | @vindex c-enable-xemacs-performance-kludge-p | |
6937 | @vindex enable-xemacs-performance-kludge-p (c-) | |
6938 | XEmacs users can set the variable | |
6939 | @code{c-enable-xemacs-performance-kludge-p} to non-@code{nil}. This | |
6940 | tells @ccmode{} to use XEmacs-specific built-in functions which, in some | |
6941 | circumstances, can locate the top-most opening brace much more quickly than | |
6942 | @code{beginning-of-defun}. Preliminary testing has shown that for | |
1df7defd | 6943 | styles where these braces are hung (e.g., most JDK-derived Java styles), |
4009494e GM |
6944 | this hack can improve performance of the core syntax parsing routines |
6945 | from 3 to 60 times. However, for styles which @emph{do} conform to | |
44e97401 | 6946 | Emacs's recommended style of putting top-level braces in column zero, |
4009494e GM |
6947 | this hack can degrade performance by about as much. Thus this variable |
6948 | is set to @code{nil} by default, since the Emacs-friendly styles should | |
6949 | be more common (and encouraged!). Note that this variable has no effect | |
6950 | in Emacs since the necessary built-in functions don't exist (in Emacs | |
6951 | 22.1 as of this writing in February 2007). | |
6952 | ||
6953 | Text properties are used to speed up skipping over syntactic whitespace, | |
1df7defd | 6954 | i.e., comments and preprocessor directives. Indenting a line after a |
4009494e GM |
6955 | huge macro definition can be slow the first time, but after that the |
6956 | text properties are in place and it should be fast (even after you've | |
6957 | edited other parts of the file and then moved back). | |
6958 | ||
6959 | Font locking can be a CPU hog, especially the font locking done on | |
6960 | decoration level 3 which tries to be very accurate. Note that that | |
6961 | level is designed to be used with a font lock support mode that only | |
1df7defd | 6962 | fontifies the text that's actually shown, i.e., Lazy Lock or Just-in-time |
4009494e GM |
6963 | Lock mode, so make sure you use one of them. Fontification of a whole |
6964 | buffer with some thousand lines can often take over a minute. That is | |
6965 | a known weakness; the idea is that it never should happen. | |
6966 | ||
6967 | The most effective way to speed up font locking is to reduce the | |
6968 | decoration level to 2 by setting @code{font-lock-maximum-decoration} | |
6969 | appropriately. That level is designed to be as pretty as possible | |
6970 | without sacrificing performance. @xref{Font Locking Preliminaries}, for | |
6971 | more info. | |
6972 | ||
6973 | ||
6974 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6975 | @node Limitations and Known Bugs, FAQ, Performance Issues, Top | |
6976 | @comment node-name, next, previous, up | |
6977 | @chapter Limitations and Known Bugs | |
6978 | @cindex limitations | |
6979 | @cindex bugs | |
6980 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
6981 | ||
6982 | @itemize @bullet | |
6983 | @item | |
6984 | @ccmode{} doesn't support trigraphs. (These are character sequences | |
6985 | such as @samp{??(}, which represents @samp{[}. They date from a time | |
6986 | when some character sets didn't have all the characters that C needs, | |
6987 | and are now utterly obsolete.) | |
6988 | ||
6989 | @item | |
6990 | There is no way to apply auto newline settings (@pxref{Auto-newlines}) | |
6991 | on already typed lines. That's only a feature to ease interactive | |
6992 | editing. | |
6993 | ||
6994 | To generalize this issue a bit: @ccmode{} is not intended to be used as | |
6995 | a reformatter for old code in some more or less batch-like way. With | |
6996 | the exception of some functions like @code{c-indent-region}, it's only | |
6997 | geared to be used interactively to edit new code. There's currently no | |
6998 | intention to change this goal. | |
6999 | ||
7000 | If you want to reformat old code, you're probably better off using some | |
1df7defd | 7001 | other tool instead, e.g., @ref{Top, , GNU indent, indent, The `indent' |
4009494e GM |
7002 | Manual}, which has more powerful reformatting capabilities than |
7003 | @ccmode{}. | |
7004 | ||
7005 | @item | |
7006 | The support for C++ templates (in angle brackets) is not yet complete. | |
7007 | When a non-nested template is used in a declaration, @ccmode{} indents | |
1df7defd | 7008 | it and font-locks it OK@. Templates used in expressions, and nested |
4009494e GM |
7009 | templates do not fare so well. Sometimes a workaround is to refontify |
7010 | the expression after typing the closing @samp{>}. | |
7011 | ||
f1bb4ee1 AM |
7012 | @item |
7013 | In a @dfn{k&r region} (the part of an old-fashioned C function | |
7014 | declaration which specifies the types of its parameters, coming | |
7015 | between the parameter list and the opening brace), there should be at | |
7016 | most 20 top-level parenthesis and bracket pairs. This limit has been | |
7017 | imposed for performance reasons. If it is violated, the source file | |
7018 | might be incorrectly indented or fontified. | |
7019 | ||
4009494e GM |
7020 | @item |
7021 | On loading @ccmode{}, sometimes this error message appears: | |
7022 | ||
7023 | @example | |
7024 | File mode specification error: (void-variable c-font-lock-keywords-3) | |
7025 | @end example | |
7026 | ||
7027 | This is due to a bug in the function @code{eval-after-load} in some | |
7028 | versions of (X)Emacs. It can manifest itself when there is a symbolic | |
7029 | link in the path of the directory which contains (X)Emacs. As a | |
7030 | workaround, put the following into your @file{.emacs} file, fairly | |
7031 | early on: | |
7032 | ||
7033 | @example | |
7034 | (defun my-load-cc-fonts () | |
7035 | (require "cc-fonts")) | |
7036 | (add-hook 'c-initialization-hook 'my-load-cc-fonts) | |
7037 | @end example | |
7038 | @end itemize | |
7039 | ||
7040 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
7041 | @node FAQ, Updating CC Mode, Limitations and Known Bugs, Top | |
7042 | @comment node-name, next, previous, up | |
7043 | @appendix Frequently Asked Questions | |
7044 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
7045 | ||
7046 | @itemize @bullet | |
7047 | @item | |
7048 | @emph{How can I change the indent level from 4 spaces to 2 spaces?} | |
7049 | ||
7050 | Set the variable @code{c-basic-offset}. @xref{Getting Started}. | |
7051 | ||
7052 | @item | |
7053 | @kindex RET | |
7054 | @kindex C-j | |
7055 | @emph{Why doesn't the @kbd{RET} key indent the new line?} | |
7056 | ||
44e97401 | 7057 | Emacs's convention is that @kbd{RET} just adds a newline, and that |
4009494e GM |
7058 | @kbd{C-j} adds a newline and indents it. You can make @kbd{RET} do this |
7059 | too by adding this to your @code{c-initialization-hook}: | |
7060 | ||
7061 | @example | |
7062 | (define-key c-mode-base-map "\C-m" 'c-context-line-break) | |
7063 | @end example | |
7064 | ||
7065 | @xref{Getting Started}. This is a very common question. If you want | |
1df7defd | 7066 | this to be the default behavior, don't lobby us, lobby RMS@! @t{:-)} |
4009494e GM |
7067 | |
7068 | @item | |
7069 | @emph{How do I stop my code jumping all over the place when I type?} | |
7070 | ||
7071 | Deactivate ``electric minor mode'' with @kbd{C-c C-l}. @xref{Getting | |
7072 | Started}. | |
7073 | ||
7074 | @item | |
7075 | @kindex C-x h | |
7076 | @kindex C-M-\ | |
7077 | @emph{How do I reindent the whole file?} | |
7078 | ||
7079 | Visit the file and hit @kbd{C-x h} to mark the whole buffer. Then hit | |
7080 | @kbd{C-M-\}. @xref{Indentation Commands}. | |
7081 | ||
7082 | @item | |
7083 | @kindex C-M-q | |
7084 | @kindex C-M-u | |
7085 | @emph{How do I reindent the current block?} | |
7086 | ||
7087 | First move to the brace which opens the block with @kbd{C-M-u}, then | |
7088 | reindent that expression with @kbd{C-M-q}. @xref{Indentation | |
7089 | Commands}. | |
7090 | ||
7091 | @item | |
7092 | @emph{I put @code{(c-set-offset 'substatement-open 0)} in my | |
7093 | @file{.emacs} file but I get an error saying that @code{c-set-offset}'s | |
7094 | function definition is void. What's wrong?} | |
7095 | ||
7096 | This means that @ccmode{} hasn't yet been loaded into your Emacs | |
7097 | session by the time the @code{c-set-offset} call is reached, most | |
7098 | likely because @ccmode{} is being autoloaded. Instead of putting the | |
7099 | @code{c-set-offset} line in your top-level @file{.emacs} file, put it | |
7100 | in your @code{c-initialization-hook} (@pxref{CC Hooks}), or simply | |
7101 | modify @code{c-offsets-alist} directly: | |
7102 | ||
7103 | @example | |
7104 | (setq c-offsets-alist '((substatement-open . 0))) | |
7105 | @end example | |
7106 | ||
7107 | @item | |
7108 | @cindex open paren in column zero | |
7109 | @emph{I have an open paren character at column zero inside a comment or | |
7110 | multiline string literal, and it causes the fontification and/or | |
7111 | indentation to go haywire. What gives?} | |
7112 | ||
7113 | It's due to the ad-hoc rule in (X)Emacs that such open parens always | |
7114 | start defuns (which translates to functions, classes, namespaces or any | |
7115 | other top-level block constructs in the @ccmode{} languages). | |
7116 | @ifset XEMACS | |
7117 | @xref{Defuns,,, xemacs, XEmacs User's Manual}, for details. | |
7118 | @end ifset | |
7119 | @ifclear XEMACS | |
7120 | @xref{Left Margin Paren,,, emacs, GNU Emacs Manual}, for details | |
7121 | (@xref{Defuns,,, emacs, GNU Emacs Manual}, in the Emacs 20 manual). | |
7122 | @end ifclear | |
7123 | ||
7124 | This heuristic is built into the core syntax analysis routines in | |
7125 | (X)Emacs, so it's not really a @ccmode{} issue. However, in Emacs | |
7126 | 21.1 it became possible to turn it off@footnote{Using the variable | |
7127 | @code{open-paren-in-column-0-is-defun-start}.} and @ccmode{} does so | |
7128 | there since it's got its own system to keep track of blocks. | |
7129 | ||
7130 | @end itemize | |
7131 | ||
7132 | ||
7133 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
7134 | @node Updating CC Mode, Mailing Lists and Bug Reports, FAQ, Top | |
7135 | @comment node-name, next, previous, up | |
7136 | @appendix Getting the Latest CC Mode Release | |
7137 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
7138 | ||
7139 | @ccmode{} has been standard with all versions of Emacs since 19.34 and | |
7140 | of XEmacs since 19.16. | |
7141 | ||
7142 | @cindex web site | |
7143 | Due to release schedule skew, it is likely that all of these Emacsen | |
7144 | have old versions of @ccmode{} and so should be upgraded. Access to the | |
7145 | @ccmode{} source code, as well as more detailed information on Emacsen | |
7146 | compatibility, etc. are all available on the web site: | |
7147 | ||
7148 | @quotation | |
7149 | @uref{http://cc-mode.sourceforge.net/} | |
7150 | @end quotation | |
7151 | ||
7152 | ||
7153 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
7154 | @node Mailing Lists and Bug Reports, GNU Free Documentation License, Updating CC Mode, Top | |
7155 | @comment node-name, next, previous, up | |
7156 | @appendix Mailing Lists and Submitting Bug Reports | |
7157 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
7158 | ||
7159 | @kindex C-c C-b | |
7160 | @findex c-submit-bug-report | |
7161 | @findex submit-bug-report (c-) | |
7162 | To report bugs, use the @kbd{C-c C-b} (bound to | |
7163 | @code{c-submit-bug-report}) command. This provides vital information | |
7164 | we need to reproduce your problem. Make sure you include a concise, | |
7165 | but complete code example. Please try to boil your example down to | |
7166 | just the essential code needed to reproduce the problem, and include | |
7167 | an exact recipe of steps needed to expose the bug. Be especially sure | |
7168 | to include any code that appears @emph{before} your bug example, if | |
7169 | you think it might affect our ability to reproduce it. | |
7170 | ||
7171 | Please try to produce the problem in an Emacs instance without any | |
1df7defd | 7172 | customizations loaded (i.e., start it with the @samp{-q --no-site-file} |
4009494e GM |
7173 | arguments). If it works correctly there, the problem might be caused |
7174 | by faulty customizations in either your own or your site | |
7175 | configuration. In that case, we'd appreciate it if you isolate the | |
7176 | Emacs Lisp code that triggers the bug and include it in your report. | |
7177 | ||
7178 | @cindex bug report mailing list | |
7179 | Bug reports should be sent to @email{bug-cc-mode@@gnu.org}. You can | |
7180 | also send other questions and suggestions (kudos? @t{;-)} to that | |
7181 | address. It's a mailing list which you can join or browse an archive | |
7182 | of; see the web site at @uref{http://cc-mode.sourceforge.net/} for | |
7183 | further details. | |
7184 | ||
7185 | @cindex announcement mailing list | |
7186 | If you want to get announcements of new @ccmode{} releases, send the | |
7187 | word @emph{subscribe} in the body of a message to | |
7188 | @email{cc-mode-announce-request@@lists.sourceforge.net}. It's possible | |
7189 | to subscribe from the web site too. Announcements will also be posted | |
7190 | to the Usenet newsgroups @code{gnu.emacs.sources}, @code{comp.emacs}, | |
7191 | @code{comp.emacs.xemacs}, @code{comp.lang.c}, @code{comp.lang.c++}, | |
7192 | @code{comp.lang.objective-c}, @code{comp.lang.java.softwaretools}, | |
7193 | @code{comp.lang.idl}, and @code{comp.lang.awk}. | |
7194 | @c There is no newsgroup for Pike. :-( | |
7195 | ||
7196 | ||
7197 | @node GNU Free Documentation License, Command and Function Index, Mailing Lists and Bug Reports, Top | |
7198 | @appendix GNU Free Documentation License | |
7199 | @include doclicense.texi | |
7200 | ||
7201 | ||
7202 | @c Removed the tentative node "Mode Initialization" from here, 2005/8/27. | |
7203 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
7204 | @node Command and Function Index, Variable Index, GNU Free Documentation License, Top | |
7205 | @comment node-name, next, previous, up | |
7206 | @unnumbered Command and Function Index | |
7207 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
7208 | ||
7209 | Since most @ccmode{} commands are prepended with the string | |
7210 | @samp{c-}, each appears under its @code{c-@var{thing}} name and its | |
7211 | @code{@var{thing} (c-)} name. | |
7212 | @iftex | |
7213 | @sp 2 | |
7214 | @end iftex | |
7215 | @printindex fn | |
7216 | ||
7217 | ||
7218 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
7219 | @node Variable Index, Concept and Key Index, Command and Function Index, Top | |
7220 | @comment node-name, next, previous, up | |
7221 | @unnumbered Variable Index | |
7222 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
7223 | ||
7224 | Since most @ccmode{} variables are prepended with the string | |
7225 | @samp{c-}, each appears under its @code{c-@var{thing}} name and its | |
7226 | @code{@var{thing} (c-)} name. | |
7227 | @iftex | |
7228 | @sp 2 | |
7229 | @end iftex | |
7230 | @printindex vr | |
7231 | ||
7232 | ||
7233 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
7234 | @node Concept and Key Index, , Variable Index, Top | |
7235 | @comment node-name, next, previous, up | |
7236 | @unnumbered Concept and Key Index | |
7237 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
7238 | ||
7239 | @printindex cp | |
7240 | ||
7241 | ||
7242 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
7243 | @comment Epilogue. | |
7244 | @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | |
7245 | ||
4009494e | 7246 | @bye |