Comment 1 Laurent Fasani 2016-10-17 08:57:18 EDT

We have no reason to declare aird file as binary file. 	On the contrary, we have reason to keep the ability to do some textual comparison between two aird.

But I guess, you have an underlying problem that you may tell more about it.(or not ;) if you consider,after all, that there is nothing to see with Sirius )

Comment 2 Ed Willink 2016-10-17 10:31:20 EDT

The Eclipse default is that files are binary, so it is necessary to have an org.eclipse.team.core.filetypes for every non-binary file type. Please add one for *.aird.

Comment 3 Laurent Fasani 2016-10-18 09:15:24 EDT

Ok, we agree that it would be an interesting improvement.
It's not yet in the scope of a release but I'm marking it so that we consider it for inclusion in the next release.

Comment 4 Ed Willink 2016-10-18 09:43:38 EDT

(In reply to Laurent Fasani from comment #3)
> Ok, we agree that it would be an interesting improvement.

Since the files fail to observe normal Eclipse behaviour it is a bug not an enhancement.

> It's not yet in the scope of a release but I'm marking it so that we
> consider it for inclusion in the next release.

All that is required is a plugin.xml declaration such as

   <extension point="org.eclipse.team.core.fileTypes">
      <fileTypes extension="aird" type="text" />
   </extension>

Comment 5 Cedric Brun 2016-11-09 05:12:53 EST

This discussion on the egit mailling list might be relevant:

https://dev.eclipse.org/mhonarc/lists/egit-dev/msg04215.html

Comment 6 Ed Willink 2016-11-09 09:53:49 EST

(In reply to Cedric Brun from comment #5)
> This discussion on the egit mailling list might be relevant:

Not really. That is about making EGIT 'smart'. IMHO any attempt to get a CM tool to distort file content predictably is a recipe for endless obscure excitements. Let all files be 'binary'. i.e. use Unix new-lines on all platforms.