GNOME Bugzilla – Bug 756688
"nautilus ." doesn't open current directory but ~/
Last modified: 2015-10-31 10:25:52 UTC
In GNOME 3.16 (and for many years before that), I would be able to browse the current directory in nautilus by running: nautilus . This doesn't work any more (it opens the home directory instead) but this works: nautilus `pwd` This is a regression from GNOME 3.16 (probably going back pretty far into GNOME 2).
(In reply to Bastien Nocera from comment #0) > In GNOME 3.16 (and for many years before that), I would be able to browse > the current directory in nautilus by running: > nautilus . Works for me. Can you try killing all instances first? > > This is a regression from GNOME 3.16 (probably going back pretty far into > GNOME 2). I don't understand what "going pretty far into GNOME 2" means here.
(In reply to Carlos Soriano from comment #1) > (In reply to Bastien Nocera from comment #0) > > In GNOME 3.16 (and for many years before that), I would be able to browse > > the current directory in nautilus by running: > > nautilus . > > Works for me. Can you try killing all instances first? It only works for the first call, after that, it only activates the existing window. > > This is a regression from GNOME 3.16 (probably going back pretty far into > > GNOME 2). > > I don't understand what "going pretty far into GNOME 2" means here. That it was working for a looooong time :)
Created attachment 313473 [details] [review] application: specify cwd We are managing all command line options in the main instance. That works always correctly except when resolving relative paths, which are relative the local instance, not the main one. To fix it, set a "cwd" option in the local instance to ensure the relative file paths are resolved in the main instance based on the local instance.
Attachment 313473 [details] pushed as af92c27 - application: specify cwd
pushed to 3.18 as well.
*** Bug 757179 has been marked as a duplicate of this bug. ***