https://bugs.kde.org/show_bug.cgi?id=429839
--- Comment #10 from David Faure <fa...@kde.org> --- A setter that only makes sense for one value which is the default value, doesn't have a good enough reason to live. What I'm wondering is whether setRunExecutables(true) makes any sense. I did a general lxr search for setRunExecutables\(true\), removed the 3 useless ones in kdepim, and found one case that maybe makes sense: https://lxr.kde.org/source/kde/workspace/plasma-workspace/applets/icon/iconapplet.cpp#0436 I guess if you add a python script as an icon in your plasma panel, you want it to execute without asking "open as text file or execute" every time you click on it. OK, so that's our use case: application launchers. Dolphin, OTOH, still has too many setRunExecutables(true) in my opinion; file managers should use setShowOpenOrExecuteDialog(true) instead. -- You are receiving this mail because: You are watching all bug changes.
