I'm of the opinion that artifacts of IDEs an OSes should not be part of a projects .gitignore. After all, different people could be using different environments for development and I really don't see the need for a projects .gitignore to contain the subset of all possible artifacts.
Use .git/info/exclude or a repository independent personal .gitignore for this.
The projects file is for files created by running the code or maybe some unavoidable build artifacts happening in all cases (.o files for example)
I really hate commits with messages like "updating .gitignore for Joe's new IDE"
Comments
I'm of the opinion that artifacts of IDEs an OSes should not be part of a projects .gitignore. After all, different people could be using different environments for development and I really don't see the need for a projects .gitignore to contain the subset of all possible artifacts.
Use .git/info/exclude or a repository independent personal .gitignore for this.
The projects file is for files created by running the code or maybe some unavoidable build artifacts happening in all cases (.o files for example)
I really hate commits with messages like "updating .gitignore for Joe's new IDE"