Thank you for the hint, Ruhan.
I am however not sure how well this would work out.
When I ran
gdevelop --help, or
there was no reaction so I thought command line parameters are not used at all. I just checked by giving a full path and wow, the project file was opened. Thank you for the fast implementation.
I use json files in many cases. There are lots that are not related to GDevelop, neither in context nor in structure. Thus I recommend changing the default extension to some custom value (e.g. *.gdevelop) so setting the association you describe does not break other behaviours like opening JSON files with my favourite IDE.
You suggest to choose “save as” from the GUI menu - I can already achieve that on the command line with a file copy.
I was not asking to save the project in another directory but to ‘export’ the project. Probably poorly named, as I believe the game.json file gets compiled into whatever format I choose - however the menu entry is called export so I am reusing that term.
My intention is to trigger this export function from the command line, without further activity on the UI. I think Bouh understood the gist.