Skip to content
This repository has been archived by the owner on Dec 18, 2024. It is now read-only.

The process cannot access the file because it is being used by another process. (os error 32) #4

Closed
DiscreteTom opened this issue Dec 17, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@DiscreteTom
Copy link
Owner

Platform: windows11

@DiscreteTom DiscreteTom added the bug Something isn't working label Dec 17, 2023
@DiscreteTom
Copy link
Owner Author

RipGrep's error messages are emitted in stderror, and at the same time the stdout may hold normal output. See BurntSushi/ripgrep#149

However in vscode-riprep-utils we throw error and disgard the stdout if stderr is not empty. This behaviour should be modified.

https://github.com/DiscreteTom/vscode-ripgrep-utils/blob/1faab03edeaff9aae9030f8171160f70b12618de/src/exec.ts#L35-L37

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant