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
Trying to use ../ in :open while in a symlinked directory shows autocomplete from the parent directory of the symlink source rather than the symlink. Actually opening the file does not do this and goes to the correct parent directory.
Reproduction Steps
I tried this:
mkdir a
mkdir b
touch file_in_root
cd a
touch file_in_a
ln -s ../b link_to_b
cd link_to_b
hx
:open ../
I expected this to happen:
Receive autocomplete from a e.g. link_to_b/ file_in_a
Instead, this happened:
Receive autocomplete from the root folder e.g. a/ b/ file_in_root
Helix log
Log was empty
Platform
Arch Linux
Terminal Emulator
kitty 0.35.2
Installation Method
pacman
Helix Version
helix 24.7
The text was updated successfully, but these errors were encountered:
This is not a bug this is simply how symlinks work. If you run ls .. instead of opening helix you will find that it prints the same thing helix suggests.
Summary
Trying to use
../
in:open
while in a symlinked directory shows autocomplete from the parent directory of the symlink source rather than the symlink. Actually opening the file does not do this and goes to the correct parent directory.Reproduction Steps
I tried this:
mkdir a
mkdir b
touch file_in_root
cd a
touch file_in_a
ln -s ../b link_to_b
cd link_to_b
hx
:open ../
I expected this to happen:
Receive autocomplete from
a
e.g.link_to_b/ file_in_a
Instead, this happened:
Receive autocomplete from the root folder e.g.
a/ b/ file_in_root
Helix log
Log was empty
Platform
Arch Linux
Terminal Emulator
kitty 0.35.2
Installation Method
pacman
Helix Version
helix 24.7
The text was updated successfully, but these errors were encountered: