Bug 73555

Summary: kdevelop needs file association for *.S files
Product: [Applications] kdevelop Reporter: Jon Smirl <jonsmirl>
Component: generalAssignee: KDevelop Developers <kdevelop-devel>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version: git master   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:

Description Jon Smirl 2004-01-26 18:56:34 UTC 
Version:           CVS (using KDE Devel)
Installed from:    Compiled sources

*.S files are gcc assembly language source. They should have an association so that the will be open via the kdevelop editor. 

For example I made a change to C file that caused and error in a *.S file. When  I jumped to the error the file wasn't associated with kdevelop and wouldn't open.
Comment 1 Amilcar do Carmo Lucas 2004-01-26 19:14:39 UTC 
possible 58912 duplicate
Comment 2 Sascha Cunz 2004-01-26 19:40:30 UTC 
Ain't a dupe of #58912 :-)

Though katepart can handle .s / .S files correctly in terms of a simple syntax-highlighting, there in fact does not exist a mime-type for gnu assembler.

Neither katepart, nor KDElibs, nor kdevelop declares a mime type for gnu assembler.

So this is pretty valid and has nothing to do with wrong mime type handling. Someone must write a .desktop file for gnu-assembler in order to have this work.

What mime-type should be used that for? text/x-gnu-asm?
Where should that mime-type be defined? Somewhere in kdelibs? in katepart? in kdevelop?

I think, that kdevelop is not the right place to put that .desktop file, since it should be posibile to open .s / .S files, even if KDevelop ain't installed at all. If so, we should reassign either to kate or some other place in kdelibs.
Comment 3 Sashmit Bhaduri 2004-01-27 07:03:35 UTC 
Are you sure that other assesemblers don't use .s/.S too?
Comment 4 Sascha Cunz 2004-01-27 09:53:27 UTC 
No. I'm pretty sure, that most assemblers will use something like: .asm .s or .S

But how could we determine at all, that a file is a) any assembler or b) maybe even GNU Assembler?
Comment 5 Jens Dagerbo 2004-09-03 23:33:50 UTC 
I'd like to think this is fixed with KDevelop-3.1. 

For unknown mimetypes KDevelop now asks if they should be opened as text with the option to do so in the future. I think this is as good as we can do it apart from fixing every single mimetype in KDE to behave properly.

FIXED.
Comment 6 Jon Smirl 2004-09-04 00:03:26 UTC 
I just tried it with current CVS. It opens the file as text without a prompt.