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
I discovered this when trying to use Git with BOW and accessing the repository from IntelliJ, as a Windows application. Modifying files from Windows using C:\Users{user}\AppData\Local\lxss\ is buggy:
As you can see, saving b.txt in Windows doesn't even make it appear on the Bash side. If I try to write to that filename from Bash, all it gives is an I/O error.
Using /mnt/c/ in Bash rather than using C:\Users{user}\AppData\Local\lxss\ in Windows seems to actually work. There's an issue with Powershell using direct I/O (modifying a.txt and c.txt in the example), but that's a different bug entirely, as it still exists in /mnt/c, and Command Prompt does not have the same issue..
Microsoft Windows [Version 10.0.14393]
To reproduce:
write a file to a path on 'C:\Users{user}\AppData\Local\lxss': PS C:\Users\{user}\AppData\Local\lxss\home\{user}> echo "Hello, World!" > file.txt
Open BOW to the same location and attempt to write to the same location: {user}@{hostname}:~$ echo "hello" > file.txt
BOW will produce the following error: -bash: file.txt: Input/output error
strace gives no extra information.
I remedied my own issue by using Git in the /mnt/c/ directory instead.
The text was updated successfully, but these errors were encountered:
Known issue, by design. Do not enter %localappdata%\lxss unless you know what you are doing.
It was hidden for a reason.
Touching anything with the wrong tools will break it.
Things you can do safely: Read/move/rename files
Things you cannot do safely: Create/edit/copy files
Okay. I didn't consider using /mnt/c/ whatever reason, and ~lxss was the only other solution that I could find online. All things considered, it's a non-issue.
I discovered this when trying to use Git with BOW and accessing the repository from IntelliJ, as a Windows application. Modifying files from Windows using C:\Users{user}\AppData\Local\lxss\ is buggy:
As you can see, saving b.txt in Windows doesn't even make it appear on the Bash side. If I try to write to that filename from Bash, all it gives is an I/O error.
Using /mnt/c/ in Bash rather than using C:\Users{user}\AppData\Local\lxss\ in Windows seems to actually work. There's an issue with Powershell using direct I/O (modifying a.txt and c.txt in the example), but that's a different bug entirely, as it still exists in /mnt/c, and Command Prompt does not have the same issue..
To reproduce:
PS C:\Users\{user}\AppData\Local\lxss\home\{user}> echo "Hello, World!" > file.txt
{user}@{hostname}:~$ echo "hello" > file.txt
-bash: file.txt: Input/output error
strace gives no extra information.
I remedied my own issue by using Git in the /mnt/c/ directory instead.
The text was updated successfully, but these errors were encountered: