Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

exa --tree with --git-ignore #569

Closed
lamyergeier opened this issue Aug 11, 2019 · 6 comments
Closed

exa --tree with --git-ignore #569

lamyergeier opened this issue Aug 11, 2019 · 6 comments

Comments

@lamyergeier
Copy link

When we execute, exa --tree with --git-ignore. Paths mentioned in .gitignored are not respected.

#.gitignore
/**/Unsync/**
$ exa --tree --git-ignore
.
├── a.pdf
├── B
│  ├── a.pdf
│  ├── b.md
│  └── Unsync
│     ├── a.pdf
│     └── b.md
└── b.md
@kdabir
Copy link

kdabir commented Aug 12, 2019

Even I am facing the same problem. The same issue affect --recurse option as well.

@hrlmartins
Copy link

hrlmartins commented Aug 27, 2019

Can you try remove the first / char from the line of the .gitignore to see if it works.

@alexilyaev
Copy link

Had the same issue with nested node_modules folder.

With exa, this only ignores the top level node_modules, but in git it actually ignores it anywhere in the tree.

#.gitignore
node_modules

Adding this works for exa, but we shouldn't be needing to do this:

#.gitignore
node_modules
*/node_modules

@whitelynx
Copy link

I'm also having the same issue, specifically with __pycache__ folders and .pyc files. My .gitignore has the lines:

__pycache__/
*.py[cod]

which correctly make git ignore all nested __pycache__ and .pyc files, but exa--tree --git-ignore still shows them.

@pmensik
Copy link

pmensik commented Nov 18, 2020

Is there any progress with this issue? I can confirm that exa -T --git-ignore will display contents of the target directory (which is in the .gitignore) when this project is built.

@ariasuni
Copy link
Collaborator

ariasuni commented Apr 9, 2021

I can’t reproduce. I believe this was fixed by #653 and that it should work correctly if you’re using exa 0.10.0.

@ariasuni ariasuni closed this as completed Apr 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants