Written by Endolith the 19 Nov 08 at 02:40.
Related project: Nautilus.
Status: New
Rationale
If you view long file names in Nautilus List View, it truncates by cutting off the end. But the vast majority of the time, if there are similar filenames, the part that differentiates them will either occur at the beginning or the end. If you cut off the end in this case, they will look identical and you will be forced to scroll or enlarge the text field to identify the one you want:
This is a file.txt
This is a long filename which is c...
This is a long filename which is c...
This is a long filename which is c...
This is a long filename which is c...
This is a short filename.jpg
But too long filenames should be prevented anyways
What do you mean by prevented? EXT3 allows up to 255 byte filenames, and that's a good thing. We certainly don't want to go back to 8.3 filenames from DOS! :)
Good idea phillip, and I too think it would be the best solution, but it is much more complicated to do. Maybe in 9.10, but I think this should be implemented in the mean time.
Horrible idea. Many times the information at the end of the file is not the important information. Extensions would be displayed instead of information in the middle that does actually pertain to the file.
Keep it as it is and if you don't like your long filenames rename the file.
Many times the information at the end of the file is not the important information.
When? Can you provide any examples of real files in which the beginning and end are identical, but the middle is not? I can't think of any time I have ever encountered this.
In the majority of cases, the beginning or end is what distinguishes similarly-named pathnames.
As I said in Solution #1, the ideal solution would be to display the parts that are actually different, but this is much more complicated and, in my experience, never actually necessary.