Skip to content

Conversation

@MuntasirSZN
Copy link

Description

Fixes #1361

In non tree mode, is_all_all was being checked, but not in tree mode.
This meant that -Ta was not being handled correctly in tree mode.

How Has This Been Tested?

i ran eza -Ta in root dir / and it didn't hang for me. Others need to test it.

@MuntasirSZN
Copy link
Author

Oops not an issue with tree mode, its -a.

@MuntasirSZN MuntasirSZN marked this pull request as draft October 16, 2025 07:10
@MuntasirSZN
Copy link
Author

Maybe its the fix, maybe just maybe...

@gierens gierens merged commit 1fdd754 into eza-community:main Jan 4, 2026
10 checks passed
@MuntasirSZN
Copy link
Author

MuntasirSZN commented Jan 5, 2026

@gierens why did you merge??? Its 0 changes!

@gierens
Copy link
Member

gierens commented Jan 5, 2026

@gierens why did you merge??? Its 0 changes!

This is odd, I didn't merge anything, how would I without any commits in this PR? The commit it shows as merged is 1fdd754, which was main just before I rebased another PR on main.

My guess would be, that using the pull bot on an empty PR causes some confusion.

@MuntasirSZN
Copy link
Author

MuntasirSZN commented Jan 5, 2026 via email

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

Successfully merging this pull request may close these issues.

bug: eza -T with -a hangs.

2 participants