Skip to content

Conversation

@spookylukey
Copy link
Collaborator

As per #340, when on Windows, attempting to commit (c c) opens up additional tabs in VS Code, which must be closed first, before the COMMIT_EDITMSG tab will work. If you just ignore these extra tabs and use COMMIT_EDITMSG, committing fails silently (which is quite annoying as the commit message you typed is lost).

For example, if the current project is in C:\Users\luke\devel\edamagittest (no space), then attempting to commit produces this:

ksnip_20250919-105347

If the path has a space in it, like C:\Users\luke\devel\edamagit test, then you get further additional tabs, like this:

ksnip_20250919-105008

I have seen the bug on multiple Windows machines (at least 3). This bug also affects other platforms if the project folder has a space in it, as noted in the bug report.

This PR fixes it. I have verified that the fix works both for Windows and for Linux.

Fixes #340

Thanks so much for your time, and all your work on edamagit which is awesome. It would be super helpful to the junior members of my team (whom I've got started using edamagit) if this bug fix could be merged and a new release done, thanks!

This fixes issues with paths that have spaces in them, and all Windows paths.

Fixes kahole#340
@spookylukey spookylukey force-pushed the fix/340-quote-instance-path branch from 733f24a to d2a5ff2 Compare January 5, 2026 09:05
@spookylukey spookylukey merged commit d5bf9fc into kahole:develop Jan 5, 2026
1 check passed
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.

Wrap COMMIT_EDITMSG path in quotes to handle spaces when opening VS Code commit editor

1 participant