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 418307 - Keeping the Width of List Columns
Keeping the Width of List Columns
Status: RESOLVED DUPLICATE of bug 410361
Product: nautilus
Classification: Core
Component: Views: List View
2.16.x
Other All
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 438991 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-03-14 18:06 UTC by Satoshi Tanabe
Modified: 2007-12-31 10:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Satoshi Tanabe 2007-03-14 18:06:10 UTC
Hello,

I want Nautilus to always remember the width of List Columns, not only for the current session. Currently it seems Nautilus automatically resizes the Name column corresponding to the width of the longest file name in the current directory, which I don't want. I want to get the fixed width for those columns for all Nautilus sessions.

I want Nautilus to keep the list columns' width like this:
http://img9.imagevenue.com/img.php?image=94262_nautilus_list_column_2_122_145lo.jpg

However, every time I start up Nautilus the list columns look something like this:
http://img138.imagevenue.com/view.php?image=94257_nautilus_list_column_1_122_182lo.jpg

This is messy especially when a directory contains a file with very, very long file name. In this case you need use the horizontal scroll bar to see the other columns.

It works fine after I set/fix the width manually. However, that's only for the current Nautilus session. Each time I start a new Nautilus session, I need to do the same thing again.

Hope this gets fixed.

Best,

Satoshi

Other information:
Comment 1 Susana 2007-08-07 14:50:43 UTC
*** Bug 438991 has been marked as a duplicate of this bug. ***
Comment 2 Cosimo Cecchi 2007-12-31 10:49:11 UTC

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