From: Denis M. <de...@li...> - 2000-10-10 22:43:57
|
I want to propose this idea on MIME types handling on the filer. Looking at the mimetypes identification code I've noticed that actually the code is splitted into dir.c and type.c and into type.c it is merged with the gui management code. The types recognition, now works with 2 pass, the first that give main type from permission and stat() result, the second that give file type from filename. This method on my system cause great problems because I have wrong execute permissions on a great number of files. Also actually there is no way to parse file contents (see file shell command) to find the file type that in my opinion is a very useful thing (on Unix systems specially). In conclusion, I think it is a good idea to transfer all the type identification code out of dir.c and use it in a unique function (for example a mime_type_from_filename()) that use name/permissions/stat() infos to give the most accurate result in file identification, also a gui separation can help in code mantaining. Comments... ??? |
From: Thomas L. <ta...@le...> - 2000-10-13 18:12:53
|
On Wed, 11 Oct 2000, Denis Manente wrote: > I want to propose this idea on MIME types handling on the filer. > Looking at the mimetypes identification code I've noticed that > actually the code is splitted into dir.c and type.c and into > type.c it is merged with the gui management code. The types > recognition, now works with 2 pass, the first that give main > type from permission and stat() result, the second that give > file type from filename. > > This method on my system cause great problems because I have > wrong execute permissions on a great number of files. Easy enough to fix - just make having an extension take precedence over being executable. But, what about 'install.sh'? That really is executable! > Also > actually there is no way to parse file contents (see file > shell command) to find the file type that in my opinion > is a very useful thing (on Unix systems specially). This is *very* slow! Especially if your home directory is an NFS mount... Hopefully, the Shift+Menu thing will allow you to choose a run action from a list based on the file's contents. So, shift+menu on a postscript file will offer to load it into GhostView, print it, etc. But to do it on every file when scanning a directory... no :-( Thomas Leonard -- tal197 at users.sourceforge.net The ROX desktop (free/GPL) : http://rox.sourceforge.net |