Use the correct relative-path separator under Windows#32
Open
nonk123 wants to merge 1 commit into
Open
Conversation
darcamo
requested changes
Nov 23, 2025
darcamo
approved these changes
Nov 23, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For reasons I cannot comprehend, having
ci-run-argumentsset to a non-empty string and executingM-x ci-run-last-target(on Windows 10) produces the following error message:Replacing the forward-slash
/with a backslash\solved the issue, at least for my case.What confuses me the most, is that this issue never occurred until I decided to set
ci-run-arguments. Running executables with the forward-slash/separator (./dwarfpaper.exe) but without the args, worked fine all this time I've been using the package.Let me know if you have any suggestions for this PR.