@Arjan-van-Dijk ,
NppExec vs NppEventExec: the NppEventExec is a helper which registers callbacks, but requires that NppExec be installed (as far as I understand; I personally use NppExec, but haven’t used NppEventExec to any serious extent).
Syntax checking: I have a script for the PythonScript plugin which runs perl -c to check the syntax on my perl code every time I save. If there is a Fortran syntax checker, you could easily modify that script to call fortrancheck.exe or whatever it’s called.
Compile: for compiling, I tend to use NppExec for that. For example, the following NppExec script will save the current file, compile it with GCC, and run the result:
npp_save
cd "$(CURRENT_DIRECTORY)"
gcc "$(FILE_NAME)" -o "$(NAME_PART)"
npp_run cmd.exe /k "$(NAME_PART)"
The Plugins > NppExec > Console Output Filters > Highlight interface allows you to define strings that will parse out FILE, LINE, and CHARacter position from error strings in the NppExec console, and will highlight those error strings, and if you click on them, they will take you to the problem position in your source code. It comes preinstalled with filters that work for many C compilers. And you can edit them, or add your own. For example, I have added one to match perl’s die output, which is ERROR MESSAGE at FILEPATH line NNN… To match this, I have a filter * at %FILE% line %LINE% which colors the line red (FF, 00, 00). And if I got the message FakeError at c:\path\to\script.pl line 6 when I run my script, it will go to line 6 of that file if I double-click that line. These filters work for any text printed into the NppExec console, so if you run your compiler in NppExec, it can find compiler errors/warnings; and you run your program in that same window, it can also find runtime errors/warnings (assuming your language has that concept of printing such runtime messages to the console; given the age of FORTRAN, I am quite confident it does.)
