After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 680982 - Default to Recent location
Default to Recent location
Status: RESOLVED OBSOLETE
Product: nautilus
Classification: Core
Component: general
3.4.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on: 682836
Blocks:
 
 
Reported: 2012-08-01 14:12 UTC by William Jon McCann
Modified: 2021-06-18 15:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
all: make Recent the default location, if supported (4.63 KB, patch)
2012-08-01 20:11 UTC, Cosimo Cecchi
reviewed Details | Review

Description William Jon McCann 2012-08-01 14:12:26 UTC
It would be nice for Nautilus to start up with a view that is immediately useful without having to do any navigation or searching.

Showing the Recent view by default would be nice because of the higher likelihood of the visible items being relevant.
Comment 1 Cosimo Cecchi 2012-08-01 20:11:46 UTC
Created attachment 220101 [details] [review]
all: make Recent the default location, if supported

Unfortunately, we seem to have some performance issues at the moment, so this is not really as useful as it would be (not specifically related to recent://, but there's usually quite a bit of data in it).
I think we need to figure those out before switching to that as default.
Comment 2 Cosimo Cecchi 2012-09-19 19:54:02 UTC
Comment on attachment 220101 [details] [review]
all: make Recent the default location, if supported

Removing from the unreviewed patch queue.
Comment 3 Peter 2012-11-16 10:28:51 UTC
Against this!
Default behaviour should be always HOME_DIR. That is was users expects and wants.

A solution for users how want presented "Recent files", could be a startup option.
Comment 4 André Klapper 2014-09-19 10:33:57 UTC
Why did this suddenly become a 3.14 milestone? Removing again. If at all, maybe 3.16 for such a disruptive behavioral change. Plus dependency unresolved.
Comment 5 Allan Day 2014-09-19 10:46:21 UTC
(In reply to comment #4)
> Why did this suddenly become a 3.14 milestone?

Because it is a positive change, and part of the long-term plan for Nautilus. I'll update the milestones to 3.16 when I get chance.

> ... If at all, maybe
> 3.16 for such a disruptive behavioral change.

So you police design decisions now?

> Plus dependency unresolved.

So? The target-milestone is a way of tracking what we'd like to get done.
Comment 6 André Klapper 2014-09-19 11:13:35 UTC
Thanks for clarifying!
So I guess part of the confusion was that 3.16 wasn't available as a milestone in the dropdown and while "long-term" (or 3.16) sounds great, setting "3.14" without further explanation after two years of silence made me feel uncomfortable from a stability PoV - 3.14.0 is only four days away and the 3.14.x series is under UI Freeze anyway.

I've added the 3.16 project milestone and setting it here; under the assumption you don't really want to get this in for 3.14.
Comment 7 Peter 2014-09-21 10:32:48 UTC
Hello!
I see that you want to make thinks faster and more convenient! But please, what ever you do, make it possible to easyly disable this! In general, I'm against this. Why? Because I have reasons and to return to the regualar behaviour, we will have to wait at least another six months:

* A user on a UNIX like operating-system expects to land inside the home-directory (see: every shell, nearly every graphical file-browser, especially Nautilus)
* Most common and usable place is the home-directory
* Nautilus is a file-browser for the hierarchical file-system not an fuzzy-search-store-tool
* "Recent" isn't usable by default, it is not a real location by itself e.g. you can't save there files
* Users get presented a weird list of file and directories. The ordering is likely not to match the currently useful or prefered one by the user (hierarchical by directory, by type, by date).

Let us take the Gtk-File-Choose as an example, I've already got bewildered by the "recent" location:
Inside a random application I want to save my stuff. I expect to be directed to my home-directory or current working-directory by default. There I can immediately save the file or can navigate very fast to a subdirectory. I hit "enter" or click "Save" and I doesn't works! Because the dialog in place defaults (for some unknown reason) to "recent", which is not an existing location. Now I spend time to find the reason why it failed, than looking through the unordered list of recent items (maybe lucky) or have to navigate to my home-directory or any other directory manually.

This behaviour, as far as I know, managed through the application in place itself, but it give a good impression and could be revised anyway.

To be more constructive:
It could speed up things often, to remember the "last working directory" and choose this by start-up. For both, Nautilus and Gtk-File-Chooser! It is likely that a user want's to start working again, where the user ended the work last time. But even this, should be an option to turn [on|off]. In both cases, [on] or [off], there is no question like "where the heck I'am?".
Comment 8 Carlos Soriano 2015-05-13 11:06:10 UTC
->3.18
Comment 9 Carlos Soriano 2015-08-31 11:23:08 UTC
Allan, what should we do?
Comment 10 Carlos Soriano 2015-09-01 14:06:50 UTC
Releasing the 3.18 target.
We discussed it and Recent is still too slow to not be problematic as a default view.
Comment 11 André Klapper 2021-06-18 15:32:57 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version of Files (nautilus), then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/

Thank you for your understanding and your help.