Add option to hide project close/save warning when opening new project

[xiota]

This adds an option to hide the warning when opening a project while one is already open. (The default is to retain the warning.) Since projects autosave when closed, no work is lost and the project can just be reopened if needed. Depending on how the user manages project files, reopening the previous project can take less time than responding to the dialog.

[xiota]

@elextr Think this PR is ready for re-review. Also, if you don't mind, would you look at #2947 (addition to manual to show use of GEANY_DEFAULT_FILETYPE_REGEX feature).

[elextr]

Please remove the po/.intltool-merge-cache.lock otherwise I'm ok. Good that its documented in the manual and in the plugin API.

But lets see if anyone else loves or loathes it.

[elextr]

Added to 1.39 milestone so its not forgotten

[xiota]

Sorry about that lock file... is it okay if I add it to .gitignore?

[elextr]

Sorry about that lock file... is it okay if I add it to .gitignore?

Shouldn't need to 2977a91

[eht16]

Tested and LGTM apart from the minor issue regarding bumping GEANY_API_VERSION.

Maybe the PR description could be updated to not mention "Don't re-open a project that is already open" which isn't part of this PR anymore?

[xiota]

@eht16 I've edited the initial description. I don't know how to bump the GEANY_API_VERSION.

[xiota]

@elextr @eht16 Is warn_on_close_project okay? Or should it be warn_on_project_close?

[eht16]

I think I would prefer warn_on_close_project but don't mind much.

[xiota]

@eht16 The original name I chose was pretty ridiculous: warn_close_save_project.

[xiota]

I just saw... #2863 ... warning dialog when the project file is read-only... Does adding an option to hide that warning get it's own PR, or can it be added to this one?

If favor of combining in one PR:

• They're related in terms of hiding warning related to project files.
• The changes involve the same files, which would create merge conflicts if they're separate PRs.

[elextr]

@xiota Either name for the preference is fine by me.

Personally I am not in favour of #2863, its a strange use-case which works as intended, even if erring on the safe if annoying side, so no it shouldn't be added here.

[xiota]

I decided to rename the option to warn_on_project_close because it would work better if more options are added in the future: warn_on_project_*, warn_on_document_*, etc.

[eht16]

For me this is fine to merge (whith squashed commits).

[xiota]

Force push to rebase and squash commits.

[xiota]

🎉 🎊 🎉 🎊 🎉 🎊