[BUG] Links do not work with marksman lsp

[oriyia]

Please confirm

• I am running the latest version of this plugin

Describe the bug
Thank you for such a wonderful plugin. But I can't understand why the links to the files don't work for me. I have marksman lsp. And such types of links as:

• [[link]]
• [[link#Header]]
• [[#Hader]]

they work. Because they are defined in marksman. But if I disable it, then the links will stop working at all.

Additional context

OS:

Linux 6.2.0-31-generic #31~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Aug 16 13:45:26 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

Editor:
$ nvim --version
NVIM v0.9.2
Build type: RelWithDebInfo
LuaJIT 2.1.1692716794

I use the minimum configuration:

require('telekasten').setup({
    home = vim.fn.expand("~/notes/"),
})

[renerocksai]

I am out and about traveling but you need keybindings or else the plugin will never get called. See https://github.com/renerocksai/telekasten.nvim#mappings Ilya Yarusov ***@***.***> schrieb am So., 24. Sept. 2023, 11:31:

…

*Please confirm* - I am running the latest version of this plugin *Describe the bug* Thank you for such a wonderful plugin. But I can't understand why the links to the files don't work for me. I have marksman <https://github.com/artempyanykh/marksman> lsp. And such types of links as: - [[link]] - [[link#Header]] - [[#Hader]] they work. Because they are defined in marksman. But if I disable it, then the links will stop working at all. *Additional context* OS: Linux 6.2.0-31-generic #31~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Aug 16 13:45:26 UTC 2 x86_64 x86_64 x86_64 GNU/Linux Editor: $ nvim --version NVIM v0.9.2 Build type: RelWithDebInfo LuaJIT 2.1.1692716794 I use the minimum configuration: require('telekasten').setup({ home = vim.fn.expand("~/notes/"), }) — Reply to this email directly, view it on GitHub <#285>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHLWBJ6J7H3FNTHEXV5OI3LX374XPANCNFSM6AAAAAA5E2BK5E> . You are receiving this because you were assigned.Message ID: ***@***.***>

[oriyia]

I have already defined keymaps, and they work, but it seems I don't understand something) For example, using the insert_link function, an ordinary link is inserted:

[[note]]

How then to make a clarification on the title or paragraph?) If no hints pop up.

For example, using marksman lsp, when you enter a link, hints appear in a pop-up window. After entering the # header hints.

Tag and link highlighting also doesn't work.

[lambtho12]

How then to make a clarification on the title or paragraph?) If no hints pop up.

At the moment it is not possible to link to a specific title or paragraph automatically. You can only link to the note and must then add manually the title. More advance features would probably require a LSP, which we have not (yet).

Tag and link highlighting also doesn't work.

The highlight groups were changed in the last PR to uniformise everything. Make sure you use the correct ones.

[oriyia]

The highlight groups were changed in the last PR to uniformise everything. Make sure you use the correct ones.

Yes, they are already working!

At the moment it is not possible to link to a specific title or paragraph automatically. You can only link to the note and must then add manually the title. More advance features would probably require a LSP, which we have not (yet).

Hmm, I thought that in the Link notation section it is indicated that such links can be created

- [[A cool title#^xxxxxxxx]]  ....... links to the paragraph with id ^xxxxxxxx within the note
                                      named 'A cool title'

[lambtho12]

Hmm, I thought that in the Link notation section it is indicated that such links can be created

You can use follow_links on these. This will open the proper note at the proper paragraph or heading. But you cannot create them with insert_link automatically. You can only use insert_link to make a link to the note, and then manually edit the link to add the heading.

[kimagin]

If you want the links to work with Marksman, make the home directory ( the one that you defined in Telekasten config) a git directory. Just enough to type in the terminal git init . while you are in that folder.

This should work seamlessly after that :