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 664899 - Too verbose column values
Too verbose column values
Status: RESOLVED DUPLICATE of bug 346337
Product: nautilus
Classification: Core
Component: Views: List View
0.x
Other Linux
: Normal enhancement
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-11-27 04:17 UTC by Kirill
Modified: 2011-11-29 03:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Kirill 2011-11-27 04:17:37 UTC 
Fields owner and date look beautiful, but are quite useless since take huge space and do not fit in window (and I hate having windows wider then half of screen).

So for practical usage it is much better to have JUST LOGIN name and SHORTEST DATE/TIME representation (like in /bin/ls -l output), than this quite verbose and too excessive information that is there now. These two fields now take more space than all others, especially considering that there are names noticeably longer than "John Doe".
Comment 1 André Klapper 2011-11-28 16:12:31 UTC 
Which Nautilus version is this about?
What are the steps to get to the dialogs that you talk about?
Comment 2 Kirill 2011-11-28 20:30:19 UTC 
Any version I've ever seen by now, including version 3.2.1. 

It is not dialogue, it is folder view. Open any folder, press Ctrl+2. 

Maybe, one should also change in preferences list of visible columns: Edit|Preferences, tab "List Columns", check "Owner" and "Date Modified" (and/or Date Accessed).

-- 
Thanks!
Comment 3 Cosimo Cecchi 2011-11-29 03:00:37 UTC 
I'm going to close this as a duplicate of bug 346337, which is about having a better string for date formatting.
Not sure about login name vs full name for the owner, but I believe it's just a consequence of bug 410361.

*** This bug has been marked as a duplicate of bug 346337 ***