"Open in terminal" has disappeared from the file explorer
In Tails 4.0 the menu option to open the terminal in the current directory by right clicking on empty space within the file explorer has disappeared.
This significantly hinders those that want to run scripts or develop on Tails.
#5 Updated by tobtoht 2019-10-31 09:59:56
> To execute a script you can drag and drop it from the Files browser into Terminal. See screenshot in attachment.
No, this way dependencies that reside in the same directory as the script will not be found.
Previously there was a consistent way to instruct users on how to start a script regardless of where they chose to save it: “Move to the directory that contains the script in the file explorer, open in terminal then run this command.”
Now I need to explain what cd is and how to use it to navigate around the terminal to get to the directory where they saved the script.
#8 Updated by tobtoht 2019-10-31 19:50:21
Thanks for taking the time to come up with some alternatives.
>What about this: cd + “drag’n’drop the folder into the Terminal”?
It’s still another step that I’d rather avoid having to explain.
Dragging a bookmark (e.g. Persistent) into the terminal doesn’t work. I can see users getting confused by this.
>Or are there important use cases that require this feature before persistence is set up?
Some users download the scripts when needed and use them without persistence.
>One can get this functionality back by adding nautilus-extension-gnome-terminal to their Additional Software.
>Is this good enough?
I’d also rather not have to explain how to enable additional software persistence, run two commands to install
nautilus-extension-gnome-terminal, just to enable a basic feature.
Consistency is key when it comes to support. When a typical support query looks like: “help can’t open script”, having to ask whether or not a user has enabled persistence, has installed the nautilus extension, knows how to change directories with the terminal, is sure they are in the right directory, etc is a cumbersome process.
Was there any specific reasoning for the removal of this feature or is this a change from upstream?
#9 Updated by intrigeri 2019-11-01 07:00:27
> Was there any specific reasoning for the removal of this feature or is this a change from upstream?
This functionality was previously forcibly installed; then it was moved to a new, separate package (
nautilus-extension-gnome-terminal), which we did not automatically get since we don’t install Recommends by default (and the only reason why this would get installed is that
From an engineering perspective, I see no particular problem with installing
nautilus-extension-gnome-terminal by default.
Given we don’t ship
changelog.Debian.gz in our images, it’s a matter of a few dozens KiB, maximum.
sajolida, should we “just” go ahead and add this package?
#13 Updated by sajolida 2019-11-06 15:07:32
I tried adding nautilus-extension-gnome-terminal to my Tails and I still can’t see the “Open in Terminal” entry when doing right-click on a script in the Files browser.
I also took care of killing any
nautilus process around and restarted GNOME Shell (Alt+F2, “R”).
#15 Updated by intrigeri 2019-11-09 09:43:06
> I tried adding nautilus-extension-gnome-terminal to my Tails and I still can’t see the “Open in Terminal” entry when doing right-click on a script in the Files browser.
Indeed, even with
nautilus-extension-gnome-terminal installed, just like in Tails 3.16, this entry is only present in the menu when right-clicking in an empty space in Nautilus (which is the lost functionality this ticket initially complained about) or on a folder.
May we scope this ticket to fixing the regression only? Or do you want to extend its scope to “Open in Terminal is not proposed when right-clicking on a script”?
#17 Updated by intrigeri 2019-11-09 09:45:20
- Target version set to Tails_4.1
> Seeing how loud this issue (and related ones) are in 4.0 and that it’s a regression, I think that it deserves “Elevated”.
I’ve put it on the FT’s plate (otherwise, having higher than normal priority won’t yield the effect you’re hoping for) and set its target version to 4.1.
#19 Updated by intrigeri 2019-11-10 10:00:16
- Status changed from In Progress to Needs Validation
- Assignee deleted (
> May we scope this ticket to fixing the regression only?
I’m optimistically assuming the answer will be yes. Built from the branch, tested manually, works as expected. I did not wait for Jenkins to run the test suite yet as I’m confident this can’t possibly break anything, and if it does, that’s trivial to revert.