You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have started working on a linter for GAMS mode (a feature present in GAMS Studio). I have put it in a separate file in my repo: gams-flymake.el. For now, it is at an early stage. It works well on small files, but it has to be tested in more complex settings.
The idea is simple: parse the lst file for the errors and highlight the GAMS code with the error using flymake, which is now built-in in emacs. When it will be fully functional, there would be no need to go to the LST files to fix errors.
For now, the approach may be too eager: the linter is launched immediately when you open a GAMS file (only for gms files). It could be better to do as in GAMS Studio, only lint the code after a run (or if asked by the user).
The text was updated successfully, but these errors were encountered:
Hi,
I have started working on a linter for GAMS mode (a feature present in GAMS Studio). I have put it in a separate file in my repo: gams-flymake.el. For now, it is at an early stage. It works well on small files, but it has to be tested in more complex settings.
The idea is simple: parse the lst file for the errors and highlight the GAMS code with the error using flymake, which is now built-in in emacs. When it will be fully functional, there would be no need to go to the LST files to fix errors.
For now, the approach may be too eager: the linter is launched immediately when you open a GAMS file (only for gms files). It could be better to do as in GAMS Studio, only lint the code after a run (or if asked by the user).
The text was updated successfully, but these errors were encountered: