Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
@M0JXD Thanks for your input. For the dart config file though one should only define "Dart commands", not the "Independent commands" which are common for all programming languages.
We are slightly limited in the number of command "slots" Geany offers - i.e. 3 for compile commands and 2 for execute commands. I think that since Dart is the main language, it should be dart commands by default (for execute the second option can be flutter though). How about:
[build-menu]
# %f will be replaced by the complete filename
# %e will be replaced by the filename without extension
FT_00_LB=_Compile
FT_00_CM=dart compile exe "%f"
FT_00_WD=
FT_01_LB=_Analyze
FT_01_CM=dart analyze "%f"
FT_01_WD=
FT_02_LB=_Test
FT_02_CM=dart test "%f"
FT_02_WD=
EX_00_LB=Dart _Run
EX_00_CM=dart run "%f"
EX_00_WD=%p
EX_01_LB=Flutter R_un
EX_01_CM=flutter run "%f"
EX_01_WD=%pI think the format command you used isn't a good candidate for compile commands as it can modify the current (possibly unsaved) buffer that may need to be reloaded. Dart LSP server is a much better candidate for this.
Speaking of LSP, I've added some default config option for the Dart LSP server to https://github.com/techee/geany-lsp which, if interested, you can try together with #3973. As far as I can tell everything works but I'd be interested in real Dart user feedback.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.