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
I would like to suggest an option/config/verb? to disable the resolving of symlink, for reason above.
Broot seems to resolve symlinks unconditionally, which mainly manifests in two ways:
In the demo below
/tmp
is resolved to/private/tmp
upon opening broot:https://github.com/user-attachments/assets/0cb14770-ade9-479f-b394-da3032dcb292
In the demo below
relative -> foo/bar
is resolved to the full path:https://github.com/user-attachments/assets/d4dd29f9-bcbe-4686-8a5d-bdf6821f1257
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
:I would like to suggest an option/config/verb? to disable the resolving of symlink, for reason above.