Skip to content

File system problem #1000

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

Closed
jevdplas opened this issue Aug 28, 2016 · 2 comments
Closed

File system problem #1000

jevdplas opened this issue Aug 28, 2016 · 2 comments

Comments

@jevdplas
Copy link

  • Brief description

Navigating through Windows-folders fails sometimes.

  • Full description / Expected results / Actual results / Steps

I made a symbolic link to a Windows folder for easy access like this: ln -s /mnt/c/Users/... to a Windows directory I often need, called Documents. The link is located in the /home/... folder from Bash/Ubuntu. In the Windows folder, there are other folders; in my case, there is a folder called Tetris.

Here is what I do (and see) in the terminal:

~$ cd Documents
~/Documents$ ls

Tetris

~/Documents$ cd Tetris
~/Documents/Tetris$ ls

Tetris

~/Documents/Tetris$ cd Tetris
~/Documents/Tetris/Tetris$ ls

Tetris

Although the path changes, the contents of the directory seems to remain the same. When I don't use the link, but write cd /mnt/c/.../Documents/Tetris in the terminal instead, the contents of the directory is shown correctly and I don't end up in a loop.

  • Windows build number

10.0.14393

  • Required packages and commands to install

none

@onomatopellan
Copy link

onomatopellan commented Aug 28, 2016

Duplicate of #650

It's already fixed on insider builds but as workaround you need to make the symlink ending the path without slash
ln -s /mnt/c/Users/onoma/Documents

@jevdplas
Copy link
Author

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants