Steps to reproduce
Create a new vault with a vault name that is invalid on the current operating system (for example, a name containing the : character on Windows).
Expected result
Obsidian should check that the vault name is valid (since it will create a folder with that name to store the vault) and, if it is not, provide the user with an informative error message.
Actual result
Obsidian attempts to create a new folder with the unsanitized name, and if this fails, it displays an uninformative ERRNO number.
Steps to reproduce
- Create a new vault
- Name it anything, ending in a .
- You’ve now got an uneditable, undeletable folder that saves nothing and isn’t recognized by the system.
Did you follow the troubleshooting guide? Yes. I can’t use the sandbox vault to try this bug, since it comes pre-named, but I uninstalled and reinstalled obsidian, made sure I had no theme, plugin (other than the core ones) and css snippets.
Expected result
The folder would be editable and would function as a vault.
Actual result
The folder isn’t seen by windows, is unable to be moved, edited or deleted, and obsidian can’t even open it a 2nd time.
Environment
SYSTEM INFO:
Obsidian version: v1.5.8
Installer version: v1.5.8
Operating system: Windows 10 Home 10.0.22621
Login status: logged in
Catalyst license: none
Insider build toggle: off
Live preview: on
Base theme: adapt to system
Community theme: none
Snippets enabled: 0
Restricted mode: on
RECOMMENDATIONS:
Make obsidian not able to make folders with ‘.’'s at the end.
Make the naming of a new vault have a ping, like the naming of folders in a vault do.
(note, there’s been at least 2 other threads about this issue but they’re both locked, so I had to make a new one)