[FEATURE] Show marksman marks in sign column

[fadedreams]

Feature Request

1. Show marksman marks in the sign column (left gutter)
   • Use vim.fn.sign_place()
   • Only for marksman-managed marks
   • Visually distinct from built-in 'a–'z marks
   • Configurable text or highlight
   • Optional: priority config

Example Config:

require("marksman").setup({
  ui = {
    position = "top_center",
    sign = {
      enabled =  true,
      text = "●",           -- or "M", "◆"
      highlight = "MarksmanSign",
      priority = 50,        -- higher than Vim's default (10)
    },
  }
})

[alexekdahl]

Sounds fair to me! Though, I think it makes more sense to keep the highlight group internal - users should just configure the color directly in the existing highlights table:

highlights = {
  ProjectMarksTitle = { fg = "#61AFEF", bold = true },
  ProjectMarksNumber = { fg = "#C678DD" },
  ProjectMarksName = { fg = "#98C379", bold = true },
  ProjectMarksFile = { fg = "#56B6C2" },
  ProjectMarksSign = { fg = "#61AFEF" },  -- New
},
signs = {
  enabled = true,
  text = "●",
  priority = 50,
}

Keeps the API consistent with how the rest of the plugin works.​​​​​​​​​​​​​​​​

Quick question though - what’s your use case for wanting signs? Is there something missing in the marks window that would solve this instead? I’m asking because priority 50 means diagnostics will override marks on error lines, and git signs will show through when there are changes - so marks would only be visible on “clean” lines. Just want to make sure that fits what you’re looking for.​​​​​​​​​​​​​​​​

[fadedreams]

I agree with keeping the highlight group internal and exposing it via the highlights table — that’s consistent with the rest of the plugin’s API. The proposed config looks great.

I find it convenient to see marks directly in the current buffer as I scroll, just like the default Vim mark behavior, without needing to open the show_marks window.

And yes — I’m okay with marks being hidden under diagnostics or git signs. I want errors and changes to take priority. The sign is just a bonus for clean lines, giving a subtle “at-a-glance” hint when scrolling through sections.

On your follow-up question — “Is there something missing in the marks window that would solve this instead?” —
Great point! It actually just came to mind: it would be awesome if, when opening show_marks, marks from the current buffer were grouped together or visually distinguished (e.g. at the top, with a separator, or highlighted) from marks in other buffers. That way, even without signs, I could instantly see “these are the ones in the file I’m looking at”.
Alternatively (or in addition), a dedicated shortcut to open a filtered view showing only current-buffer marks would be handy — like a “local marks” mode.

Thanks for the thoughtful discussion — really appreciate the care you’re putting into the design!

[alexekdahl]

Thanks for clarifying.

For showing current buffer marks in the UI, I think an indicator next to the mark number would work - something like a small nerdfont icon. Color feels too subtle and reordering would break the goto_1, goto_2 mental model.

Something like this?

│ ● [1] fn_config            current_file.lua      │
│   [2] api_handler          other_file.lua        │
│ ● [3] parse_data           current_file.lua      │

[fadedreams]

I’m totally on board with your suggestion.
Bonus idea (only if you think it fits): maybe make the icon configurable via signs.current_buffer_icon (defaulting to "●") so users can pick something like "▸", "◆", or even a space-padded ">" for terminal-only setups.
But even without that — your current proposal works great as-is.

[alexekdahl]

Hi @fadedreams, I’ve implemented a small proof-of-concept for you to try.
There are still several areas that can be improved, so any feedback would be greatly

#28