I'm using msys + vim + ninja + MSVC on windows.
When building, the quickfix list has errors that use the windows path, ie c:\work\folder\file.cpp
Vim handles it ok-ish, it can open the files, but ideally it should translate those into msys style paths, ie /c/work/folder/file.cpp
and better yet, I'm in the C:\work folder, so it should become a relative path, ie folder/file.cpp
The messages are coming back from Ninja, which is using MSVC's cl.exe to build.
If vim is able to resolve your paths correctly and the issue is simply the visual component in the quickfix list, then you can customize its output with quickfixtextfunc (:h qftf) as follows (untested since I don't have a machine running Windows):
set qftf=QuickFixTextFunc
function QuickFixTextFunc(info) abort
if a:info.quickfix
let qfl = getqflist(#{id: a:info.id, items: 0}).items
else
let qfl = getloclist(a:info.winid, #{id: a:info.id, items: 0}).items
endif
let l = []
for idx in range(a:info.start_idx - 1, a:info.end_idx - 1)
let e = qfl[idx]
let fname = bufname(e.bufnr)->fnamemodify(':p')
let fname = 'c:' .. substitute(fname, '/', '\', 'g')
let path = split(fname, ':')
let letter = path[0]
let fname = letter .. substitute(join(path[1:], ''), '\', '/', 'g')
let lnum = e.lnum
let col = e.col
let type = e.type
call add(l, fname .. '|' .. lnum..' '.. col .. '|' .. e.text)
endfor
return l
endfunction
The quickfix entries should looks like this:
In BuildToolsWrapper I have a hook for translating cygwin pathnames into gvim(-win32) pathnames.
The approach I've taken consists in piping make/ninja... output into another program that'll do the translation. It's done directly in the &makeprg option.
It could be done in pure vimscript as well. For instance, I have a filter that changes filenames after the compilation (event triggered on QuickFixCmdPost) where i do some dark magic in order to update the buffers registered in the quickfix list: https://github.com/LucHermitte/vim-build-tools-wrapper/blob/project/compiler/BTW/substitute_filenames.vim
I think this approach/workaround is convoluted and best avoided, and we should prefer filtering error messages (and thus changing filenames) directly in the &makeprg.
