Description
Describe the bug
After creating a text file in Linux within my mounted %sandbox desk, if I then run "+ls %" to check the results of the commit, I wind up with a situation similar to below, where I get some error messages, followed by "%dy-edit-busy" resulting from any keypress until I hit backspace:
`
=dir /=sandbox=
=% /~hathec-pilsyx/sandbox/~2021.1.19..01.31.32..d654
[ %clay-sing-indirect-data
desk=%sandbox
mood=[care=%a case=[%da p=~2021.1.19..01.31.32..d654] path=/gen/ls/hoon]
aeon=3
]
+ls %
[ %clay-sing-indirect-data
desk=%sandbox
mood=[care=%a case=[%da p=~2021.1.19..01.31.32..d654] path=/gen/ls/hoon]
aeon=3
]
%dy-no-prompt
%dy-edit-busy
%dy-edit-busy
%dy-edit-busy
~hathec-pilsyx:dojo/=/sandbox/~2021.1.19..01.31.32..d654>
`
To Reproduce
Steps to reproduce the behaviour:
- Create a textfile in Linux within a mounted desk
- In dojo, commit the changes to the desk
- Use +ls to examine desk contents
Expected behaviour
The current directory contents are printed to terminal
System (please supply the following information, if relevant):
- OS: [e.g. macOS, linux64, FreeBSD] Ubuntu 20.04.1 x64
- Vere and Urbit OS versions - 1.0
- Your ship's
%basehash (use+troubleto check) - [0v1.1gbvo.e03d1.nk94q.lmsv5.lasnk.7s08i.jmgvq.7goos.3uqij.fienr]
Additional context
Spoke to some users in ~bitbet-bolbel/urbit-community/help, and was told my issue sounded similar to #4037