Custom errorformat for cargo template about overseer.nvim HOT 5 CLOSED

Hmmm...this will take some more thought. We don't want to automatically add the on_output_quickfix component to all the cargo tasks, but we would like to provide a default value for errorformat if the component is added. We would also like to use that in the "set quickfix" action. I have the seeds of an idea for this; will play around with it and see if it works out.

from overseer.nvim.

How are you sending the output to the quickfix? The on_output_quickfix component has a parameter to customize the errorformat.

I also just added some better utilities for customizing the components of a template or template provider.

All together, I think this should do what you want:

  overseer.hook_template("cargo", function(task_defn, util)
    util.add_component(task_defn, {
      "on_output_quickfix",
      errorformat = [[%Eerror: %\%%(aborting %\|could not compile%\)%\@!%m,]]
        .. [[%Eerror[E%n]: %m,]]
        .. [[%Inote: %m,]]
        .. [[%Wwarning: %\%%(%.%# warning%\)%\@!%m,]]
        .. [[%C %#--> %f:%l:%c,]]
        .. [[%E  left:%m,%C right:%m %f:%l:%c,%Z,]]
        .. [[%.%#panicked at \'%m\'\, %f:%l:%c]]
    })
  end)

from overseer.nvim.

How are you sending the output to the quickfix?

I just used an action on task from Telescope.

All together, I think this should do what you want:

Thank you!
Should we hook this by default? Otherwise Cargo messages will have wrong filenames capture.

from overseer.nvim.

I've committed a feature for this. Tasks can now have a default_component_params table:

These values will be used as the default for any params on any components that are both not supplied by the user and defined as default_from_task = true

The "open output in quickfix" action will also search here for the errorformat to use.

from overseer.nvim.

Thank you a lot, a very convenient feature!

from overseer.nvim.