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

Option to not resolve symlink #942

Open
kidonng opened this issue Sep 10, 2024 · 0 comments
Open

Option to not resolve symlink #942

kidonng opened this issue Sep 10, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@kidonng
Copy link

kidonng commented Sep 10, 2024

Broot seems to resolve symlinks unconditionally, which mainly manifests in two ways:

  • Symlinks are resolved when navigating through directories, whether passed as command line arguments or inside broot

In the demo below /tmp is resolved to /private/tmp upon opening broot:

Screen.Recording.2024-09-11.at.1.11.03.AM.mov
  • Relative symlinks are shown with resolved absolute paths

In the demo below relative -> foo/bar is resolved to the full path:

Screen.Recording.2024-09-11.at.1.12.26.AM.mov

I'm not sure if this is intentional or actually a bug, I will assume it's the former. While the former manifestation is less problematic in practice (left arrow key goes back regardless of symlinks or not), the latter could prevent efficient display of useful info.

In the (somewhat contrived) demo below, broot shows the files less optimal than regular ls:

ls broot
Screenshot 2024-09-11 at 1 17 26 AM Screenshot 2024-09-11 at 1 17 32 AM

I would like to suggest an option/config/verb? to disable the resolving of symlink, for reason above.

@kidonng kidonng added the enhancement New feature or request label Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant