In general I am skeptical to putting too much into .hgignore and .gitignore and such. They sometimes hide things and create more confusion. Typically I would run "make clean" quite often so build artifacts are gone when I use "hg status". And I use "hg diff" a lot so I see what I have changed. However I see the advantage of a cleaner hg status to catch for instance that a new source file hasn't been added to the repo.
The .DS_Store is such a calamity that it is reason enough to not use MacOS at all ;)
You know that you can have your own per-user ignore file? That would make very much sense for .DS_Store and .o and .a files that you likely want to ignore in all your mercurial repos. In your $HOME/.hgrc add for instance:
[ui]ignore=~/.my_hgignore
Last edit: Tormod Volden 2020-04-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In general I am skeptical to putting too much into .hgignore and .gitignore and such. They sometimes hide things and create more confusion. Typically I would run "make clean" quite often so build artifacts are gone when I use "hg status". And I use "hg diff" a lot so I see what I have changed. However I see the advantage of a cleaner hg status to catch for instance that a new source file hasn't been added to the repo.
The .DS_Store is such a calamity that it is reason enough to not use MacOS at all ;)
You know that you can have your own per-user ignore file? That would make very much sense for .DS_Store and .o and .a files that you likely want to ignore in all your mercurial repos. In your $HOME/.hgrc add for instance:
Last edit: Tormod Volden 2020-04-25
Tormod, you bring up some good points. Plus I found from real .a files in the repo. I'll close this.