David Barnett
David Barnett
They're mentioned in the helpfile (specifically `:help codefmt-mappings`). Any clarifications you're looking for there?
I think I would want some kind of empty check in the clang-format code regardless, because otherwise there's a correctness issue: `FormatRanges([X, Y])` means "format ranges X and Y", but...
BTW, the tool apparently doesn't support range formatting. Filed https://code.google.com/p/google-rlint/issues/detail?id=4 Another slight problem: No google-rlint tool… They created the repo but haven't pushed any code or file downloads to it:...
If you could add some pointers here for how you'd recommend implementing it, it's not _impossible_ I'd be able to help out.
Also inferring "current test method" would be good, but we can ignore that for v1 since there's some complexity getting that right and exposing it cleanly as a feature.
@martindemello has worked on processing bazel output and might be able to help out here.
Discussed w/ @Kashomon, he suggests quickfix isn't the right paradigm at all and we should consider presenting the full build log w/ annotations so we can support jumping straight to...
No work started. Just have to grab filenames from the command output and `:edit` them manually in the meantime.
Yup, see discussion in #1 and the comment in the description here: > I've also seen the discussion on #1 about how vim's error parsing isn't up to the task...
Welcome! I do encourage you to tinker with the plugin locally and "steal" whatever solutions work for you, and I've just added a note pointing to this PR for anyone...