From: Glenn Morris Date: Mon, 24 Jun 2002 21:48:18 +0000 (+0000) Subject: *** empty log message *** X-Git-Tag: ttn-vms-21-2-B4~14462 X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=2d588beb819b2f8444eac522f04bc95656fcfa3b;p=emacs.git *** empty log message *** --- diff --git a/etc/NEWS b/etc/NEWS index 35c4e871ff3..7c49adf99a8 100644 --- 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 a34d84e5d38..70f3c25fd1f 100644 --- 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