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

fix: do not print parent filename with --absolute=on #1182

Merged

Conversation

libklein
Copy link
Contributor

@libklein libklein commented Oct 6, 2024

The parent path of a file was added even with absolute={on,follow}, causing the parent path being prepended to the resolved (absolute) filepath.

Fixes: #1151

@libklein libklein force-pushed the issue-1151-absolute-path-wrong branch 2 times, most recently from 022fba8 to 859c7c4 Compare October 6, 2024 14:39
The parent path of a file was added even with absolute={on,follow}, causing the parent path being prepended to the resolved (absolute) filepath.

Fixes: eza-community#1151
@cafkafk cafkafk force-pushed the issue-1151-absolute-path-wrong branch from 859c7c4 to db412c7 Compare October 9, 2024 07:04
Copy link
Member

@cafkafk cafkafk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! I manage to be able to reproduce the issue, and this does seem to solve it, thanks for the contribution!

@cafkafk cafkafk merged commit 1725903 into eza-community:main Oct 9, 2024
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

bug: The --absolute option is unable to correctly retrieve the file's absolute path.
2 participants