I am using Windows + Wezterm + bash with the default configuration of fx.
Here is the directory in fx:
symlinked-bash is a symlinked folder. It links to new-dir:
(See the symlinked-bash -> new-dir.)
symlinked-bash was created in bash using ln -s new-dir/ symlinked-bash. Windows Developer Mode had to be enabled and the follwing had to be put in ~/.bashrc: export MSYS=winsymlinks:nativestrict.
new-dir:
If I press l on symlinked-bash, the path at the top gets prefixed with \\?\. It looks almost like a UNC path:
If I press l on new-dir, the path at the top is fine:
If I press <cr> on symlinked-bash, this occurs. The file is empty and the path at the bottom is messed up.
If I press <cr> on new-dir, everything works normally.
I am using Windows + Wezterm + bash with the default configuration of
fx
.Here is the directory in![image](https://github.com/kyoheiu/felix/assets/58403689/3ab0ab41-1aba-4ea6-b598-b557a7b8ae60)
fx
:symlinked-bash
is a symlinked folder. It links tonew-dir
:symlinked-bash -> new-dir
.)symlinked-bash
was created in bash usingln -s new-dir/ symlinked-bash
. Windows Developer Mode had to be enabled and the follwing had to be put in~/.bashrc
:export MSYS=winsymlinks:nativestrict
.new-dir
:If I press![image](https://github.com/kyoheiu/felix/assets/58403689/545ea5a2-b635-4b13-8bfe-dd7f35e28cf7)
l
onsymlinked-bash
, the path at the top gets prefixed with\\?\
. It looks almost like a UNC path:If I press![image](https://github.com/kyoheiu/felix/assets/58403689/f0d3ffb3-37c2-427a-bbdc-b3e938da3ab9)
l
onnew-dir
, the path at the top is fine:If I press![image](https://github.com/kyoheiu/felix/assets/58403689/fc99f1fc-7aa3-4a83-ba5d-f12971a0ba32)
<cr>
onsymlinked-bash
, this occurs. The file is empty and the path at the bottom is messed up.If I press
<cr>
onnew-dir
, everything works normally.