Issue:
On Windows, when providing an absolute path that contains spaces, the application incorrectly resolves it relative to the Obsidian vault directory instead of treating it as an absolute path.
Example path:
C:\Program Files (x86)\Nodist\bin
Even when the path is wrapped in quotes, it is still interpreted as relative and searched inside the Obsidian directory (e.g. C:\Users\...\Obsidian\...), resulting in an error.
Workaround used:
We were able to make it work by using the 8.3 short path instead:
C:\PROGRA~2\Nodist\bin
This confirms the issue is related to space handling / absolute path resolution, not path validity.
Expected behavior:
- Absolute paths should always be respected
- Paths containing spaces must not be re-resolved relative to the vault
- Proper absolute-path detection should be enforced on Windows
Why this matters:
- Paths with spaces are extremely common on Windows
- This breaks integrations, scripts, and external tools
Let me know if logs or a minimal reproduction case are required.
Issue:
On Windows, when providing an absolute path that contains spaces, the application incorrectly resolves it relative to the Obsidian vault directory instead of treating it as an absolute path.
Example path:
C:\Program Files (x86)\Nodist\binEven when the path is wrapped in quotes, it is still interpreted as relative and searched inside the Obsidian directory (e.g.
C:\Users\...\Obsidian\...), resulting in an error.Workaround used:
We were able to make it work by using the 8.3 short path instead:
C:\PROGRA~2\Nodist\binThis confirms the issue is related to space handling / absolute path resolution, not path validity.
Expected behavior:
Why this matters:
Let me know if logs or a minimal reproduction case are required.