Bug 36151 - file dialog has no sort file by file type option
Summary: file dialog has no sort file by file type option
Status: RESOLVED DUPLICATE of bug 63877
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: kfile (show other bugs)
Version: unspecified
Platform: Slackware Other
: NOR wishlist
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-12-14 16:03 UTC by kreuzritter2000
Modified: 2005-01-08 18:50 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kreuzritter2000 2001-12-14 15:58:04 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           kate
Version:           KDE 2.2.0 
Severity:          wishlist
Installed from:    Slackware Packages
Compiler:          Not Specified
OS:                Not Specified
OS/Compiler notes: Not Specified

In Kate the inbuild file browser
has an option to sort the filenames my
date name etc. but it is not possible to sort that files by the filetype.

So such a feature would be great.

For example.
I use kate for programming.
So i have my *.cpp files in my directory when i compile them with
$ g++ test.cpp -o test.bin 
i get my binary file.

But when i have 20 files let's say test1.cpp - test20.cpp i also
have test1.bin -test20.bin.

But now picking only the source code files in the browser is not very userfriendly because between every source code file i have a binay file listed.

----
test1.bin
test1.cpp
test2.bin
test2.cpp
test3.bin
test3.cpp
etc..
-----

So sorting those files by the file type would improve the usability of kate.

This way it would look like this:
----
test1.bin
test2.bin
test3.bin
etc *.bin
test1.cpp
test2.cpp
test3.cpp
etc..
-----

Another good feature would be to only list those files which should be showed.

For example only *.cpp or *.c files etc.


thanks.
 

(Submitted via bugs.kde.org)
Comment 1 Stephan Binner 2005-01-08 18:50:35 UTC

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