Skip to content

Add Support for WSL Environments With Windows-stored Obsidian Vaults#84

Merged
Yakitrak merged 5 commits into
Yakitrak:mainfrom
hGriff0n:wsl-support
Feb 13, 2026
Merged

Add Support for WSL Environments With Windows-stored Obsidian Vaults#84
Yakitrak merged 5 commits into
Yakitrak:mainfrom
hGriff0n:wsl-support

Conversation

@hGriff0n

Copy link
Copy Markdown
Contributor

Description
Modifies the obsidian path resolution logic to include an additional check before failing in the case the user is running in WSL. The path resolution will instead do an additional lookup in the users Windows home directory (which is mounted for access from WSL) for the obsidian config
Modifies the vault path resolution logic to include an additional check in the case that we are in a WSL environment. If the received vault path is a windows file path, then we translate it into the WSL-mounted equivalent.

Checklist:

  • I have written unit tests for my changes.
  • [-] I have updated the documentation accordingly.
  • All new and existing tests passed.

hGriff0n and others added 5 commits February 13, 2026 13:39
Intention is to be on top of #76 but I didn't realize it wasn't from a branch
If we're reading into the windows-stored config.json, then the paths are going to be windows filepaths. This simply applies the same "mnt translation" from the config path lookup to the vault path.
Previously adjustForWslMount only handled C: drive paths. Now detects
any drive letter (A-Z) and translates to the corresponding /mnt/ path.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@Yakitrak Yakitrak merged commit 79d67a2 into Yakitrak:main Feb 13, 2026
TriplEight added a commit to TriplEight/notesmd-cli that referenced this pull request Feb 17, 2026
getPathForVault matches by strings.HasSuffix(path, name), so vault
names must be a suffix of the configured path. The original tests used
arbitrary keys ('windows', 'secondary', 'linux') that never matched,
causing all three WSL tests to fail since PR Yakitrak#84.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants