As pointed out in #55 the extension by default recognises log files as lammps files (due to the default name log.lammps). The syntax highlighting for log files is likely appreciated by users, but the pre-run checks throw errors, which makes obviously no sense for a log file.
It would be nice to to find a way to automatically distinguish in-files from log-files and disable the pre-run-checks for the latter. One obvious way would be to go by file name, because by default the log files are named log.lammps. However, this can be altered and log files can have any name I believe. So it may be better to actually go by file-content in some way.
As pointed out in #55 the extension by default recognises log files as lammps files (due to the default name log.lammps). The syntax highlighting for log files is likely appreciated by users, but the pre-run checks throw errors, which makes obviously no sense for a log file.
It would be nice to to find a way to automatically distinguish in-files from log-files and disable the pre-run-checks for the latter. One obvious way would be to go by file name, because by default the log files are named log.lammps. However, this can be altered and log files can have any name I believe. So it may be better to actually go by file-content in some way.