I'm having this issue also using an external hard drive. It gets very annoying. There are a few good ways that I can think of fixing this.
The first would be to require that the Backup directory chosen in the preferences already exists. Let TimeVault create subdirectories, but not the root backup dir.
The next option would be to try to guess if they are using an external drive based on conventions. That would mean if the root backup directory exists inside /mnt or /media, then make sure the drive is mounted before backing up to it.
Last option would be to make the option of using an external drive part of the app prefs. Then handle is like above.
I'm having this issue also using an external hard drive. It gets very annoying. There are a few good ways that I can think of fixing this.
The first would be to require that the Backup directory chosen in the preferences already exists. Let TimeVault create subdirectories, but not the root backup dir.
The next option would be to try to guess if they are using an external drive based on conventions. That would mean if the root backup directory exists inside /mnt or /media, then make sure the drive is mounted before backing up to it.
Last option would be to make the option of using an external drive part of the app prefs. Then handle is like above.