You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've encountered a nasty problem with br which I think can be quite widespread among developers and ruins first experience with br (it took me about 30 minutes to find the root cause). At the first glance it looked like a some bug file listing permissions or similar issue, but it turned out that it is related to hidden files.
I store all my dotfiles at github. br by default ignores .gitignore-ed files, but I have .gitignore in my $HOME with * pattern as a first line (i.e. ignore ALL files except whitelisted). so br ignores ALL files in my home and shows literally nothing (dotfiles are hidden also).
I think you can show some hint in case br lists an "empty" folder, something like "press alt + i to show gitignored files, press alt + h to show hidden files"
The text was updated successfully, but these errors were encountered:
It's not just the .gitignore: you must have also defined your home directory as a git repository or the gitignore rules wouldn't have been applied by broot. The usual practice is rather to symlink the relevant files.
I've encountered a nasty problem with
br
which I think can be quite widespread among developers and ruins first experience withbr
(it took me about 30 minutes to find the root cause). At the first glance it looked like a some bug file listing permissions or similar issue, but it turned out that it is related to hidden files.I store all my dotfiles at github.
br
by default ignores.gitignore
-ed files, but I have.gitignore
in my$HOME
with*
pattern as a first line (i.e. ignore ALL files except whitelisted). sobr
ignores ALL files in my home and shows literally nothing (dotfiles are hidden also).I think you can show some hint in case
br
lists an "empty" folder, something like "press alt + i to show gitignored files, press alt + h to show hidden files"The text was updated successfully, but these errors were encountered: