Ripgrep output not parsed correctly when search path is on a network drive

[mattia72]

Bug Description

When using DRipGrepper to search within a directory located on a network drive (e.g., mapped drive like Z:\ or UNC path like \server\share), the output from ripgrep (rg.exe) is not parsed correctly by the application. This results in missing or malformed search results in the GUI.

Steps to Reproduce

1. Open DRipGrepper.
2. Set the search path to a network drive (e.g., \\tsclient\c\Projects\MyCode).
3. Run a search.
4. Observe the results: Not an absolute or relative path\tsclient...

Expected Behavior

Ripgrep output should be parsed and displayed correctly regardless of whether the search path is local or on a network drive.

Environment

• DRipGrepper version: [insert version]
• OS: [insert OS version]
• Ripgrep version: [insert rg version]
• Network drive type: [e.g., SMB, NFS, etc.]

Additional Context

This issue does not occur when searching local paths. It seems the parsing logic may not handle certain path formats or line endings correctly when the source is a network location.