Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplicate entries in :ZkBacklinks #189

Open
2 tasks done
WhyNotHugo opened this issue Sep 17, 2024 · 1 comment
Open
2 tasks done

Duplicate entries in :ZkBacklinks #189

WhyNotHugo opened this issue Sep 17, 2024 · 1 comment

Comments

@WhyNotHugo
Copy link
Contributor

WhyNotHugo commented Sep 17, 2024

Check if applicable

  • I have searched the existing issues (required)
  • I'm willing to help fix the problem and contribute a pull request

Describe the bug

Entries for :ZkBacklinks are all duplicate. If I call require("fzf-lua").lsp_references(), all entries shown are also duplicated.

If I remove require("zk").setup({}) from the config, the picker for require("fzf-lua").lsp_references() no longer duplicates entries.

How to reproduce?

  1. Ensure that the configuration file includes require("zk").setup({}).
  2. :ZkBacklinks

zk configuration

[notebook]
dir = "~/zk"

[note]
filename = "{{id}}"

[format.markdown]
hashtags = true
link-format = "[{{title}}]({{rel-path}})"

[lsp.diagnostics]
dead-link = "error"

[alias]
n = "zk new"
e = "zk edit --interactive"
journal = "zk new --no-input ~/zk/journal/"

[group.journal]
paths = ["journal"]

[group.journal.note]
filename = "{{format-date now}}"

Neovim configuration

I don't have a minimal template yet, full config is:

https://git.sr.ht/~whynothugo/dotfiles/tree/f34b44434fa8a103e764584ea618dbdef301a438/item/home/.config/nvim/init.lua

Environment

zk 
system: Linux 6.10.10-0-edge x86_64 Linux
NVIM v0.10.0
Build type: MinSizeRel
LuaJIT 2.1.1710398010
Run "nvim -V1 -v" for more info
@tjex
Copy link
Member

tjex commented Sep 18, 2024

(deleted my last comment. Didn't read properly the first time around).
I can confirm this is happening for me too, and it could well be the same behaviour I noticed in #185

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants