*** empty log message ***

diff --git a/etc/NEWS b/etc/NEWS
index 35c4e871ff30ad5b6d2cd866e3d9cadbc552441d..7c49adf99a8bf205bbcbe9803dbafbb20c84f0a5 100644 (file)
--- a/etc/NEWS
+++ b/etc/NEWS
@@ -705,7 +705,10 @@ instead of using default-major-mode.
 ---
 ** Perl mode has a new variable `perl-indent-continued-arguments'.
 
++++
 ** Fortran mode has a new variable `fortran-directive-re'.
+Adapt this to match the format of any compiler directives you use.
+Lines that match are never indented, and are given distinctive font-locking.
 
 ---
 ** F90 mode has new navigation commands `f90-end-of-block',

diff --git a/man/programs.texi b/man/programs.texi
index a34d84e5d380608521b6d524ef1ee06b46fdc1f8..70f3c25fd1f40c94b6ea9cc68adb066ce73340d0 100644 (file)
--- a/man/programs.texi
+++ b/man/programs.texi
@@ -2155,6 +2155,15 @@ full-line comments by setting the variable
 @code{fortran-comment-indent-char} to the single-character string you want
 to use.
 
+@vindex fortran-directive-re
+  Compiler directive lines, or preprocessor lines, have much the same
+appearance as comment lines.  It is important, though, that such lines
+never be indented at all, no matter what the value of
+@code{fortran-comment-indent-style}.  The variable
+@code{fortran-directive-re} is a regular expression that specifies which
+lines are directives.  Matching lines are never indented, and receive
+distinctive font-locking.
+
 @vindex comment-line-start
 @vindex comment-line-start-skip
   Fortran mode introduces two variables @code{comment-line-start} and