GoUpAlign and GoUpAlignTop will align the second line to top instead of the first one.

[swahpy]

Screen.Recording.2025-01-09.at.14.26.24.mov

hi, from the screen record we can see that when align to top using GoUpAlign or GoUpAlignTop, it will set the second line to top. Below is my configuration.

{
    "nullromo/go-up.nvim",
    event = "WinScrolled",
    opts = {}, -- specify options here
    config = function(_, opts)
      local goUp = require "go-up"
      goUp.setup(opts)
    end,
  }

[nullromo]

Thanks for the issue report.

From the screen recording, I can see your vim window has an extra line at the top. There’s the tabline, which says “init.lua mappings.lua markview.lua” and then there’s another line with some kind of breadcrumb showing “plugins > init.lua > return”.

Do you know which of your other plugins is producing that breadcrumb line? I haven’t seen that before, but I’m guessing it’s built with an extmark. If you point me to the cause of that line, I could probably provide a fix that makes go-up aware of it.

[swahpy]

Thanks for the issue report.

From the screen recording, I can see your vim window has an extra line at the top. There’s the tabline, which says “init.lua mappings.lua markview.lua” and then there’s another line with some kind of breadcrumb showing “plugins > init.lua > return”.

Do you know which of your other plugins is producing that breadcrumb line? I haven’t seen that before, but I’m guessing it’s built with an extmark. If you point me to the cause of that line, I could probably provide a fix that makes go-up aware of it.

yes. it is breadcrumb from lspsaga.

[nullromo]

@swahpy I added an option called alignOffsetLines, which you can set to { top = 1 } in your case to fix the problem.