I prefer using a gfx command and it should not be added to the API as Richard
said.

if we use a config file can we store it correctly, for example, using a ".cmgui"
directory. I used to dislike having a "CMGUI" file in my home directory.

Do we still have the cmgui.com start-up comfile? Anyone care to say how it is
now used?
We'd use that instead of a "config file"...
Add some gfx command to control the setting?
I don't think it makes sense to add to the API as it is standalone cmgui-
specific...

Don't remove it.  There is an easy compromise.  By default (i.e. after first
install), the "are you sure you want to quit" is enabled, but it has a checkbox
"Always show this confirmation before quitting".  The user then has the option.
Defaults will need to be saved in a config file.  I think if the user wants to
re-enable confirmation, for now, they can edit the config file.

This is open to discussion. I can't speak for others but I tend to work with a
comfile and work should be saved anyway. I find it annoying when you are
tweaking and rerunning a comfile a lot. I would also argue that using a comfile
is best practice.

I put that up in case users accidentally close the application without saving
their works. I guess this has been an annoying feature to some other users too.
I will remove the quit prompt.