Comments (5)
There is a PR #4 in the works. Meanwhile you can check out this custom component that I created based on (but independent of) this PR that does the same. It is a lua table, but you can just convert that to json and put it in your task.json
file
from overseer.nvim.
As Ranjith said, that PR should address this and is in-progress but not finalized. There are some API changes I'd like to make to it before merging. It's been pending for a while because I've had a whole lot going on at work and outside of work, and requests on my open source projects have piled up. Just this last week I've started making headway on the backlog, but I'm out of time again for today. I hope to be able to come back and finish this one up no later than the end of next weekend.
from overseer.nvim.
@krishnakumarg1984 after taking another look, your ask is actually independent of that PR. The issue was much simpler: the necessary problemMatcher wasn't included (because it was in the vscode-cpptools extension).
If you get the most recent master and change your tasks.json
to have this line: "problemMatcher": "$gcc"
, that's all that's required to parse the output into diagnostics.
If you then make sure that you have the on_result_diagnostics_quickfix
component (with open = true
to auto-open quickfix), that should be all you need. This could look like:
require("overseer").setup({
component_aliases = {
default = {
-- These are the default components listed in the README
-- You probably want to keep them
"on_output_summarize",
"on_exit_set_status",
"on_complete_notify",
"on_complete_dispose",
-- This puts the parsed results into the quickfix
{ "on_result_diagnostics_quickfix", open = true },
-- This puts the parsed results into neovim's diagnostics
"on_result_diagnostics",
},
},
})
from overseer.nvim.
@ranjithshegde and @stevearc Thank you for your responses, and thank you for trying to address this request.
I updated the overseer setup call to use the above suggested table, and updated the problemMatcher
line in tasks.json
to use $gcc
, and even after updating to the latest commit of overseer
, I still am not able to make this work. i.e. the quickfix window does not open. In fact, the quickfix window seems to not even contain diagnostics. After :OverSeerRun
and :OverSeerToggle!
, I am getting some garbled characters in the overseer split. Please see the screenshot below which hopefully illustrates these problems.
- The problematic source code in the top right split
- Manually opened (with
:copen
) empty quickfix window in bottom right - Overseer window (with
:OverSeerToggle!
) in the left split
from overseer.nvim.
Some questions:
- In your initial
tasks.json
file, you used the key"problemMatchers"
instead of"problemMatcher"
. Have you corrected that? - If you expand the task all the way in the overseer list (default bound to
L
), do you see a "problem_matcher: " line underneath thevscode.result_vscode_task
component?
- What does the full output of the command look like if you open the terminal?
from overseer.nvim.
Related Issues (20)
- bug: `$eslint-stylish` triggers error HOT 2
- feature request: ToggleTerm strategy - go to previous window on terminal close
- feature request: Is there any way to create custom strategy?
- feature request: strategy to read output from a log file instead of stdout and stderr
- bug: The sidebar buffer doesn't render after opening overseer before job start HOT 2
- bug: The scroll doesn't work with the toggleterm strategy when opening a preview
- feature request: Hidden vscode tasks HOT 3
- bug: Wrong autocomplete parameters with enum type
- bug: Orchestrator strategy undefined behavior HOT 1
- bug: open vsplit doesn't open (split) on the right HOT 1
- bug: telescope picker not shown but a fallback HOT 1
- feature request: [windows] remove (nonstandard?) escape sequences
- on_result_diagnostics_quickfix.set_empty_results not clearing diagnostics list HOT 1
- -
- bug: Targets from included Makefile only visible on first execution HOT 3
- bug: shell escape single quote HOT 2
- bug: How to keep in task log window HOT 2
- feature request: OverseerToggle!top
- How to change select multi parameters( TAB is no effect)
- bug: ephemeral docker containers do not stop HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from overseer.nvim.