Hi all,
When I click on an executable file in Dolphin it now shows me only the option to launch it and no longer to open it in a text editor. Is this a new feature or is something wrong here?
I have "Always Ask" set, but I see the same as OP - I’m asked whether I want to launch the file, but I’m not given the option of opening it in a text editor.
That means it must/should be a bug since the option is still in the settings.
So, a bug report needs to be submitted.
For now, right-clicking and choosing “Open With” should still work.
EDIT:
Just checked. It is the same for me. Curiously, when I set it back to “Run script”, there is no confirmation, so it’s possible this was an intentional change.
I imagine the reasoning would be that if you want to launch an executable, you would double-click (or single-click if you’re carefree like that), and if you want to edit it, you’d right-click and choose “Open With”.
On a technical level, this is the only “promise” of that setting. The option to edit the executable is not part of the “promise”.
It’s not being carefree and you know it. It is a matter of preference.
@pg-tips I’d test but currently I have Dolphin rolled back cause we’re still waiting for the icon preview issue to finally be fixed, so waiting for the update to 26.08.2 or 26.08.3 that’s suppose to finally address the issue.
I originally wanted to say “if ya nasty”, but then I thought, not everyone would understand that because lots of people here are from non-English-speaking countries. So, I used the next “best” thing. Apparently, it’s even more inconsiderate.
This is about the most ironic, “pot calling the kettle” thing I’ve ever seen.
Anyway, at least my comments could be considered as useful, minus the one part you focused on, as usual. Proper irony!
If I simply click on an executable Bash script, I’m asked if it’s OK to launch the file and then – nothing.
If I inspect the user entries in the systemd Journal, then I can see the script’s output.
If I want to see the script’s output live I have to right-click the script’s file and select Actions → “Run it in a Konsole” …
I had 26.08.1 before I downgraded for another issue and this was working fine in it. Now I don’t know if that’s a carry over from having previous versions installed or if only on certain systems a bug crops up.
if it is just a bash that uses STDIN/OUT, this is expected behavior… but if its a bash script that say runs kdialog commands then those commands will execute