# Column Widths in List View Don't Save **URL:** \ **Category:** TotalFinder\ **Created:** [September 1, 2014, 1:02pm UTC](https://discuss.binaryage.com/t/column-widths-in-list-view-dont-save/2460 "2014-09-01T13:02:08Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![JimSD](https://discuss.binaryage.com/user_avatar/discuss.binaryage.com/jimsd/32/1942_2.png) [@JimSD](https://discuss.binaryage.com/u/JimSD)\ **Post date:** [September 1, 2014, 1:02pm UTC](https://discuss.binaryage.com/t/column-widths-in-list-view-dont-save/2460/1 "2014-09-01T13:02:08Z")
I have TotalFinder v1.6.9 installed on my iMac using Yosemite beta 2. In List View, I will change the column width for the Name column but when I come back later, it has returned to what I assume is the default width which is too narrow for my tastes. You can set the minimum column width for Column View but not List View. Am I missing how to set default List View column widths? If this is an Apple Finder thing, can you add a feature to TotalFinder to set the minimum width of the Name column in List View? I also have submitted feedback to Apple since this may be a Yosemite thing. Thanks, Jim ---
**Author:** ![jameskachan](https://discuss.binaryage.com/letter_avatar_proxy/v4/letter/j/5f8ce5/32.png) [@jameskachan](https://discuss.binaryage.com/u/jameskachan)\ **Post date:** [October 25, 2014, 7:08pm UTC](https://discuss.binaryage.com/t/column-widths-in-list-view-dont-save/2460/2 "2014-10-25T19:08:57Z")
Bug Report. In List View — Columns are very tight together and changing them doesn’t reflect in new windows nor does setting a new default size. Disabling TotalFfinder corrects the issue. ---
**Author:** ![JimSD](https://discuss.binaryage.com/user_avatar/discuss.binaryage.com/jimsd/32/1942_2.png) [@JimSD](https://discuss.binaryage.com/u/JimSD)\ **Post date:** [October 25, 2014, 7:21pm UTC](https://discuss.binaryage.com/t/column-widths-in-list-view-dont-save/2460/3 "2014-10-25T19:21:46Z")
If you haven’t updated, TotalFinder is now up to v1.6.13. Perhaps that version would wok for you. ---
**Author:** ![jameskachan](https://discuss.binaryage.com/letter_avatar_proxy/v4/letter/j/5f8ce5/32.png) [@jameskachan](https://discuss.binaryage.com/u/jameskachan)\ **Post date:** [October 28, 2014, 5:51pm UTC](https://discuss.binaryage.com/t/column-widths-in-list-view-dont-save/2460/4 "2014-10-28T17:51:36Z")
Latest update (including beta) doesn’t fix this issue. ---
**Author:** ![Kenan\_Mamedoff](https://discuss.binaryage.com/letter_avatar_proxy/v4/letter/k/6a8cbe/32.png) [@Kenan\_Mamedoff](https://discuss.binaryage.com/u/Kenan_Mamedoff)\ **Post date:** [October 28, 2014, 7:40pm UTC](https://discuss.binaryage.com/t/column-widths-in-list-view-dont-save/2460/5 "2014-10-28T19:40:03Z")
Yeah. This issue bothers me so much too. Every new folder is opening like this. I have to change the size of each folder. ![](https://discuss-s3.binaryage.com.s3.amazonaws.com/10220e4d0c34465cd3b16b2af86dfd575c97eac0411d.png) ---
**Author:** ![jameskachan](https://discuss.binaryage.com/letter_avatar_proxy/v4/letter/j/5f8ce5/32.png) [@jameskachan](https://discuss.binaryage.com/u/jameskachan)\ **Post date:** [November 1, 2014, 6:06am UTC](https://discuss.binaryage.com/t/column-widths-in-list-view-dont-save/2460/6 "2014-11-01T06:06:12Z")
Do any of you use Alfred or some other launch to jump to or open a folder? I have listed a step by step process of the issue for me that is, I think, similar to what is posted here. > [@TotalFinder + Alfred error / Finder view setup error](http://discuss.binaryage.com/t/totalfinder-alfred-error-finder-view-setup-error/2827): > > This issue is related to TotalFinder not saving column width view settings in list view. Alfred.app has a protocol that allows it to launch a file or folder with a hotkey. I use this to jump to a folder in Finder for stuff I’m currently working on. When I use this commend to jump to and open a folder, it always displays truncated in list view by default, I can change the columns, but Finder never remembers what I change them to and the next time I open the folder the columns are all crunched … ---
**Author:** ![fza](https://discuss.binaryage.com/user_avatar/discuss.binaryage.com/fza/32/451_2.png) [@fza](https://discuss.binaryage.com/u/fza)\ **Post date:** [November 5, 2014, 4:11pm UTC](https://discuss.binaryage.com/t/column-widths-in-list-view-dont-save/2460/7 "2014-11-05T16:11:06Z")
I’m having this issue, too. Running TF 1.6.16 on OS X 10.10. First I thought this has something to do with asepsis, but the problem remains even after I uninstalled it. I like to use Finder solely in list view mode. Neither does TF’s column width min/max setting have any permanent effect (opening the same folder in another tab opens it with narrow columns again) nor does the “Save as default”-button in the folder settings do what it should. FYI: I just cleaned my HDD from all .DS\_Store files before trying out column width settings. Cheers Felix ---
**Author:** ![bhalejos](https://discuss.binaryage.com/letter_avatar_proxy/v4/letter/b/ad7895/32.png) [@bhalejos](https://discuss.binaryage.com/u/bhalejos)\ **Post date:** [February 14, 2015, 9:54am UTC](https://discuss.binaryage.com/t/column-widths-in-list-view-dont-save/2460/8 "2015-02-14T09:54:29Z")
Has anybody found a fix for column widths not keeping their sizes on List View? Every time I restart my session or my Mac, bam, all columns back to their “default” size! ---
**Author:** ![Rohirm](https://discuss.binaryage.com/letter_avatar_proxy/v4/letter/r/7bcc69/32.png) [@Rohirm](https://discuss.binaryage.com/u/Rohirm)\ **Post date:** [February 21, 2015, 1:03pm UTC](https://discuss.binaryage.com/t/column-widths-in-list-view-dont-save/2460/9 "2015-02-21T13:03:45Z")
Not yet ☹ This problem is really annoying… hope it will be fixed soon. ---
**Author:** ![PhilR](https://discuss.binaryage.com/letter_avatar_proxy/v4/letter/p/3d9bf3/32.png) [@PhilR](https://discuss.binaryage.com/u/PhilR)\ **Post date:** [March 8, 2015, 11:38pm UTC](https://discuss.binaryage.com/t/column-widths-in-list-view-dont-save/2460/10 "2015-03-08T23:38:08Z")
I use List view almost exclusively. Every time I open a Finder window I can’t read most file names because the Name column starts so narrow. So every time I have to click and drag to make it wider. Other columns appear to remember their widths (or maybe I’ve just left them at their defaults). I have uninstalled TotalFinder (temporarily, I hope) because TotalFinder’s numerous benefits don’t overcome this serious shortcoming. I’m adding to this thread to keep it in the developer’s mind so that the issue might be attended to. (TotalFinder 1.6.17. OS X 10.10.2) ---
**Author:** ![PhilR](https://discuss.binaryage.com/letter_avatar_proxy/v4/letter/p/3d9bf3/32.png) [@PhilR](https://discuss.binaryage.com/u/PhilR)\ **Post date:** [March 20, 2015, 8:53pm UTC](https://discuss.binaryage.com/t/column-widths-in-list-view-dont-save/2460/11 "2015-03-20T20:53:35Z")
I know I said above that I uninstalled TotalFinder “because [its] numerous benefits don’t overcome this serious shortcoming.” Well, I found after a while that I couldn’t live without TotalFinder’s wonderful improvements to the Finder. But to illustrate the seriousness of this column width issue, here’s a picture of what my Finder window looks like, when I’m down a couple levels in the folder hierarchy, every time I open a new Finder window. ![](https://discuss-s3.binaryage.com.s3.amazonaws.com/127166c844e78d47e72cf592e4338f380049815ceb94.jpg)You can see that it’s useless, file names completely obscured, and every single time I’ve gotta go up and click and drag to make that Name column much wider. ---
**Author:** ![PhilR](https://discuss.binaryage.com/letter_avatar_proxy/v4/letter/p/3d9bf3/32.png) [@PhilR](https://discuss.binaryage.com/u/PhilR)\ **Post date:** [June 7, 2015, 3:29pm UTC](https://discuss.binaryage.com/t/column-widths-in-list-view-dont-save/2460/12 "2015-06-07T15:29:37Z")
What with all those [resolved] topics that recently appeared, I feel left out and ignored. Without TF, OS X remembers list-view column widths. With TF, columns always start with their default widths. Can’t this be fixed? At least can we get a response from the developer?