bug: eza hides files beginning with __ for python projects on Windows #1220
Comments
|
Just my 2 cents here but in my opinion this "feature" is more confusing than useful. I'll open a PR removing this. But I think some of the maintainer may want to weigh in here |
On windows files prefixed with a `_` were being ignored because some old applications used those files as pseudo dotfiles. This was controversial when the feature was added way back when: ogham/exa#820 (review) Fixes eza-community#1220
|
For what it's worth, as a Windows user I do find this behaviour very surprising. No other tool I've used considers them hidden. And I can't think of a situation where I've wanted them to be. |
|
Just popping by to say that this confused me too. It is not the behaviour used by Other than using Cheers |
|
I've had to add convoluted exclude patterns to my commonly used eza alias. So I include that -a flag, and then patterns I want excluded like .*, and a bunch of Windows junk hidden files that crop up in %userprofile% (home) (which are not hidden by default by eza) |
On windows files prefixed with a `_` were being ignored because some old applications used those files as pseudo dotfiles. This was controversial when the feature was added way back when: ogham/exa#820 (review) Fixes eza-community#1220
Python developers will know that 'dunder' files are common in python projects (
__init__.py,__main__.py,_private_module.py, etc).On Windows, eza consideres files starting with a underscore (
_) as a hidden 'dotfile', and does not list them by default.Technically, this is not actually a bug, as I have seen the code and PR's that added this feature.
But I think we would all agree this is undesired behavior and a common occurance for lots of (python) developers?
Seemingly 'missing' files beginning with
_has annoyed me more often then it's been useful hiding files I don't want to see.(I don't think I have ever encountered a file on Windows starting with
_that should be hidden. Though I have certainly spent too long trying to ignore all the garbage files Windows likes to throw in my $HOME)The text was updated successfully, but these errors were encountered: