Issue description
The issue happens if in a different terminal, you delete the folder that rovr is currently in, resulting in it not being able to get the current working directory, causing a crash.
How do you reproduce it?
- Go to
/tmp
- Create a new directory
mkdir test
- Open rovr there
rovr /tmp/test
- Create a new terminal, delete the folder
rm -rf /tmp/test
- Watch the crash happen
What is the expected result of the steps?
I expect it to be alive at least, realise that it is in a broken directory, and try up to as much parent directory as possible
What actually happened after doing the steps?
Death
Affected Operating System(s)
How can this be fixed?
Make change watcher keep the current directory as a variable, so if getcwd fails, keep going up the parent until something works. But if root doesn't work, just die, I will blame the end user for this.
Issue description
The issue happens if in a different terminal, you delete the folder that rovr is currently in, resulting in it not being able to get the current working directory, causing a crash.
How do you reproduce it?
/tmpmkdir testrovr /tmp/testrm -rf /tmp/testWhat is the expected result of the steps?
I expect it to be alive at least, realise that it is in a broken directory, and try up to as much parent directory as possible
What actually happened after doing the steps?
Death
Affected Operating System(s)
How can this be fixed?
Make change watcher keep the current directory as a variable, so if getcwd fails, keep going up the parent until something works. But if root doesn't work, just die, I will blame the end user for this.