It's common that ASCII text files in FMU projects have no file extension or arbitrary ones. Some key examples of this are
random.seeds- a file that contains list of seed integers
ERT workflow/job configurations and definitions
well.obs- two column ASCII data files with well observational data
multregt.tmpl - these files are used by ERT's GEN_KW keyword
more?
These files don't necessarily need highlighting but should be supported. This could mean opening files with unsupported file extensions as text by default or reading the entirety of the file to ensure it's fully ASCII or UTF-8 before opening. The Monaco portion of the code does the former already, so it might be the case that only the openFile thunk needs to be looked at.
It's common that ASCII text files in FMU projects have no file extension or arbitrary ones. Some key examples of this are
random.seeds
- a file that contains list of seed integerswell.obs
- two column ASCII data files with well observational datamultregt.tmpl
- these files are used by ERT'sGEN_KW
keywordThese files don't necessarily need highlighting but should be supported. This could mean opening files with unsupported file extensions as text by default or reading the entirety of the file to ensure it's fully ASCII or UTF-8 before opening. The Monaco portion of the code does the former already, so it might be the case that only the
openFile
thunk needs to be looked at.