Bug 371837

I can reproduce, thanks for reporting.

The problem is in  ConfirmationsSettingsPage::applySettings()
It is only saving the setting if the setting is checked, but not doing anything if it's unchecked.  Unlike it's neighboring settings, it's not being saved as a simple on/off so I don't know how to deal with it.  I need to look into how this setting is being used and find an appropriate value to set when the checkbox is off.

The reason why you can't simply uncheck the box is because you need to specify the behavior you want if you don't want the confirmation.  When you click on a script, you will get the text, "What do you wish to do with this executable file?", and you have the option to "Open" or "Execute".  In that same dialog there is an option "Do not ask again".  If you check that box, and choose "Open" or "Execute", it will no longer ask for confirmation, and always perform the action that you choose - either "Open" or "Execute".  This will also turn off the "Executing scripts or desktop files" setting.  The problem is if that setting is on, and you turn it off, we don't know what you want to do with the script - "Open" or "Execute".  If you don't want to the confirmation, you'll somehow have to specify if you want to "Open" or "Execute".  I'm not sure what's the best way to fix this.  The setting really should be "Always Execute, Always Open, or Always Ask".

Created attachment 102167 [details]
Suggested improvement for executable file select default behavior

The "Executing scripts or desktop files" option only turns the confirmation
dialog on --- resets it, but only the confirmation dialog can turn itself off. 
Unchecking the checkbox on the Confirmations tab does nothing. And this is done 
to capture the default behavior when someone clicks an executable file.

I see a couple of issues:
1. The remembered behavior is not visible, so the user doesn't know what it is.
2. If the user changes the option (was on, turns off or visa versa), but the 
   user hasn't clicked an executable to get the dialog, the behavior is in
   some sort of a limbo state until the user clicks an executable and selects a 
   default behavior.

A suggested improvement would be to make the default behavior visible on the
"Behavior" tab.  The "Executing scripts or desktop files" confirmation dialog 
would just be a dialog and the user could turn on/off via the checkbox.
Please see the attached image for a simple example.

Created attachment 102172 [details]
suggestion for behavior page

Comment on attachment 102172 [details]
suggestion for behavior page

My suggestion is to remove the setting from the confirmations page and instead add a new section to the behaviors page to set the behavior for executable scripts and desktop files from:  Always Ask, Open, Execute

The reason why I suggest to do it this way is because dolphin activates the file via KRun(KIO) which uses a "behaviourOnLaunch" setting where the valid values are "alwaysAsk", "open", and "execute".  This implementation is a direct mapping to that.  Another reason to do it this way is so that that setting isn't split into two places - "Behavior", and "Confirmation".  If we go with the two separate places, we would then also have to make changes to how that setting is captured.  This would require a lot more changes.

From the usability perspective, Don Nguyen's suggestion to implement a three-option radio group is the only sensible solution, so please go with that.

The original problem should be fixed meanwhile (in the upcoming 18.08.2), the setting should stick:
https://cgit.kde.org/dolphin.git/commit/?h=Applications/18.08&id=5f252da8b58e03b623e56f788ff6d1056269c005

It's still not possible to choose between opening and executing though.

Before we add more options, I'd like to see this setting removed from Dolphin and put in System Settings, which is the correct place for a global setting for KIO. This is tracked by Bug 376992.

*** This bug has been marked as a duplicate of bug 398022 ***

Reopening and updating the title. It is still not possible to choose between "execute" and "open". See also https://phabricator.kde.org/T9932

Git commit 983273924d2887cdccdd7c3618d332b52dc0dad6 by Nate Graham.
Committed on 29/09/2019 at 16:27.
Pushed by ngraham into branch 'master'.

Expose full set of script execution options in settings window

Summary:
Right now the script execution setting is a checkbox, capable only of handling boolean
input. This is not appropriate because there are actually three options available.

Accordingly, this patch replaces the checkbox with a combobox (to save space compared
to radio buttons) that clearly exposes all three options.
FIXED-IN: 19.12.0

Test Plan:
{F7440559}

- All three options do what they say they'll do
- All options get saved properly
- The combobox displays the correct option when the window is loaded
- The {nav Defaults} button resets it to "always ask" as expected

Reviewers: elvisangelaccio, #dolphin, #vdg

Reviewed By: elvisangelaccio, #dolphin

Subscribers: kfm-devel

Tags: #dolphin

Maniphest Tasks: T9932

Differential Revision: https://phabricator.kde.org/D24247

M  +40   -9    src/settings/general/confirmationssettingspage.cpp
M  +2    -1    src/settings/general/confirmationssettingspage.h

https://commits.kde.org/dolphin/983273924d2887cdccdd7c3618d332b52dc0dad6