It looks like the decision to remove the function of running binaries and scripts from the Nautilus file manager will be Restored. After some use cases emerged, that is, developers agreed that they needed support, “especially for businesses and content creators,” before making changes.
One such use case is Mention As a restore reason, this is a small “if then that” script for building HTML and PDF files that uses Zenity to display dialog boxes and display notifications to show progress.
I find it a bit weird that use cases are used as examples, because this is certainly not common, such as self-extracting game scripts.
Although currently merge The request (submitted by the same developer who removed the ability to run binaries and scripts earlier this week) allows the binaries and scripts to run as before, and there are some improvements to the Nautilus binaries and script handling in question. What is currently Proposed This feature is regarded as “legacy support”, adding the “Run as Program” context (right-click) menu instead of allowing double-clicking of binary files or scripts.
In the proposal, the menu item “Run as program” should be displayed even if the file is not marked as executable. In this case, a dialog box will be displayed allowing the user to mark the file as trusted and make it executable. Allow it to run:
|Image source: António Fernandes (@)|
Clicking “Run” will close the dialog box and open a terminal window that executes the binary file. This means that even for programs with a GUI, the terminal will be used. This is not completely ideal, so some suggestions were made in the latter part of the discussion, that is, only display the terminal, and automatically close it after running the binary file, so as to provide feedback to the user that something has happened.
According to error report Explaining this change, adding “Run as a program” to the context menu is considered safer, because double-clicking it does not allow the program to run, and provides an alternative solution. It also eliminates the need to know how to make the file executable. This new “implementation by program” old version implementation is currently under discussion. Here, Not the final design decision.
However, this does not include information about what will happen when running *.desktop files.
For *.desktop files, there is a Different suggestions It mentions that running files from the context menu is similar to scripts and binary files, with a confirmation dialog box that warns of risks and sets executable bits, but does not require opening a terminal window.