Adding a gazillion specific editor files in project specific .gitignore is impractical. There's always N+1 conceivable editors where 1 represents a new editor that hasn't been conceived yet; but will definitely come with new specific files that pollute your projects.
The problem then is that doing the upkeep of adjusting all .gitignore files across all your projects to the new situation is time-consuming and tedious housekeeping. Whereas simply adding a single line to a global .gitignore is trivial.
But what about people who don't use a global gitignore file?
If you're the maintainer of a project; you get to reject PR's that might contain such files.
If you aren't the maintainer of a project; and simply forked someone else's code that does contain such files; either you could create a PR and flag it as a housekeeping task, or you could happily ignore those files and put the responsibility in the hands of the maintainer in so-far that they don't get in the way of your own editor settings.
If you are working in a small team, you should at least make an agreement on how to deal with this problem among team members.
See: https://twitter.com/eenriquelopez/status/1212636370365083648
Adding a gazillion specific editor files in project specific .gitignore is impractical. There's always N+1 conceivable editors where 1 represents a new editor that hasn't been conceived yet; but will definitely come with new specific files that pollute your projects.
The problem then is that doing the upkeep of adjusting all .gitignore files across all your projects to the new situation is time-consuming and tedious housekeeping. Whereas simply adding a single line to a global .gitignore is trivial.
But what about people who don't use a global gitignore file?
If you're the maintainer of a project; you get to reject PR's that might contain such files.
If you aren't the maintainer of a project; and simply forked someone else's code that does contain such files; either you could create a PR and flag it as a housekeeping task, or you could happily ignore those files and put the responsibility in the hands of the maintainer in so-far that they don't get in the way of your own editor settings.
If you are working in a small team, you should at least make an agreement on how to deal with this problem among team members.