You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One does not know which files exist in the current dir. That makes it hard to reason about the directory structure if there are symlinks for which the targets only exist in the production environment for example.
Creating a file that collides with the name of a symlink will unexpectedly create a file where the symlink points to. So creating "a" could create "/some/file/somewhere".
The text was updated successfully, but these errors were encountered:
Steps to Reproduce the Issue
ln -s b a
vim .
Current Behavior
a is not displayed
Expected Result
a is displayed as "a -> b"
Not displaying it creates a few issues:
One does not know which files exist in the current dir. That makes it hard to reason about the directory structure if there are symlinks for which the targets only exist in the production environment for example.
Creating a file that collides with the name of a symlink will unexpectedly create a file where the symlink points to. So creating "a" could create "/some/file/somewhere".
The text was updated successfully, but these errors were encountered: