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

Feature request: Add support to run through xargs (show absolute path) #524

Closed
Knud3 opened this issue May 5, 2022 · 7 comments
Closed

Comments

@Knud3
Copy link

Knud3 commented May 5, 2022

e.g. when running find "${PWD}" -type f -print0 | xargs -0 colorls -l it only shows file names.

find "${PWD}" -type f -print0 | xargs -0 ls -l in otherhand shows files with absolute path.

@ayushpoddar
Copy link
Contributor

I'd like to take it up ✋🏽

@ayushpoddar
Copy link
Contributor

Update: Issue found

colorls treats file arguments differently from how ls does.

When the argument is file path, colorls just displays the file name. Whereas, ls displays the relative file path

@ayushpoddar
Copy link
Contributor

@avdv Can we close this issue, now that the related PR has been merged

@avdv
Copy link
Collaborator

avdv commented Jun 7, 2023

@avdv Can we close this issue, now that the related PR has been merged

Yes, of course. Fixed by #594

@avdv avdv closed this as completed Jun 7, 2023
@Knud3
Copy link
Author

Knud3 commented Jun 7, 2023

Fantastic update! Thanks @ayushpoddar!

@avdv, any schedule when gem package get updated with this PR? Latest release is over year old.

@avdv
Copy link
Collaborator

avdv commented Jun 7, 2023

any schedule when gem package get updated with this PR? Latest release is over year old.

Seems like I Inadvertently had broken our publish process and just figured this out: #596 -- if this is merged you should be able to install a pre-release version immediately, but still needs an approval from @athityakumar

@ayushpoddar
Copy link
Contributor

any schedule when gem package get updated with this PR? Latest release is over year old.

Seems like I Inadvertently had broken our publish process and just figured this out: #596 -- if this is merged you should be able to install a pre-release version immediately, but still needs an approval from @athityakumar

I will wait until this PR is merged before creating any more PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants