Open miEsMar opened 8 months ago
I don't know enough fortran to tell what I'm seeing lol
This is foo.f
opened in with the min config
Same config, same file in telescope ^ this looks like it has syntax highlighting but looks totally different from the other one above
Can you elaborate some more?
Hi @jamestrew , thanks for getting back.
What you're seeing is:
when opening the buffer normally in (Neo)Vim
, the fortran.vim
syntax file detects the fixed file format since the file has the .f
extension. So, all those red highlighting at the beginning of each line is because for it that's an error, cause all syntactical lines should begin at the 7th column onwards (the first 6 column characters are reserved for labels and other things).
On the other hand, it's funny how instead Telescope
preview highlights it using the free file format, which is what happens to be actually used, regardless of the .f
file extension.
This is what I have instead (extension: .f90
):
NOTE: this is what I have instead if I change with .f
file extension:
The only way for me to get it to work is by setting .f77
as file extension:
Description
When searching files, seraching by grep (or every other Telescope command), if file is a Fortran file preview does not apply any syntax highlight, just plain text.
Neovim version
Operating system and version
Win 10 Pro version 10.0.19045 N/D build 19045
Telescope version / branch / rev
telescope 0.1.x
checkhealth telescope
Steps to reproduce
Expected behavior
Syntex highlighting in Telescope preview for Fortran files.
Actual behavior
Preview shows Fortran files as plain text, no syntax highlight.
Minimal config