diff options
Diffstat (limited to 'lisp/progmodes/fortran.el')
| -rw-r--r-- | lisp/progmodes/fortran.el | 11 |
1 files changed, 6 insertions, 5 deletions
diff --git a/lisp/progmodes/fortran.el b/lisp/progmodes/fortran.el index 811951eaaaf..d84c3795653 100644 --- a/lisp/progmodes/fortran.el +++ b/lisp/progmodes/fortran.el @@ -1,4 +1,4 @@ -;;; fortran.el --- Fortran mode for GNU Emacs +;;; fortran.el --- Fortran mode for GNU Emacs -*- lexical-binding: t -*- ;; Copyright (C) 1986, 1993-1995, 1997-2020 Free Software Foundation, ;; Inc. @@ -429,7 +429,7 @@ The only difference is, it returns t in a case when the default returns nil." fortran-font-lock-keywords-1 ;; All type specifiers plus their declared items. (list - (list (concat fortran-type-types "[ \t(/]*\\(*\\)?") + (list (concat fortran-type-types "[ \t(/]*\\(\\*\\)?") ;; Type specifier. '(1 font-lock-type-face) ;; Declaration item (or just /.../ block name). @@ -495,14 +495,15 @@ This is used to fontify fixed-format Fortran comments." ;; `byte-compile', but simple benchmarks indicate that it's probably not ;; worth the trouble (about 0.5% of slow down). (eval ;I hate `eval', but it's hard to avoid it here. - '(syntax-propertize-rules + `(syntax-propertize-rules ("^[CcDd\\*]" (0 "<")) ;; We mark all chars after line-length as "comment-start", rather than ;; just the first one. This is so that a closing ' that's past the ;; line-length will indeed be ignored (and will result in a string that ;; leaks into subsequent lines). - ((format "^[^CcDd\\*\t\n].\\{%d\\}\\(.+\\)" (1- line-length)) - (1 "<"))))) + (,(format "^[^CcDd\\*\t\n].\\{%d\\}\\(.+\\)" (1- line-length)) + (1 "<"))) + t)) (defvar fortran-font-lock-keywords fortran-font-lock-keywords-1 "Default expressions to highlight in Fortran mode.") |