dotfiles VS navi

You put your snippets in a lua file, like here (with syntax according to the luasnip documentation) and invoke such file somewhere in your configuration so that it's required (i. e. "loaded").

Without knowing your precise folder structure and where you are requiring what is a little hard to understand. However, I do something similar but I have a functions file in my lua folder (without any nested subfolder) and I just require all the .lua stuff in my init.lua here.

Some examples here, but as other users suggested it's vim.filetype.add().

You can find my snippets here: to be honest they are rather simple, so creating such doesn't take me too long. In general I would say either style is fine (or equally ugly :p).

Whilst at the moment I do not have time to go through your config, this is my noice config and my lsp. You can copy&paste, I have borders set and normal highlight window. It works, so just copy it and then work back till you add yours.

If it can be of help this is my noice configuration and lsp setup. It is working fine for me and I tested updating everything right now.

See examples here.

Here - it is just a config file with a few functions: use it as inspiration! The code is probably not optimised yet (I just got it working and I wanted to share, do let me know if you can make it better): mappings to operate

I use navi and I am very satisfied: it's very easy to create your own cheatsheets, see for instance what I do here.

It is macOS with iTerm2 and zsh as shell. The DE is the standard one that comes pre-installed, I didn't make changes; you can find my configurations here

I've built something similar for myself (fzf+a bit of shell). But I realized that fzf's history view (with very long history buffer) works much better for my use case.

I still needed something to cover rare commands with dynamic arguments. That got covered by Navi: https://github.com/denisidoro/navi (takes more friction to add new command than with TBMK, but you get much more organized and easier to search tool).

navi repo add denisidoro/navi-tldr-pages Cloning https://github.com/denisidoro/navi-tldr-pages into /home//.local/share/navi/cheats/tmp... Cloning into '/home//.local/share/navi/cheats/tmp'... remote: Enumerating objects: 1841, done. remote: Counting objects: 100% (1841/1841), done. remote: Compressing objects: 100% (1756/1756), done. remote: Total 1841 (delta 83), reused 1839 (delta 83), pack-reused 0 Receiving objects: 100% (1841/1841), 504.71 KiB | 1.95 MiB/s, done. Resolving deltas: 100% (83/83), done. Hey, listen! navi encountered a problem. Do you think this is a bug? File an issue at https://github.com/denisidoro/navi. Caused by: 0: Failed to import cheatsheets from `denisidoro/navi-tldr-pages` 1: Failed to get cheatsheet files from finder 2: Failed to pass data to finder 3: Unable to prompt cheats to import 4: Broken pipe (os error 32)

Similar projects (in a way): navi

I think navi is a better alternative. You can create custom cheats too.

navi might help you with that

I like using navi, but idk if you want something that runs in the terminal.

There's also a cli program called tealdeer that does this kind of thing and uses a local cache. And there's a fuzzy search interactive cli cheatsheet program called navi that's also pretty cool (and you can write your own cheatsheets).