← Back to team overview

desktop-packages team mailing list archive

[Bug 1243806] Re: The names column has its width dictated by other columns


Does this mean it's fixed or someone just pushed the "ignore pesky
users" button again?  I see no new Nautilus updates since last week.

Does this mean 14.10's version will be improved?

The 14.04 examples in the attachment are a bit forced with non-sensitive
data from my home machine, but when you're at work dealing with files
and paths like "/Clients/Lastname, Firstname/adv. Plaintiff/for
filing/Motion (Second) for Extension of Time to File Opposition.pdf" and
any column gets truncated, you're in for a bad time when all search
results return as e.g. "Mot...".

The Dash search also seems to have issues being useful with these common
cases of 'important metadata is in the path as well as the filename' if
you're trying to find Bob's motion and not Alice's.

I know I'm without gruntle, but I'm told all of these features break
equally when working with multiple git repos, so what audience is being
adequately served by any of this again?

** Attachment added: "Nautilus maximum column width still suboptimal - bring back horizontal scrollbar.png"

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.

  The names column has its width dictated by other columns

Status in Nautilus:
Status in “nautilus” package in Ubuntu:
Status in “nautilus” source package in Trusty:

Bug description:
  Folder names in Location area keeps the width even though when I go back to upper folder.
  First of all this new downgraded nautilus folder section holds its width and I cannot even change the width at all.
  Then when I go deep down lower folders or open folder with long name, it would squeeze down the "Name" part and I cannot even see names anymore. Then when I go up to upper folder or root, I cannot see the names anymore becaue location column takes up all the space. Once I click one of the unseen folder, I may see the names again. 
  This is one of too many problems of 13.10.

To manage notifications about this bug go to: