Tony Chen

I think that’s reasonable; it probably makes sense to include something like this if no other plugin implements this, given that a lot of the sign placing and refresh infrastructure...

Can you convert this to a pr and I’ll review it more closely? Alternatively I can take the lead on this if you don’t have time

This is expected behavior: if you tell neovim to not save mark information by disabling shada, then close/reopen the buffer, neovim has no way to remember what marks you set...

Can you please check again on latest master if this problem persists? I just pushed a fix to another issue that may have also solved this one.

Persisting bookmarks across buffer delete will be possible, but a little more effort to support. As far as I can tell, vim-signature doesn't do this either; markers disappear once you...

Telescope integration would be cool, but should probably be implemented in a separate plugin. I’d rather not add and maintain support for another plugin that I don’t personally use

I'm reopening this issue because ideally the plugin would expose bookmark information in a more easily accessible way rather than requiring any telescope extension to plumb through `require'marks'.bookmark_state`.

Use the `excluded_filetypes` key in the config table.

Can you post your config? Just from your description, this doesn't sound like a bug, as I would expect a built in mark to show up if you have `builtin_marks`...

If you want the `.` mark to show up in buffers but not in popups, you should probably use the `excluded_filetypes` keyword to disable mark tracking in those popups. Currently,...