As I mentioned in T61679, this isn't something you can typically disable with artist-oriented apps. The only reason this was an option was that it was very cautiously added very late in Blender's lifetime. I see no reason to have this as an option for end-users.
The real egregious issue is that this dialog isn't supported when doing File > New or File > Open (!!!)
It also does not ask to save unsaved images if you forget to save image data before quitting.
Agree it's fine to remove this.
As a developer it can be convenient not to ask for confirmation if you open/close Blender hundreds of times a day, but I'm not sure if anyone is using it for that reason still.
Cleared means it's cleared in the versioning code so that a future settings can reuse this flag. That was not done here, so you can leave out that comment.
Unless there are artists in the studio or long time users who can rationalize why this is useful, fine to remove it.
I'll probably setup my own key binding for force-quit, since I like this feature when checking bug reports.
Before, superusers could use bpy.ops.wm.quit_blender('EXEC_DEFAULT') to bypass the save quit dialog.
After the implementation of the new quit dialog this no longer worked, however turning off "Prompt Quit" remedied this.
Now that this also will be gone, what are our options to force quit Blender?
I personally open/close Blender so often that I use the feature, but as long as there is a way to make our own operator skip the dialog via invoke then it's fine.
Also got very used to just do Ctrl+Q > D, since the keys are very close. If devs are good with it then +1!
Note that there are 3 people who like to have the ability to quit quickly, I'm still OK to remove it but we don't _have_ to remove if enough people find it useful.
Editing the keymap gets you some of the way there, but still doesn't work if the window manager asks the window to close - so it's not exactly a replacement.
We could provide a Force Quit operator that is hard to trigger by accident except when someone created a keymap entry for it. The normal Quit operator would always show the dialog then.
This way we can also get rid of the "hacks" that people seem to have developed: bpy.ops.wm.quit_blender('EXEC_DEFAULT').
Even if we have a non-hacky code-path for force quit, it could still be a preference.
Bonus points if it doesn't save quit.blend, was testing with very large files recently and quitting was making my computer hang, eg - if you have >2gb file open w/ gzip compression.
Thinking there may be reasons a quit dialog isn't useful, when using Blender as an interactive tool for eg you might not want it (admittedly we don't have interactive mode yet, just saying).
I don't really mind strongly either way, other than the fact that this seems like adding clutter in the code and also the Preferences for an option that artists won't use. We really have a lot of Preferences in Blender, and this seems like one of those things that was made an option just because it was added a later time in development,
We could put all these kinds of things in a Developer section, or could accept the rather neat solution of only showing prompt when invoke is called. This solution avoids the need for a preference.
If we really must keep it, we should probably rename it from Quit Prompt to Save Prompt. It's not a prompt for quitting but a prompt for saving unsaved changes. It should also appear when performing Open or New File commands, which also illustrates that this is not really a Quit Prompt at all.
The real urgent & egregious issue is the File->New and File->Open which misses this save prompt completely.
Closing the window via the window-manager will still show the prompt.
Agree reducing unnecessary options in the preferences is worth doing where possible. The clutter in the code is minimal so I wouldn't worry about that in this case. (many other worse offenders in this respect)
@Campbell Barton (campbellbarton) If some developers need to quit quickly and never have real work to save, they could simply use the operator without invoke. Currently there's already a difference between closing the window and doing File > Quit. One uses a system dialog, and the other uses Blender's built-in dialog.
This particular issue is not a big deal either way, but there's a chance it could help a bit with focusing on improving the save dialog if we double down on having one system, rather than the current mishmash of dialogs that appear only on some OS's, and the preferences to use alternative dialogs.
I say it from an artist point of view. Opening and closing Blender all the time to try things out in library files, characters, props, which I check and study but don't plan to actually save. Maybe casual artist don't use it but those working in real production do this all the time (the lack of an asset manager and overrides is part of the reason though).
We could put all these kinds of things in a Developer section
It's not developer only.
If we really must keep it, we should probably rename it from Quit Prompt to Save Prompt
+1 . This way the dialog can be re-used when creating/opening a new file as well.
A "Force Quit" operator would still be useful though (if the 'exec_default' feels too hacky). One of the ways we use is when sending files to render, we have a "Submit & Quit" to automatically close Blender after the file is sent to the farm, I can see other type of add-ons/farms using a similar workflow.
@Pablo Vazquez (pablovazquez) This patch essentially already has a force quit option. If you add this to the keymap without invoke, there will be no dialog.
I will defer to others on whether to keep this as a separate preference option, or to do it the way this patch suggests. It all seems to be a bit of bikeshedding when compared the real serious issue of it not appearing for File > New and File > Open.