Bug 464249 - Cannot set confirmation dialog for deletion to default to 'Yes'
Summary: Cannot set confirmation dialog for deletion to default to 'Yes'
Status: RESOLVED DUPLICATE of bug 462845
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 22.12.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-13 18:18 UTC by David
Modified: 2023-01-13 21:35 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description David 2023-01-13 18:18:22 UTC 
SUMMARY
In the latest versions of Dolphin, the default behavior of Shift+Delete changed to have the option "No" in the confirmation dialog as the default selection (used to be "Yes"). I don't like this option and it doesn't let me configure it to ask for confirmation but have "Yes" as default, only to forego the confirmation altogether.

STEPS TO REPRODUCE
1. Open dolphin.
2. Go to hambuger menu -> Configure -> Configure Dolphin -> General -> Confirmations, and tick 'Deleting files or folders'.
3. Select some file inside dolphin.
4. Press Shift+Delete.

OBSERVED RESULT
The confirmation dialog has option 'No' selected as the default.

EXPECTED RESULT
Perhaps this is a reasonable default behavior, but it should let me configure it otherwise. The dialog itself **is** already a confirmation of my action - I don't want to pass through 2 confirmation actions (changing the option and then pressing enter) in order to execute the action.

SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7
Kernel Version: 5.18.0-4-amd64 (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 2700 Eight-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX Vega
Manufacturer: Acer
Product Name: Predator PH517-61
System Version: V1.09

ADDITIONAL INFORMATION
Comment 1 Patrick Silva 2023-01-13 21:35:08 UTC 

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