*** empty log message ***
This commit is contained in:
parent
c1a1535ae4
commit
2d588beb81
2 changed files with 12 additions and 0 deletions
3
etc/NEWS
3
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',
|
||||
|
|
|
@ -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
|
||||
|
|
Loading…
Add table
Reference in a new issue