GNOME Bugzilla – Bug 759056
Bug in nautilus-open-terminal extension
Last modified: 2016-02-10 03:05:51 UTC
Hi, I want report a "low level" bug in Nautilus. I'd installed nautilus- open-terminal extension. I use normally the window in list mode; so, you can't encounter "free space" for the right button of the mouse and, consequently, the contextual menu always offers possibilities for folders or archives. If you right click a folder, the option appears, but Terminal will open this folder clicked, not the folder present in window. If you change to icons mode, the mouse can encounter "open space" and the option "Open terminal here" appears. Like reference only, Nemo offers a button permanent for this function in the toolbar, and you can elect view it or not. I think this small bug is easily correctable. Thanks for all the work done. Will
What is actual behavior, and what is the expected behavior?
Hi, André. The actual behavior, in list mode, is that the contextual menu (for obtain the option "Open in terminal") can't shows the option; there is not "free space" in the rows or columns. This way you select only a file or a folder contained in the folder taht you desire open in terminal. If you do right clic on a folder, you will open this folder, not the desired. The zoom in this mode not modify the situation, the rows are united, without space. When you change to icons mode, you obtain "free space" and you can view the option "Open in terminal" rightclicking. No problem! You can open in terminal the visible folder, not other contained. I can't send you images; with the contextual menu opened in Nautilus, don't works "print screen" (with Firefox, i. e., this problem don't occurs). Comment: in Nemo exists a button in the toolbar for this purpose, although don't exist this problem. In the right side of the window, i. e., the contextual menu opens and you can view the option. Thanks a lot for the job, André.
This is a duplicate of bug 744161 "Can't use the gnome-terminal nautilus extension from list view".
*** This bug has been marked as a duplicate of bug 744161 ***