bartste / nvim-project-marks Goto Github PK

Description

There is a problem where performing a certain set of actions makes it so the cursor is teleported to the wrong place, but in the right file when teleporting to a global mark.
Oddly enough, it seems to work fine when you go to the mark via the Telescope selector (builtin.marks).

Expected behaviour

Going to a global mark using 'N goes to the file and line on which the mark was created.

Actual behaviour

Going to a global mark using 'N goes to the file on which the mark was created but to the line on which the most recent deletion of a mark happened.
This happens unless no mark has been deleted in that file.

Steps to reproduce

1. Open NeoVim in folder x with the nvim command
2. Open file a
3. Create a new mark M on a random line
4. Create a new mark N on another line that is different from the line you chose for M
5. Move the cursor to a new, third, line
6. Delete mark M
7. Use the 'N command to go to mark N

This action should teleport you to the third line you chose instead of the expected line marked N.
Going to another file in the same folder and typing 'N should teleport to the file, but to the same wrong line.

More info

NeoVim version:

NVIM v0.9.4
Build type: Release
LuaJIT 2.1.1699392533

Plugin version:

branch main
commit d69997f

Plugin manager:

url     https://github.com/folke/lazy.nvim
version 10.15.1
tag     stable
branch  main
commit  9658486

System:

# System Details Report
---

## Report details
- **Date generated:**                              2023-11-10 20:38:12

## Hardware Information:
- **Hardware Model:**                              Gigabyte Technology Co., Ltd. B550 AORUS ELITE V2
- **Memory:**                                      32,0 GiB
- **Processor:**                                   AMD Ryzen™ 5 5600X × 12
- **Graphics:**                                    AMD Radeon™ RX 6800 XT
- **Disk Capacity:**                               1,0 TB

## Software Information:
- **Firmware Version:**                            FB
- **OS Name:**                                     Arch Linux
- **OS Build:**                                    rolling
- **OS Type:**                                     64-bit
- **GNOME Version:**                               45.1
- **Windowing System:**                            Wayland
- **Kernel Version:**                              Linux 6.6.1-arch1-1

Minimal config

A barebones lazy.nvim setup with this as the only plugin:

return {
    {
        "BartSte/nvim-project-marks",
        lazy = false,
        config = function()
            require("projectmarks").setup({})
        end,
    },
}

Doesn't pick the nvim.The shada file is at the root of a git project file and uses the global one instead, sometimes the local shada file picks up some data, but not the global marks.
I tried it on a clean neovim 9.4-2 on Arch Linux with Lazy.nvim using the default configuration