bug: Overseer buffers should not allow swapping (bad Neotree interactions)

[HugoPeters1024]

Neovim version (nvim -v)

0.11.4

Operating system/version

MacOS 26.1

Describe the bug

The problem is as follows, when opening a file using neotree, it chooses to replace the buffer you last come from. When this buffer is the overseer task manager, it means my file opens is the little bottom pane of overseer where normally the lists of tasks are, which is very annoying and unhelpful. I imagine that this problem is not specific to neotree and applies to other buffer swapping plugins as well.

I'm not 100% sure if Overseer is to blame for this bug, but I figured that if an option exist to make a buffer non-eligible for opening another file/input, this would be an amazing and robust solution.

Interested to hear what's possible and to learn more :). And thank your for the plugin, I'm use it daily and with pleasure <3

What is the severity of this bug?

minor (annoyance)

Steps To Reproduce

1. Install overseer and neotree
2. over both overseer and neotree as sidebars, as well as a main buffer
3. jump from the main buffer to the overseer sidebar
4. then jump to the neotree buffer
5. select a file and press enter
6. The file gets opened in the overseer sidebar instead of the main buffer

Expected Behavior

At (6.), The file gets opened in the main buffer instead

Minimal example file

No response

Minimal init.lua

This is the relevant config I use for neotree and overseer, but I'm pretty sure that it's not relevant to the issue:


      require("overseer").setup({
        task_list = {
          bindings = {
            ["<C-j>"] = false, -- disable default <C-j>
            ["<C-k>"] = false, -- disable default <C-k>
            ["<C-h>"] = false, -- disable default <C-h>
            ["<C-l>"] = false, -- disable default <C-l>
          },
        },
        -- Override default component alias to remove automatic disposal
        component_aliases = {
          default = {
            { "display_duration", detail_level = 2 },
            "on_output_summarize",
            "on_exit_set_status",
            "on_complete_notify",
            -- Removed "on_complete_dispose" to prevent automatic task disposal
          },
        },
      })


      require("neo-tree").setup({
        window = {
          mappings = {
            ["f"] = "none", -- Disable 'f' to allow 'ff' for telescope
          },
        },
        filesystem = {
          follow_current_file = {
            enabled = true
          },
        },
      })

Additional context

No response

[seppeon]

I see the same issue.