bootandy/archived-dust
1
0
Fork 0
mirror of https://github.com/bootandy/dust.git synced 2026-06-08 11:29:05 +03:00
Code Issues 21 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #524] --files0-from takes newline-terminated paths, not null-terminated paths #230

New Issue
Closed
opened 2026-06-08 11:26:15 +03:00 by zhus · 3 comments
zhus commented 2026-06-08 11:26:15 +03:00
Owner
Copy Link
Copy Source

Originally created by @j824h on GitHub (Aug 20, 2025).
Original GitHub issue: https://github.com/bootandy/dust/issues/524

touch a b
# This gets parsed to a, b
printf 'a\nb\n' | dust --files0-from -
# This doesn't get parsed to a, b so errors:
printf 'a\0b\0' | dust --files0-from -

Contradictory to what -h shows, --files0-from takes newline-terminated paths, not null-terminated paths.
This is confusing also because the expectations from GNU du (along with many others in coreutils family) does not match the current actual behavior of dust.

cf. #405

Originally created by @j824h on GitHub (Aug 20, 2025). Original GitHub issue: https://github.com/bootandy/dust/issues/524 ``` touch a b # This gets parsed to a, b printf 'a\nb\n' | dust --files0-from - # This doesn't get parsed to a, b so errors: printf 'a\0b\0' | dust --files0-from - ``` Contradictory to what -h shows, `--files0-from` takes newline-terminated paths, not null-terminated paths. This is confusing also because the expectations from GNU `du` (along with many others in coreutils family) does not match the current actual behavior of dust. cf. #405
zhus closed this issue 2026-06-08 11:26:15 +03:00
zhus commented 2026-06-08 11:26:15 +03:00
Author
Owner
Copy Link
Copy Source

@j824h commented on GitHub (Aug 23, 2025):

I might work on the "fix" but it would technically cause a breaking change.

<!-- gh-comment-id:3216794764 --> @j824h commented on GitHub (Aug 23, 2025): I might work on the "fix" but it would technically cause a breaking change.
zhus commented 2026-06-08 11:26:15 +03:00
Author
Owner
Copy Link
Copy Source

@j824h commented on GitHub (Aug 30, 2025):

https://github.com/j824h/dust/commit/0f6c11415853e0b2f0bdb64aa3d8662face95c39

<!-- gh-comment-id:3239195017 --> @j824h commented on GitHub (Aug 30, 2025): https://github.com/j824h/dust/commit/0f6c11415853e0b2f0bdb64aa3d8662face95c39
zhus commented 2026-06-08 11:26:16 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (Oct 6, 2025):

thanks,
https://github.com/bootandy/dust/pull/529

<!-- gh-comment-id:3373419450 --> @bootandy commented on GitHub (Oct 6, 2025): thanks, https://github.com/bootandy/dust/pull/529
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 windows help wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
zhus (Sergey Zhukov)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bootandy/archived-dust#230
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?