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 keep all my configuration stuff, ad-hoc scripts and so on in git repository
that is cloned into my home directory. This workflow is described in greater
detail in following blog article: https://drewdevault.com/2019/12/30/dotfiles.html
As configured by ".gitignore" in home directory, everything is ignored, and
when I want to start tracking particular script or configuration file, I "git
add -f" it. And once I started tracking file, I also want to auto-format it.
Problem is that treefmt(1) reads my .gitignore and concludes that it should not
traverse anywhere, so it finds no files to format and does nothing. This
behaviour makes perfect sense (disregarding .gitignore and traversing whole ~/
would take ages), yet it does not work for my scenario.
I think reasonable solution that would be mostly backward-compatible would be
to additionally process files printed by "git ls-files", so files already
tracked in git will always be considered by treefmt(1).
Alternatively, I can manually do "git ls-files .config | xargs treefmt", but
that is quite a lot of typing.
The text was updated successfully, but these errors were encountered:
I keep all my configuration stuff, ad-hoc scripts and so on in git repository
that is cloned into my home directory. This workflow is described in greater
detail in following blog article: https://drewdevault.com/2019/12/30/dotfiles.html
As configured by ".gitignore" in home directory, everything is ignored, and
when I want to start tracking particular script or configuration file, I "git
add -f" it. And once I started tracking file, I also want to auto-format it.
Problem is that treefmt(1) reads my .gitignore and concludes that it should not
traverse anywhere, so it finds no files to format and does nothing. This
behaviour makes perfect sense (disregarding .gitignore and traversing whole ~/
would take ages), yet it does not work for my scenario.
I think reasonable solution that would be mostly backward-compatible would be
to additionally process files printed by "git ls-files", so files already
tracked in git will always be considered by treefmt(1).
Alternatively, I can manually do "git ls-files .config | xargs treefmt", but
that is quite a lot of typing.
The text was updated successfully, but these errors were encountered: