Use $XDG_CONFIG_HOME/git/ignore as the default global .gitignore

[mrymtsk]

Describe the bug
Broot currently refers to the file specified in core.excludesFile variable of the global git config as the global .gitignore. However, it is stated in the documentation that $XDG_CONFIG_HOME/git/ignore (or $HOME/.config/git/ignore if $XDG_CONFIG_HOME is not set) is the default value of core.excludesFile. It would be nice if broot refers to $XDG_CONFIG_HOME/git/ignore when core.excludesFile is not set.

To Reproduce

1. Create $XDG_CONFIG_HOME/git/ignore with * (ignores all) as the content.
2. Remove core.excludesFiles variable from the global git config.
3. Go to any git repository.
4. broot -I to see that files are not ignored.

Expected behavior
All files are expected to be ignored in the above case.

Configuration (please complete the following information):

• OS: macOS
• Version: broot 0.13.2

[Canop]

The specification says:

Patterns which a user wants Git to ignore in all situations (e.g., backup or temporary files generated by the user’s editor of choice) generally go into a file specified by core.excludesFile in the user’s ~/.gitconfig. Its default value is $XDG_CONFIG_HOME/git/ignore. If $XDG_CONFIG_HOME is either not set or empty, $HOME/.config/git/ignore is used instead.

I think it means the correct behavior is to use the core.excludesFile git configuration variable, which is what broot does.

[mrymtsk]

Yes that is the correct behavior, but I meant that broot can use $XDG_CONFIG_HOME/git/ignore (or $HOME/.config/git/ignore) as the global .gitignore when core.excludesFile is not set, just as git does.

[rlue]

Not sure if this is related or if it deserves a new issue, but I've explicitly set core.excludesFile and still seeing files in broot that are explicitly ignored:

# ~/.config/git/config
[core]
	excludesFile = ~/.config/git/ignore

# ~/.config/git/ignore
/tags

Even with this, br still shows tags files in the current directory with gi:y. Am I missing something or doing something wrong? Should I open a new issue? Can we reopen this one?

[Canop]

@rlue this looks like a different issue. I suspect the / in /tags isn't understood by broot to be the current repository. Can you create the issue ?
(if you don't create it I'll do it when I have some time for the checks)

[rlue]

Sorry it took so long to follow up. I see that you created #321 for this. Thanks so much! 🙇