I am editing a fortran90 code with vim. Note that I'm working with a *.f90 file, not *.f. vim doesn't recognize as legitimate code anything beyond column 72. This is an annoying problem because if a quote is opened at, say, column 50 but not closed until column 80, then vim colors all the following lines as part of the same quote. This would make sense if I was working with an old fortran77 file, but I'm clearly not. Is there any way to convince vim to recognize code beyond column 72?
相关问题
- CABS(x) function for complex(8)
- Emacs shell: save commit message
- How to change the first two uppercase characters o
- Insert text into current buffer from function
- Upper bound of random number generator
相关文章
- 如何让 vim 支持 .cshtml 文件的代码高亮
- Auto-save in VIM as you type
- How can I use gcc's -I command to add recursiv
- Does gfortran take advantage of DO CONCURRENT?
- Vim: overloaded mapping for multiple modes
- How to use relative line numbering universally in
- Fortran 90 - “Segmentation fault - invalid memory
- How to copy the value of a vim option to a registe
This could be related to the 'synmaxcol' variable. If you run
In vim's command line, what do you get back? Setting this option higher might fix your issue. It's generally set low as vim can get laggy when syntax highlighting very long lines, such as those found in XML.
if I create a new .f90 file syntax is highlighted as if it is fortran 77 (fixed line length, comments in first col, code at 6th col, etc etc) rather than modern free form fortran.
does the trick to get vim highlighting it correctly.