New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

list view column width not remembered. #626

Closed
splace opened this Issue Jun 6, 2014 · 56 comments

Comments

Projects
None yet
@splace

splace commented Jun 6, 2014

just resets columns to being all the same width on each launch, noticed after upgrade from mint 16 to 17.

@AdelSulaiman

This comment has been minimized.

Show comment
Hide comment
@AdelSulaiman

AdelSulaiman Jul 30, 2014

Opening Nemo in List View gives equal width to all columns, with a bit more space to the Name column.
Resizing the column widths will not stick when you close and reopen Nemo.

Why is this a problem? You can only see a small part of file names in the Name column. So every time you open Nemo, you have to resize the column.

As splace mentioned, this only became a problem after Mint 16. To be clear, I did a clean install of Mint 17.

AdelSulaiman commented Jul 30, 2014

Opening Nemo in List View gives equal width to all columns, with a bit more space to the Name column.
Resizing the column widths will not stick when you close and reopen Nemo.

Why is this a problem? You can only see a small part of file names in the Name column. So every time you open Nemo, you have to resize the column.

As splace mentioned, this only became a problem after Mint 16. To be clear, I did a clean install of Mint 17.

@martin-wagner

This comment has been minimized.

Show comment
Hide comment
@martin-wagner

martin-wagner Aug 21, 2014

Any updates regarding this?
Worked without any problems in Nemo 1.8 and -you will hate me- almost twenty years ago in Win 95 :-)

martin-wagner commented Aug 21, 2014

Any updates regarding this?
Worked without any problems in Nemo 1.8 and -you will hate me- almost twenty years ago in Win 95 :-)

@to-ba

This comment has been minimized.

Show comment
Hide comment
@to-ba

to-ba Dec 18, 2014

This problem still exist in Nemo 2.4.4
Nemo does not save the custom column width.
In every new tab, window and after restart Nemo all columns have the same width.

to-ba commented Dec 18, 2014

This problem still exist in Nemo 2.4.4
Nemo does not save the custom column width.
In every new tab, window and after restart Nemo all columns have the same width.

@1enn0

This comment has been minimized.

Show comment
Hide comment
@1enn0

1enn0 Dec 19, 2014

I can confirm this. Running Nemo 2.4.4 as well.

1enn0 commented Dec 19, 2014

I can confirm this. Running Nemo 2.4.4 as well.

@AdelSulaiman

This comment has been minimized.

Show comment
Hide comment
@AdelSulaiman

AdelSulaiman Dec 20, 2014

Issue #796 seems to describe the same problem.

AdelSulaiman commented Dec 20, 2014

Issue #796 seems to describe the same problem.

@gianlucapettinello

This comment has been minimized.

Show comment
Hide comment
@gianlucapettinello

gianlucapettinello Dec 28, 2014

A primitive workaround at least to start nemo with increased "name" column width is to modify nemo-list-view.c:
gtk_tree_view_column_set_min_width (view->details->file_name_column, 125);
into
gtk_tree_view_column_set_min_width (view->details->file_name_column, 300);

Very unelegant but at least better than today. I think it is pretty easy to code a value that is remembered between sessions, but I'm not so good programmer

gianlucapettinello commented Dec 28, 2014

A primitive workaround at least to start nemo with increased "name" column width is to modify nemo-list-view.c:
gtk_tree_view_column_set_min_width (view->details->file_name_column, 125);
into
gtk_tree_view_column_set_min_width (view->details->file_name_column, 300);

Very unelegant but at least better than today. I think it is pretty easy to code a value that is remembered between sessions, but I'm not so good programmer

@hub2git

This comment has been minimized.

Show comment
Hide comment
@hub2git

hub2git Jan 1, 2015

Thanks for the reply. How do I modify nemo-list-view.c?

hub2git commented Jan 1, 2015

Thanks for the reply. How do I modify nemo-list-view.c?

@Filbuntu

This comment has been minimized.

Show comment
Hide comment
@Filbuntu

Filbuntu May 15, 2015

@gianlucapettinello, @hub2git Where do I find nemo-list-view.c on the computer and how do I modify the file? Thanks for your help because this bug is annoying.

Filbuntu commented May 15, 2015

@gianlucapettinello, @hub2git Where do I find nemo-list-view.c on the computer and how do I modify the file? Thanks for your help because this bug is annoying.

@splace

This comment has been minimized.

Show comment
Hide comment
@splace

splace May 15, 2015

this isn't a practical workaround,
because that is a 'c' source file, although it is just accessing an API, so could be written in a script language, it is not, so you would need to get all the other sources, and compile them with the right settings then replace the executables, and repeat the whole thing each time nemo was updated.
people don’t do this.
people sometimes do, fork the repo, and make the changes/compile/maintain/repeat etc. but still ugly.
or
get to be able to contribute to the project, and make the changes, but the reason this isn't already done is that its not the 'real' solution, which is to figure out how it got broke, ideally it would have been noticed and acted on quickly, now it cant just be reverted because of the web of other changes after it, clearly not interesting enough to have been looked at yet, although the other linked bugs might get it pushed up in priority.

splace commented May 15, 2015

this isn't a practical workaround,
because that is a 'c' source file, although it is just accessing an API, so could be written in a script language, it is not, so you would need to get all the other sources, and compile them with the right settings then replace the executables, and repeat the whole thing each time nemo was updated.
people don’t do this.
people sometimes do, fork the repo, and make the changes/compile/maintain/repeat etc. but still ugly.
or
get to be able to contribute to the project, and make the changes, but the reason this isn't already done is that its not the 'real' solution, which is to figure out how it got broke, ideally it would have been noticed and acted on quickly, now it cant just be reverted because of the web of other changes after it, clearly not interesting enough to have been looked at yet, although the other linked bugs might get it pushed up in priority.

@mtwebster

This comment has been minimized.

Show comment
Hide comment
@mtwebster

mtwebster May 15, 2015

Member

There is a large history behind this issue - it's definitely not uninteresting, but there's not an easy fix that pleases everyone - it's a no-win scenario.

Brief timeline:

  • Nemo remembers list view widths. People complain they can't reduce widths of some columns to fit a useful list into a small window, and hate having horizontal scroll bars.
  • We try to accomodate and make columns able to be made very small if desired. Oh, but Gtk got changed in the mean time, and the list view class we use is actually now broken and we're unable to implement this. You can resize as much as you want, but you never get a horizontal scrollbar, ever. So columns just disappear if you make other columns too wide. The Gtk change also means we can't even go back to the way things originally were - we're on an island.
  • The current behavior is implemented as a temporary fix until we figure out what to do.
  • We patch the gtk we ship with Mint to 'band-aid' the problem (actually a rejected patch someone submitted to the Gnome devs). There's a PR (#611) to restore the original behavior (see list item 1). This of course will only be useful to people that liked the original behavior, but doesn't improve anything, and only applies to those running this patched Gtk (Mint 17 users).
  • You are here.

So, yeah it's been kicked under the rug a bit, and that's our fault. But there's not been a clear solution either. I'll take a look again in the next couple weeks if I can fix the issue at hand here - remembering widths - before 2.6.

Member

mtwebster commented May 15, 2015

There is a large history behind this issue - it's definitely not uninteresting, but there's not an easy fix that pleases everyone - it's a no-win scenario.

Brief timeline:

  • Nemo remembers list view widths. People complain they can't reduce widths of some columns to fit a useful list into a small window, and hate having horizontal scroll bars.
  • We try to accomodate and make columns able to be made very small if desired. Oh, but Gtk got changed in the mean time, and the list view class we use is actually now broken and we're unable to implement this. You can resize as much as you want, but you never get a horizontal scrollbar, ever. So columns just disappear if you make other columns too wide. The Gtk change also means we can't even go back to the way things originally were - we're on an island.
  • The current behavior is implemented as a temporary fix until we figure out what to do.
  • We patch the gtk we ship with Mint to 'band-aid' the problem (actually a rejected patch someone submitted to the Gnome devs). There's a PR (#611) to restore the original behavior (see list item 1). This of course will only be useful to people that liked the original behavior, but doesn't improve anything, and only applies to those running this patched Gtk (Mint 17 users).
  • You are here.

So, yeah it's been kicked under the rug a bit, and that's our fault. But there's not been a clear solution either. I'll take a look again in the next couple weeks if I can fix the issue at hand here - remembering widths - before 2.6.

@Filbuntu

This comment has been minimized.

Show comment
Hide comment
@Filbuntu

Filbuntu May 15, 2015

Hi splace! Thank you very much for your explanation. I won't compile it as I don't know how ;-).
Hi Michael! Thanks a lot for the helpful and hopeful post. It is good to know the history behind it. We hope there will be a possible fix! I switched from Nautilus to Nemo (using Xubuntu and the ppa:webupd8team/nemo) and I really like Nemo better than Nautilus. "But the column width remembering" is really important for me as I have to change the column width dozens of times a day with the current setting. Thanks for your work on this in advance!

Filbuntu commented May 15, 2015

Hi splace! Thank you very much for your explanation. I won't compile it as I don't know how ;-).
Hi Michael! Thanks a lot for the helpful and hopeful post. It is good to know the history behind it. We hope there will be a possible fix! I switched from Nautilus to Nemo (using Xubuntu and the ppa:webupd8team/nemo) and I really like Nemo better than Nautilus. "But the column width remembering" is really important for me as I have to change the column width dozens of times a day with the current setting. Thanks for your work on this in advance!

@AdelSulaiman

This comment has been minimized.

Show comment
Hide comment
@AdelSulaiman

AdelSulaiman May 16, 2015

@mtwebster Your explanation is both clear and welcome, and your willingness to have a look at the issue at hand much appreciated. Thanks!

AdelSulaiman commented May 16, 2015

@mtwebster Your explanation is both clear and welcome, and your willingness to have a look at the issue at hand much appreciated. Thanks!

@martinrotter

This comment has been minimized.

Show comment
Hide comment
@martinrotter

martinrotter May 16, 2015

This bug is blocker for me. I switched to double commander and will probably never come back. :)

martinrotter commented May 16, 2015

This bug is blocker for me. I switched to double commander and will probably never come back. :)

@Filbuntu

This comment has been minimized.

Show comment
Hide comment
@Filbuntu

Filbuntu Jun 1, 2015

@mtwebster Hi Michael! Is there any happy news about this issue? Eagerly waiting ;-).

Filbuntu commented Jun 1, 2015

@mtwebster Hi Michael! Is there any happy news about this issue? Eagerly waiting ;-).

@Filbuntu

This comment has been minimized.

Show comment
Hide comment
@Filbuntu

Filbuntu Jul 20, 2015

@mtwebster Hi Michael! What is the status? Is it possible to fix or is impossible or does it take more time as expected? Hopefully this bug will soon stop to be a "blocker".

Filbuntu commented Jul 20, 2015

@mtwebster Hi Michael! What is the status? Is it possible to fix or is impossible or does it take more time as expected? Hopefully this bug will soon stop to be a "blocker".

@gunwald

This comment has been minimized.

Show comment
Hide comment
@gunwald

gunwald Jul 23, 2015

Hey guys, if there isn't a solution to make nemo remember the width, I would suggest to work around the issue as the crazy nautilus guys do: Make the name column larger (50% is what I would suggest) and the time and size columns smaller. To be honest, as it is, the list view is almost unusable. And remember: we're relying upon you, because if not we have to use nautilus again, and then we got to kill our self to not become a madman!

gunwald commented Jul 23, 2015

Hey guys, if there isn't a solution to make nemo remember the width, I would suggest to work around the issue as the crazy nautilus guys do: Make the name column larger (50% is what I would suggest) and the time and size columns smaller. To be honest, as it is, the list view is almost unusable. And remember: we're relying upon you, because if not we have to use nautilus again, and then we got to kill our self to not become a madman!

@Filbuntu

This comment has been minimized.

Show comment
Hide comment
@Filbuntu

Filbuntu Jul 23, 2015

@gunwald Thanks for the comment. Can an individual (like me) use your workaround (make the name column larger, ...) or is it up to the developers for a next Nemo version? I had to go back to Nautilus because of this bug, but I hope to return to Nemo sooner than later.

Filbuntu commented Jul 23, 2015

@gunwald Thanks for the comment. Can an individual (like me) use your workaround (make the name column larger, ...) or is it up to the developers for a next Nemo version? I had to go back to Nautilus because of this bug, but I hope to return to Nemo sooner than later.

@to-ba

This comment has been minimized.

Show comment
Hide comment
@to-ba

to-ba Jul 23, 2015

Before going to Nautilus you can use caja. This is my workaround to solve the problem.
Caja is also a Nautilus fork but with all the missing features from the current Nautilus. Ans without the Nemo issue. :-)

to-ba commented Jul 23, 2015

Before going to Nautilus you can use caja. This is my workaround to solve the problem.
Caja is also a Nautilus fork but with all the missing features from the current Nautilus. Ans without the Nemo issue. :-)

@robertc

This comment has been minimized.

Show comment
Hide comment
@robertc

robertc Aug 15, 2015

I don't really care whether or not it remembers the width, just make Name the widest column by default instead of Date Modified.

robertc commented Aug 15, 2015

I don't really care whether or not it remembers the width, just make Name the widest column by default instead of Date Modified.

@Filbuntu

This comment has been minimized.

Show comment
Hide comment
@Filbuntu

Filbuntu Aug 16, 2015

@robertc That sounds like a possible workaround. How do you set the Name column as the widest? I did not find this possibility in the preferences.

Filbuntu commented Aug 16, 2015

@robertc That sounds like a possible workaround. How do you set the Name column as the widest? I did not find this possibility in the preferences.

@jensb

This comment has been minimized.

Show comment
Hide comment
@jensb

jensb Sep 2, 2015

Contributor

@robertc, by "make Name the widest column by default" do you mean:

  • make all columns except "Name" as narrow as possible without them having horizontal scrollbars, and
  • make the Name column just use the rest of the available window width, and
  • resize the width of only the Name column if the width of the window is changed?

This is how PcManFM (of Lubuntu) and SpaceFM do it and I really like this behvaiour, I think it would fit most expectations. Also when using this approach it is not necessary to remember the column widths - it is sufficient to just remember the window width.

Contributor

jensb commented Sep 2, 2015

@robertc, by "make Name the widest column by default" do you mean:

  • make all columns except "Name" as narrow as possible without them having horizontal scrollbars, and
  • make the Name column just use the rest of the available window width, and
  • resize the width of only the Name column if the width of the window is changed?

This is how PcManFM (of Lubuntu) and SpaceFM do it and I really like this behvaiour, I think it would fit most expectations. Also when using this approach it is not necessary to remember the column widths - it is sufficient to just remember the window width.

@Frederick888

This comment has been minimized.

Show comment
Hide comment
@Frederick888

Frederick888 Sep 16, 2015

@jensb This is exactly what I want as well. Columns like size, type or date apparently do not need so much space.

Frederick888 commented Sep 16, 2015

@jensb This is exactly what I want as well. Columns like size, type or date apparently do not need so much space.

@robertc

This comment has been minimized.

Show comment
Hide comment
@robertc

robertc Sep 16, 2015

@jensb Yes, that's what I meant. That seems to be the behaviour of the Date Modified column at the moment (I have name, size, type, date modified columns visible).

robertc commented Sep 16, 2015

@jensb Yes, that's what I meant. That seems to be the behaviour of the Date Modified column at the moment (I have name, size, type, date modified columns visible).

@jensb

This comment has been minimized.

Show comment
Hide comment
@jensb

jensb Sep 17, 2015

Contributor

This works, but ONLY if I Double click on both mtime and size column right borders to auto-resize them EVERY time I open up a new Nemo window.
After this action, resizing Nemo's window will auto-resize the file name width. If I perform any other action within Nemo (sorting, changing directories, etc.) before doing this, the column widths will stay fixed and cause horizontal scrollbars when the window is changed.
So it seems there is a fix but it doesn't work 100% yet. Can this be fixed?

Contributor

jensb commented Sep 17, 2015

This works, but ONLY if I Double click on both mtime and size column right borders to auto-resize them EVERY time I open up a new Nemo window.
After this action, resizing Nemo's window will auto-resize the file name width. If I perform any other action within Nemo (sorting, changing directories, etc.) before doing this, the column widths will stay fixed and cause horizontal scrollbars when the window is changed.
So it seems there is a fix but it doesn't work 100% yet. Can this be fixed?

@jensb

This comment has been minimized.

Show comment
Hide comment
@jensb

jensb Oct 14, 2015

Contributor

So what would have to be done to make this the default behaviour (and remember column widths if set once)?

Contributor

jensb commented Oct 14, 2015

So what would have to be done to make this the default behaviour (and remember column widths if set once)?

@jensb

This comment has been minimized.

Show comment
Hide comment
@jensb

jensb Nov 16, 2015

Contributor

The update of Nemo 2.8.4 has removed the ability to double click on a column heading separator to auto-resize it like described above. Also, date and size columns do not stick to the right window border any more afterwards. Also column widths are still not remembered between windows and sessions. Is this issue being actively worked on? I would be very happy. :) Please give us a status. Thank you!

Contributor

jensb commented Nov 16, 2015

The update of Nemo 2.8.4 has removed the ability to double click on a column heading separator to auto-resize it like described above. Also, date and size columns do not stick to the right window border any more afterwards. Also column widths are still not remembered between windows and sessions. Is this issue being actively worked on? I would be very happy. :) Please give us a status. Thank you!

@octohedron

This comment has been minimized.

Show comment
Hide comment
@octohedron

octohedron Mar 15, 2016

The current state of the Nemo Column size on details view not being persistent pretty much makes it unusable, look at this:

image

How is it possible that you decided the Size column to take as much space as the Name column when 99.9% of the time, the filename is going to be larger than the Size? I've literally wasted hours resizing the columns, every time i open the program i have to manually resize it again to see the filenames. Please do something or everyone is going to ditch Nemo for a smarter file manager.

octohedron commented Mar 15, 2016

The current state of the Nemo Column size on details view not being persistent pretty much makes it unusable, look at this:

image

How is it possible that you decided the Size column to take as much space as the Name column when 99.9% of the time, the filename is going to be larger than the Size? I've literally wasted hours resizing the columns, every time i open the program i have to manually resize it again to see the filenames. Please do something or everyone is going to ditch Nemo for a smarter file manager.

@AdelSulaiman

This comment has been minimized.

Show comment
Hide comment
@AdelSulaiman

AdelSulaiman Mar 16, 2016

This thread is getting longer and longer. Already 19 participants. The issue was reported almost 2 years ago, but nothing about the described odd behavior of Nemo has changed since.

@mtwebster you've mentioned that this is not an easy fix, that you would try to see if you can fix things, but we have not heard from you since.

Is there any chance this will get fixed soon, we are a bit in the dark here. Could one of the devs give an update please? That would be much appreciated.

I keep sticking with Nemo, but frankly, this behavior of Nemo is starting to get on my nerves.

AdelSulaiman commented Mar 16, 2016

This thread is getting longer and longer. Already 19 participants. The issue was reported almost 2 years ago, but nothing about the described odd behavior of Nemo has changed since.

@mtwebster you've mentioned that this is not an easy fix, that you would try to see if you can fix things, but we have not heard from you since.

Is there any chance this will get fixed soon, we are a bit in the dark here. Could one of the devs give an update please? That would be much appreciated.

I keep sticking with Nemo, but frankly, this behavior of Nemo is starting to get on my nerves.

@mtwebster

This comment has been minimized.

Show comment
Hide comment
@mtwebster

mtwebster Mar 16, 2016

Member

This is fixed for nemo 3.0 - see b001de9

The only reason I haven't merged that branch into master yet is I have not been able to fix the issue in LMDE and Mint 17 yet. Because of the nature of this issue/behavior and how it has evolved over Gtk versions, that is proving difficult. Whatever fix I implement there I want to be sure will run on non-modified Gtk libraries, and behave in the same way across the board, or at least as closely as possible.

I left this bug open because I haven't merged with master yet. This will be done one way or the other prior to the next release.

Member

mtwebster commented Mar 16, 2016

This is fixed for nemo 3.0 - see b001de9

The only reason I haven't merged that branch into master yet is I have not been able to fix the issue in LMDE and Mint 17 yet. Because of the nature of this issue/behavior and how it has evolved over Gtk versions, that is proving difficult. Whatever fix I implement there I want to be sure will run on non-modified Gtk libraries, and behave in the same way across the board, or at least as closely as possible.

I left this bug open because I haven't merged with master yet. This will be done one way or the other prior to the next release.

@Filbuntu

This comment has been minimized.

Show comment
Hide comment
@Filbuntu

Filbuntu Mar 17, 2016

@mtwebster Thanks a lot for the encouraging update. Hopefully the last
difficulties can be overcome soon.

Filbuntu commented Mar 17, 2016

@mtwebster Thanks a lot for the encouraging update. Hopefully the last
difficulties can be overcome soon.

@AdelSulaiman

This comment has been minimized.

Show comment
Hide comment
@AdelSulaiman

AdelSulaiman Mar 17, 2016

@mtwebster Great update and good news. When can we expect the release of Nemo 3.0? Will it be part of Mint 18 in May/June or are we thinking long(er) term?
Thanks for the quick response, by the way, and especially for all of your efforts as a developer.

AdelSulaiman commented Mar 17, 2016

@mtwebster Great update and good news. When can we expect the release of Nemo 3.0? Will it be part of Mint 18 in May/June or are we thinking long(er) term?
Thanks for the quick response, by the way, and especially for all of your efforts as a developer.

@mxmlnkn

This comment has been minimized.

Show comment
Hide comment
@mxmlnkn

mxmlnkn Apr 18, 2016

@mtwebster: Thanks for your effort!

I'm no expert, but the commit you linked looks like it only changes the initial size, but the original bug report was about the column width not being remembered. Because I have the problem that I wanted to adjust the size of a column (because the size column was too wide), and after going in a subfolder, then going back, the column width had been reset to their initial state with the size column being too wide.

mxmlnkn commented Apr 18, 2016

@mtwebster: Thanks for your effort!

I'm no expert, but the commit you linked looks like it only changes the initial size, but the original bug report was about the column width not being remembered. Because I have the problem that I wanted to adjust the size of a column (because the size column was too wide), and after going in a subfolder, then going back, the column width had been reset to their initial state with the size column being too wide.

mtwebster added a commit to mtwebster/nemo that referenced this issue Apr 29, 2016

nemo-list-view.c: Fix initial column sizing - expand the filename
column only to fill available space.  Other columns will start with
their natural size.

Fixes linuxmint#626
Fixes linuxmint#984 as a bonus
Fixes half of linuxmint#938 (the misplaced edit box)

TODO: This currently breaks nemo in Mint
betsy and mint 17 need a gtk revert of:
linuxmint/gtk@30f6687
with possibly an #ifdef or two.

@mtwebster mtwebster closed this in 438f5ac Apr 30, 2016

@mtwebster

This comment has been minimized.

Show comment
Hide comment
@mtwebster

mtwebster Apr 30, 2016

Member

@mxmlnkn The column width has never been remembered (I had originally thought this also but never verified it at the time - i apologize if this seemed to be misleading) - the new behavior across the board (for different distros) should be that the non-name columns should start out at their natural minimum size, with the name column expanding to fill the remaining space. You should still be able to resize columns smaller than their normal size, down to a certain minimum (this was the original thing that was frustratingly lacking early on, and led down this path to begin with).

Member

mtwebster commented Apr 30, 2016

@mxmlnkn The column width has never been remembered (I had originally thought this also but never verified it at the time - i apologize if this seemed to be misleading) - the new behavior across the board (for different distros) should be that the non-name columns should start out at their natural minimum size, with the name column expanding to fill the remaining space. You should still be able to resize columns smaller than their normal size, down to a certain minimum (this was the original thing that was frustratingly lacking early on, and led down this path to begin with).

@fcastilloec

This comment has been minimized.

Show comment
Hide comment
@fcastilloec

fcastilloec May 3, 2016

So are these fixes schedule to be released for nemo 3.0? If so, will that be done on time for the next Mint release? or hopefully even before that?

fcastilloec commented May 3, 2016

So are these fixes schedule to be released for nemo 3.0? If so, will that be done on time for the next Mint release? or hopefully even before that?

@geckolinux

This comment has been minimized.

Show comment
Hide comment
@geckolinux

geckolinux May 3, 2016

I'm now running Nemo 3.0 on openSUSE, and it still doesn't remember column width. I have to resize the directory name column every time I open Nemo to accommodate the width of the names. :(

geckolinux commented May 3, 2016

I'm now running Nemo 3.0 on openSUSE, and it still doesn't remember column width. I have to resize the directory name column every time I open Nemo to accommodate the width of the names. :(

@herrdeh

This comment has been minimized.

Show comment
Hide comment
@herrdeh

herrdeh commented May 23, 2016

me2

@rphair

This comment has been minimized.

Show comment
Hide comment
@rphair

rphair May 23, 2016

This is an important workflow issue for me as well. I agree with the behaviour in b001de9 - will it be confirmed here when this patch is included in 3.0? For instance we can get Cinnamon 3.0 on other distros (e.g. Ubuntu) but installing Cinnamon is a lot of overhead especially when we don't know if it includes the patch.

rphair commented May 23, 2016

This is an important workflow issue for me as well. I agree with the behaviour in b001de9 - will it be confirmed here when this patch is included in 3.0? For instance we can get Cinnamon 3.0 on other distros (e.g. Ubuntu) but installing Cinnamon is a lot of overhead especially when we don't know if it includes the patch.

@mtwebster

This comment has been minimized.

Show comment
Hide comment
@mtwebster

mtwebster May 23, 2016

Member

This is in Nemo since 3.0.1. I have no control over releases and updates in distros other than Mint. It will for sure be in Mine 18. It is currently in the Cinnamon/Nemo nightly PPA (ppa:gwendal-lebihan-dev/cinnamon-nightly), but I have no idea about other unofficial PPA's for Ubuntu (of which there are a number)

Member

mtwebster commented May 23, 2016

This is in Nemo since 3.0.1. I have no control over releases and updates in distros other than Mint. It will for sure be in Mine 18. It is currently in the Cinnamon/Nemo nightly PPA (ppa:gwendal-lebihan-dev/cinnamon-nightly), but I have no idea about other unofficial PPA's for Ubuntu (of which there are a number)

@odigity

This comment has been minimized.

Show comment
Hide comment
@odigity

odigity Jun 1, 2016

Does anyone know of an easy way to install Nemo 3.0.1 on Ubuntu 16.04? I'm dying to get this fix.

odigity commented Jun 1, 2016

Does anyone know of an easy way to install Nemo 3.0.1 on Ubuntu 16.04? I'm dying to get this fix.

@rphair

This comment has been minimized.

Show comment
Hide comment
@rphair

rphair Jun 1, 2016

@odigity in case it helps keep this thread clear for the specific Nemo issue, there is some discussion of that in the comments here.

rphair commented Jun 1, 2016

@odigity in case it helps keep this thread clear for the specific Nemo issue, there is some discussion of that in the comments here.

@tp0

This comment has been minimized.

Show comment
Hide comment
@tp0

tp0 Jun 1, 2016

@odigity See: http://www.webupd8.org/2016/04/how-to-install-cinnamon-30-in-ubuntu.html

EDIT: I thought the question was about installing Cinnamon & Nemo in Ubuntu 16.04.

tp0 commented Jun 1, 2016

@odigity See: http://www.webupd8.org/2016/04/how-to-install-cinnamon-30-in-ubuntu.html

EDIT: I thought the question was about installing Cinnamon & Nemo in Ubuntu 16.04.

@rphair

This comment has been minimized.

Show comment
Hide comment
@rphair

rphair Jun 1, 2016

@tp0 I posted on the aforementioned comments what happens when you try to install the Cinnamon 3.0 Nero on Ubuntu 16.04: the Unity desktop is ruined when Nero manages the icons. Apologies to the developer for another off topic message but a lot of users who need the "list column view" fixed are running into this issue repeatedly (to avoid duplication of effort), please correct me if I'm wrong but Nero 3.0 does not work outside of Cinnamon.

rphair commented Jun 1, 2016

@tp0 I posted on the aforementioned comments what happens when you try to install the Cinnamon 3.0 Nero on Ubuntu 16.04: the Unity desktop is ruined when Nero manages the icons. Apologies to the developer for another off topic message but a lot of users who need the "list column view" fixed are running into this issue repeatedly (to avoid duplication of effort), please correct me if I'm wrong but Nero 3.0 does not work outside of Cinnamon.

@mtwebster

This comment has been minimized.

Show comment
Hide comment
@mtwebster

mtwebster Jun 1, 2016

Member

Nemo does not work under Unity only, without patches. Ubuntu's Nautilus, the default file manager, is patched so that it also draws the desktop background in Unity. Nemo no longer does this (and hasn't for a long time). I believe the webupd8 version of Nemo has these patches as well.

Member

mtwebster commented Jun 1, 2016

Nemo does not work under Unity only, without patches. Ubuntu's Nautilus, the default file manager, is patched so that it also draws the desktop background in Unity. Nemo no longer does this (and hasn't for a long time). I believe the webupd8 version of Nemo has these patches as well.

@rphair

This comment has been minimized.

Show comment
Hide comment
@rphair

rphair Jun 1, 2016

At this time, Nemo 2.8.7 from the first link (ppa:webupd8team/nemo) has those patches, but Nemo 3.0.1 from the second link (ppa:embrosyn/cinnamon) does not.

rphair commented Jun 1, 2016

At this time, Nemo 2.8.7 from the first link (ppa:webupd8team/nemo) has those patches, but Nemo 3.0.1 from the second link (ppa:embrosyn/cinnamon) does not.

@Filbuntu

This comment has been minimized.

Show comment
Hide comment
@Filbuntu

Filbuntu Jun 17, 2016

Nemo for Ubuntu: The list-view patch has been added by Andrew (THANKS A LOT!) to Nemo 2.8.7 (patched for Unity already) in the webupd8.org PPA:

sudo add-apt-repository ppa:webupd8team/nemo
sudo apt-get update
sudo apt-get install nemo nemo-fileroller

More info please, see webupd8.org PPA. He could not patch Nemo 3 for Ubuntu (with Unity):"Unfortunately I couldn't update Nemo to v3, it requires so many updates to the old patches that I doubt anyone will do it. However, I did manage to include the list-view patch, as well as some other patches from Nemo 3, into Nemo 2.8.7. Those patches seem to only work with GTK 3.18 and newer (I'm not sure, but I saw in a commit that they need some fixes to work on Linux Mint 17.x and thus, Ubuntu 14.04). That's why I uploaded Nemo 2.8.7 with these new patches for Ubuntu 16.04 only."

Filbuntu commented Jun 17, 2016

Nemo for Ubuntu: The list-view patch has been added by Andrew (THANKS A LOT!) to Nemo 2.8.7 (patched for Unity already) in the webupd8.org PPA:

sudo add-apt-repository ppa:webupd8team/nemo
sudo apt-get update
sudo apt-get install nemo nemo-fileroller

More info please, see webupd8.org PPA. He could not patch Nemo 3 for Ubuntu (with Unity):"Unfortunately I couldn't update Nemo to v3, it requires so many updates to the old patches that I doubt anyone will do it. However, I did manage to include the list-view patch, as well as some other patches from Nemo 3, into Nemo 2.8.7. Those patches seem to only work with GTK 3.18 and newer (I'm not sure, but I saw in a commit that they need some fixes to work on Linux Mint 17.x and thus, Ubuntu 14.04). That's why I uploaded Nemo 2.8.7 with these new patches for Ubuntu 16.04 only."

@AdelSulaiman

This comment has been minimized.

Show comment
Hide comment
@AdelSulaiman

AdelSulaiman Jul 7, 2016

Installed Linux Mint 18 Cinnamon Edition today. I'm very pleased with how Nemo 3 handles the column widths. Columns other than the name column get exactly the width they need, the rest of the available space is for the name column. There is no 'remembering' of the column width in case you'd feel like changing it, but I don't mind.
Not sure what this means for those who will remain on Mint 17.x the coming years, but for what it's worth, I'm happy now. I'd like to thank @mtwebster for his hard work.

AdelSulaiman commented Jul 7, 2016

Installed Linux Mint 18 Cinnamon Edition today. I'm very pleased with how Nemo 3 handles the column widths. Columns other than the name column get exactly the width they need, the rest of the available space is for the name column. There is no 'remembering' of the column width in case you'd feel like changing it, but I don't mind.
Not sure what this means for those who will remain on Mint 17.x the coming years, but for what it's worth, I'm happy now. I'd like to thank @mtwebster for his hard work.

@jensb

This comment has been minimized.

Show comment
Hide comment
@jensb

jensb Jul 7, 2016

Contributor

I just updated to Ubuntu 16.04 and I must say I like the more compact layout of Nemo's list views much better than before. Also, the 2.8.7 patches as described above work perfectly. For me, this issue is closed. Well, if we can get Nemo 3 at some point for Ubuntu 16.04 too, that is. But I'm not in a hurry. :)
Thank you to all involved!

Contributor

jensb commented Jul 7, 2016

I just updated to Ubuntu 16.04 and I must say I like the more compact layout of Nemo's list views much better than before. Also, the 2.8.7 patches as described above work perfectly. For me, this issue is closed. Well, if we can get Nemo 3 at some point for Ubuntu 16.04 too, that is. But I'm not in a hurry. :)
Thank you to all involved!

@agibson

This comment has been minimized.

Show comment
Hide comment
@agibson

agibson Jul 27, 2016

The topic of this thread is:
Re: [nemo] list view column width not remembered. (#626

*The new NEMO only auto adjusts the fields at startup, which is better. *

For the BEST: As the topic states and is still the case for MINT 18 : NEMO
does not remember the list view column width yet.

This would save me lots of time.

On Thu, Jul 7, 2016 at 1:11 PM, jensb notifications@github.com wrote:

I just updated to Ubuntu 16.04 and I must say I like the more compact
layout of Nemo's list views much better than before. Also, the 2.8.7
patches as described above work perfectly. For me, this issue is closed.
Well, if we can get Nemo 3 at some point for Ubuntu 16.04 too, that is. But
I'm not in a hurry. :)
Thank you to all involved!


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#626 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AAallPu8OILI9B0Sb709CpjKkdcyfuUJks5qTU9hgaJpZM4CB-rv
.

agibson commented Jul 27, 2016

The topic of this thread is:
Re: [nemo] list view column width not remembered. (#626

*The new NEMO only auto adjusts the fields at startup, which is better. *

For the BEST: As the topic states and is still the case for MINT 18 : NEMO
does not remember the list view column width yet.

This would save me lots of time.

On Thu, Jul 7, 2016 at 1:11 PM, jensb notifications@github.com wrote:

I just updated to Ubuntu 16.04 and I must say I like the more compact
layout of Nemo's list views much better than before. Also, the 2.8.7
patches as described above work perfectly. For me, this issue is closed.
Well, if we can get Nemo 3 at some point for Ubuntu 16.04 too, that is. But
I'm not in a hurry. :)
Thank you to all involved!


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#626 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AAallPu8OILI9B0Sb709CpjKkdcyfuUJks5qTU9hgaJpZM4CB-rv
.

@Vahan86

This comment has been minimized.

Show comment
Hide comment
@Vahan86

Vahan86 Nov 7, 2016

I can reproduce this issue in Nemo 3.0.6.

Vahan86 commented Nov 7, 2016

I can reproduce this issue in Nemo 3.0.6.

@JosephMcc JosephMcc added the BUG label Nov 7, 2016

@Vahan86

This comment has been minimized.

Show comment
Hide comment
@Vahan86

Vahan86 Nov 16, 2016

@JosephMcc, can we reopen this issue?

Vahan86 commented Nov 16, 2016

@JosephMcc, can we reopen this issue?

@mtwebster mtwebster removed the BUG label Nov 16, 2016

@mtwebster

This comment has been minimized.

Show comment
Hide comment
@mtwebster

mtwebster Nov 16, 2016

Member

No, the whole column width thing is as sane as it's going to get. Remembering column widths for each folder would add a lot of complexity and overhead that I really don't think would pay off.

We tend to keep metadata for easily defined things - the column order, sort column and so on. These are the same no matter what size the window ends up being, whether you're in dual pane view or not, and so on.

Not so with column widths - we would have to handle proportionality when the window isn't adequate size, or is overs-sized - we could assume things and implement some 'best guess,' algorithms, but based on experience, these seldom work 100% and they add yet more complexity for maintaining it.

The view we're using, a GtkListView, is very buggy and has been crippled in many ways over the past couple of years, as some of my comments in this thread can attest. As soon as you manually size a column, a number of changes take place in it (beyond our control without writing our own subclass), that make it no longer behave like a naturally-sized column.

I honestly think the current behavior is perfect for 99% of users - all your columns are guaranteed viewable upon loading, and any extra space is taken by the name column, which tends to run longest anyhow. All columns can be resized smaller than their content if desired (for very narrow views), and the scroll bars work in a reasonable manner.

Member

mtwebster commented Nov 16, 2016

No, the whole column width thing is as sane as it's going to get. Remembering column widths for each folder would add a lot of complexity and overhead that I really don't think would pay off.

We tend to keep metadata for easily defined things - the column order, sort column and so on. These are the same no matter what size the window ends up being, whether you're in dual pane view or not, and so on.

Not so with column widths - we would have to handle proportionality when the window isn't adequate size, or is overs-sized - we could assume things and implement some 'best guess,' algorithms, but based on experience, these seldom work 100% and they add yet more complexity for maintaining it.

The view we're using, a GtkListView, is very buggy and has been crippled in many ways over the past couple of years, as some of my comments in this thread can attest. As soon as you manually size a column, a number of changes take place in it (beyond our control without writing our own subclass), that make it no longer behave like a naturally-sized column.

I honestly think the current behavior is perfect for 99% of users - all your columns are guaranteed viewable upon loading, and any extra space is taken by the name column, which tends to run longest anyhow. All columns can be resized smaller than their content if desired (for very narrow views), and the scroll bars work in a reasonable manner.

@Vahan86

This comment has been minimized.

Show comment
Hide comment
@Vahan86

Vahan86 Nov 17, 2016

@mtwebster, thanks a lot for explanation.

Vahan86 commented Nov 17, 2016

@mtwebster, thanks a lot for explanation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment