feature request: Snacks.terminal strategy

[franroa]

Did you check existing requests?

• [x] I have searched the existing issues

Describe the feature

Hi, I was thinking that having a snacks.terminal in overseer would be really awesome: https://github.com/folke/snacks.nvim/blob/main/docs/terminal.md

What are your thoughts about it?

Provide background

No response

What is the significance of this feature?

nice to have

Additional details

No response

[gou4shi1]

+1

[somethingteste]

yes

[stevearc]

I am currently in the middle of a rather large refactor, and as part of that I am actually moving away from custom strategies like toggleterm or snacks. I am pretty confident that this is the correct direction for the project, but open to learning more and potentially changing my stance.

Could any or all of you explain in as much detail as you are willing: what is the workflow you are hoping to achieve with a snacks.terminal integration? How are you using overseer now, and what is the gap that a snacks.terminal strategy would unlock?

[franroa]

In my case, I would like to be able to configure the overseer tasks with the snacks terminal customization. I have a very stupid prototype working right now in my local fork. With this, I can leverage the snack terminal config (like auto_scroll, direction, etc...):

function SnacksStrategy.new(opts)
  opts = vim.tbl_extend("keep", opts or {}, {
    use_shell = false,
    size = nil,
    direction = nil,
    highlights = nil,
    auto_scroll = nil,
    close_on_exit = false,
    quit_on_exit = "never",
    open_on_start = true,
    hidden = false,
    on_create = nil,
  })
  local strategy = {
    opts = opts,
    term = nil,
  }
  setmetatable(strategy, { __index = SnacksStrategy })
  ---@type overseer.SnacksStrategy
  return strategy
end

Forthermore, if I could send the tasks to the snack terminal I can reuse "snack_terminal" filetype on my autocommands and also list the "overseer" terminals within the snack list

[hergaiety]

Snacks' explorer and pickers are consistent across nearly every part of my workflow except for overseer. That's a big reason it'd be ideal to see an integration, consistent UX