[Emacs-diffs] Changes to emacs/etc/NEWS

[Alan Mackenzie]

Index: emacs/etc/NEWS
diff -c emacs/etc/NEWS:1.1291 emacs/etc/NEWS:1.1292
*** emacs/etc/NEWS:1.1291       Fri Dec  2 19:48:47 2005
--- emacs/etc/NEWS      Sun Dec  4 21:00:59 2005
***************
*** 2005,2010 ****
--- 2005,2058 ----
  +++
  ** CC mode changes.
  
+ *** The CC Mode manual has been extensively revised.
+ The information about using CC Mode has been separated from the larger
+ and more difficult chapters about configuration.
+ 
+ *** Changes in Key Sequences
+ **** c-toggle-auto-hungry-state is no longer bound to C-c C-t.
+ 
+ **** c-toggle-hungry-state is no longer bound to C-c C-d.
+ This binding has been taken over by c-hungry-delete-forwards.
+ 
+ **** c-toggle-auto-state (C-c C-t) has been renamed to c-toggle-auto-newline.
+ c-toggle-auto-state remains as an alias.
+ 
+ **** The new commands c-hungry-backspace and c-hungry-delete-forwards
+ have key bindings C-c C-DEL (or C-c DEL, for the benefit of TTYs) and
+ C-c C-d (or C-c C-<delete> or C-c <delete>) respectively.  These
+ commands delete entire blocks of whitespace with a single
+ key-sequence.  [N.B. "DEL" is the <backspace> key.]
+ 
+ **** The new command c-toggle-electric-mode is bound to C-c C-l.
+ 
+ **** The new command c-subword-mode is bound to C-c C-w.
+ 
+ *** C-c C-s (`c-show-syntactic-information') now highlights the anchor
+ position(s).
+ 
+ *** New Minor Modes
+ **** Electric Minor Mode toggles the electric action of non-alphabetic keys.
+ The new command c-toggle-electric-mode is bound to C-c C-l.  Turning the
+ mode off can be helpful for editing chaotically indented code and for
+ users new to CC Mode, who sometimes find electric indentation
+ disconcerting.  Its current state is displayed in the mode line with an
+ 'l', e.g. "C/al".
+ 
+ **** Subword Minor Mode makes Emacs recognize word boundaries at upper case
+ letters in StudlyCapsIdentifiers.  You enable this feature by C-c C-w.  It can
+ also be used in non-CC Mode buffers.  :-) Contributed by Masatake YAMATO.
+ 
+ *** New clean-ups
+ 
+ **** `comment-close-slash'.
+ With this clean-up, a block (i.e. c-style) comment can be terminated by
+ typing a slash at the start of a line.
+ 
+ **** `c-one-liner-defun'
+ This clean-up compresses a short enough defun (for example, an AWK
+ pattern/action pair) onto a single line.  "Short enough" is configurable.
+ 
  *** Font lock support.
  CC Mode now provides font lock support for all its languages.  This
  supersedes the font lock patterns that have been in the core font lock
***************
*** 2024,2034 ****
  variable font-lock-maximum-decoration.
  
  Note that the most demanding font lock level has been tuned with lazy
! fontification in mind, i.e.  there should be a support mode that waits
! with the fontification until the text is actually shown
! (e.g. Just-in-time Lock mode, which is the default, or Lazy Lock
! mode).  Fontifying a file with several thousand lines in one go can
! take the better part of a minute.
  
  **** The (c|c++|objc|java|idl|pike)-font-lock-extra-types variables
  are now used by CC Mode to recognize identifiers that are certain to
--- 2072,2081 ----
  variable font-lock-maximum-decoration.
  
  Note that the most demanding font lock level has been tuned with lazy
! fontification in mind; Just-In-Time-Lock mode should be enabled for
! the highest font lock level (by default, it is).  Fontifying a file
! with several thousand lines in one go can take the better part of a
! minute.
  
  **** The (c|c++|objc|java|idl|pike)-font-lock-extra-types variables
  are now used by CC Mode to recognize identifiers that are certain to
***************
*** 2043,2052 ****
  language, so it's possible to e.g. turn on Javadoc font locking in C
  buffers.  See the variable c-doc-comment-style for details.
  
! Currently two kinds of doc comment styles are recognized: Suns Javadoc
! and Autodoc which is used in Pike.  This is by no means a complete
! list of the most common tools; if your doc comment extractor of choice
! is missing then please drop a note to address@hidden
  
  **** Better handling of C++ templates.
  As a side effect of the more accurate font locking, C++ templates are
--- 2090,2100 ----
  language, so it's possible to e.g. turn on Javadoc font locking in C
  buffers.  See the variable c-doc-comment-style for details.
  
! Currently three kinds of doc comment styles are recognized: Sun's
! Javadoc, Autodoc (which is used in Pike) and GtkDoc (used in C).  (The
! last was contributed by Masatake YAMATO).  This is by no means a
! complete list of the most common tools; if your doc comment extractor
! of choice is missing then please drop a note to address@hidden
  
  **** Better handling of C++ templates.
  As a side effect of the more accurate font locking, C++ templates are
***************
*** 2081,2094 ****
  are normally placed under the start of the respective pattern, function
  definition, or structured statement.
  
! The predefined indentation functions haven't yet been adapted for AWK
! mode, though some of them may work serendipitously.  There shouldn't be
! any problems writing custom indentation functions for AWK mode.
! 
! The command C-c C-q (c-indent-defun) hasn't yet been adapted for AWK,
! though in practice it works properly nearly all the time.  Should it
! fail, explicitly set the region around the function (using C-u C-SPC:
! C-M-h probably won't work either) then do C-M-\ (indent-region).
  
  **** Font Locking
  There is a single level of font locking in AWK mode, rather than the
--- 2129,2137 ----
  are normally placed under the start of the respective pattern, function
  definition, or structured statement.
  
! The predefined line-up functions haven't yet been adapted for AWK
! mode, though some of them may work serendipitously.  There shouldn't
! be any problems writing custom indentation functions for AWK mode.
  
  **** Font Locking
  There is a single level of font locking in AWK mode, rather than the
***************
*** 2096,2119 ****
  idiosyncrasies in AWK mode's font-locking due to the peculiarities of
  the AWK language itself.
  
! **** Comment Commands
! M-; (indent-for-comment) works fine.  None of the other CC Mode
! comment formatting commands have yet been adapted for AWK mode.
! 
! **** Movement Commands
! Most of the movement commands work in AWK mode.  The most important
! exceptions are M-a (c-beginning-of-statement) and M-e
! (c-end-of-statement) which haven't yet been adapted.
! 
! The notion of "defun" has been augmented to include AWK pattern-action
! pairs.  C-M-a (c-awk-beginning-of-defun) and C-M-e (c-awk-end-of-defun)
! recognize these pattern-action pairs, as well as user defined
! functions.
! 
! **** Auto-newline Insertion and Clean-ups
! Auto-newline insertion hasn't yet been adapted for AWK.  Some of
! the clean-ups can actually convert good AWK code into syntactically
! invalid code.  These features are best disabled in AWK buffers.
  
  *** New syntactic symbols in IDL mode.
  The top level constructs "module" and "composition" (from CIDL) are
--- 2139,2154 ----
  idiosyncrasies in AWK mode's font-locking due to the peculiarities of
  the AWK language itself.
  
! **** Comment and Movement Commands
! These commands all work for AWK buffers.  The notion of "defun" has
! been augmented to include AWK pattern-action pairs - the standard
! "defun" commands on key sequences C-M-a, C-M-e, and C-M-h use this
! extended definition.
! 
! **** "awk" style, Auto-newline Insertion and Clean-ups
! A new style, "awk" has been introduced, and this is now the default
! style for AWK code.  With auto-newline enabled, the clean-up
! c-one-liner-defun (see above) is useful.
  
  *** New syntactic symbols in IDL mode.
  The top level constructs "module" and "composition" (from CIDL) are
***************
*** 2122,2129 ****
  composition-close, and incomposition.
  
  *** New functions to do hungry delete without enabling hungry delete mode.
! The functions `c-hungry-backspace' and `c-hungry-delete-forward' can be
! bound to keys to get this feature without toggling a mode.
  
  *** Better control over `require-final-newline'.
  
--- 2157,2166 ----
  composition-close, and incomposition.
  
  *** New functions to do hungry delete without enabling hungry delete mode.
! The new functions `c-hungry-backspace' and `c-hungry-delete-forward'
! provide hungry deletion without having to toggle a mode.  They are
! bound to C-c C-DEL and C-c C-d (and several variants, for the benefit
! of different keyboard setups.  See "Changes in key sequences" above).
  
  *** Better control over `require-final-newline'.
  
***************
*** 2151,2160 ****
  In some cases there are more than one position given for a syntactic
  symbol.
  
! This change might affect code that call `c-guess-basic-syntax' directly,
! and custom lineup functions if they use `c-syntactic-context'.  However,
! the argument given to lineup functions is still a single cons cell
! with nil or an integer in the cdr.
  
  *** API changes for derived modes.
  
--- 2188,2198 ----
  In some cases there are more than one position given for a syntactic
  symbol.
  
! This change might affect code that calls `c-guess-basic-syntax'
! directly, and custom lineup functions if they use
! `c-syntactic-context'.  However, the argument given to lineup
! functions is still a single cons cell with nil or an integer in the
! cdr.
  
  *** API changes for derived modes.
  
***************
*** 2165,2171 ****
  Mode with less risk of such problems in the future.
  
  **** New language variable system.
! See the comment blurb near the top of cc-langs.el.
  
  **** New initialization functions.
  The initialization procedure has been split up into more functions to
--- 2203,2210 ----
  Mode with less risk of such problems in the future.
  
  **** New language variable system.
! These are variables whose values vary between CC Mode's different
! languages.  See the comment blurb near the top of cc-langs.el.
  
  **** New initialization functions.
  The initialization procedure has been split up into more functions to
***************
*** 2215,2229 ****
  
  **** Better alignment of line continuation backslashes.
  `c-backslash-region' tries to adapt to surrounding backslashes.  New
! variable `c-backslash-max-column' which put a limit on how far out
  backslashes can be moved.
  
  **** Automatic alignment of line continuation backslashes.
  This is controlled by the new variable `c-auto-align-backslashes'.  It
  affects `c-context-line-break', `c-context-open-line' and newlines
  inserted in Auto-Newline mode.
- **** Line indentation works better inside macros.
  
  Regardless whether syntactic indentation and syntactic indentation
  inside macros are enabled or not, line indentation now ignores the
  line continuation backslashes.  This is most noticeable when syntactic
--- 2254,2268 ----
  
  **** Better alignment of line continuation backslashes.
  `c-backslash-region' tries to adapt to surrounding backslashes.  New
! variable `c-backslash-max-column' puts a limit on how far out
  backslashes can be moved.
  
  **** Automatic alignment of line continuation backslashes.
  This is controlled by the new variable `c-auto-align-backslashes'.  It
  affects `c-context-line-break', `c-context-open-line' and newlines
  inserted in Auto-Newline mode.
  
+ **** Line indentation works better inside macros.
  Regardless whether syntactic indentation and syntactic indentation
  inside macros are enabled or not, line indentation now ignores the
  line continuation backslashes.  This is most noticeable when syntactic
***************
*** 2232,2241 ****
  
  *** indent-for-comment is more customizable.
  The behavior of M-; (indent-for-comment) is now configurable through
! the variable `c-indent-comment-alist'.  The indentation behavior based
! on the preceding code on the line, e.g. to get two spaces after #else
! and #endif but indentation to `comment-column' in most other cases
! (something which was hardcoded earlier).
  
  *** New function `c-context-open-line'.
  It's the open-line equivalent of `c-context-line-break'.
--- 2271,2280 ----
  
  *** indent-for-comment is more customizable.
  The behavior of M-; (indent-for-comment) is now configurable through
! the variable `c-indent-comment-alist'.  The indentation behavior is
! based on the preceding code on the line, e.g. to get two spaces after
! #else and #endif but indentation to `comment-column' in most other
! cases (something which was hardcoded earlier).
  
  *** New function `c-context-open-line'.
  It's the open-line equivalent of `c-context-line-break'.