kok.nvim VS sad

In the examples listed on this page https://github.com/ms-jpq/coq_nvim, there is a pattern overlay over the whole screen. Is there a neovim plugin that does this? Thanks.

nvim-cmp or coq_nvim is for autocompletion. Treesitter is for parsing language syntax. (I guess the most typical use case for this would be syntax highlighting.) Note that (neo)vim also has built in manual completion that you can use by setting up your omnifunc and triggering it with in insert mode .

Aw man that's not nice to hear. I have had my own struggle with lsp not gonna lie. I used to use coc until it got too slow, after struggling for like 2 days lol lsp is working fast and neat. I'd suggest you to take a look at coq https://github.com/ms-jpq/coq_nvim which claims to be fast as fuck (literally lol) and also claims to be faster than lsp (because its written using c or something). Haven't tried it personally

Coq_nvim

I'm attempting to use (coq_nvim)[https://github.com/ms-jpq/coq_nvim]. This is my config:

Does your coq_nvim and nvim-lspconfig really load? Because they have opts = true

I'd be happy for someone who knows more about this to correct me. But in my experience as well, nvim-cmp is not as good completion as vscode, its suggestions can be all over the place sometimes. I found that coq_nvim tends to better in this regard. I still prefer nvim-cmp for other reasons but you should definitely try coq_nvim out and see if you have a better experience.

Coq_nvim isn't the same as Coc.nvim. Coq is a completion plugin with lots of caching written in Python that works alongside the builtin LSP. Coc is an LSP client (and has it's own plugin ecosystem) written in Node.

There are some like https://github.com/SirVer/ultisnips and https://github.com/ms-jpq/coq_nvim. Speed is not really an issue, I guess people just prefer to have fewer dependencies and use lua which is already bundled in neovim.

Maybe using coq.nvim instead of nvim-cmp could help (?) dince it caches the LSP responses. I haven't test it, though

also check out sad a more intuitively named sd that allows for fancy pipe input

If i were to write this in a faster language, it would be in Rust, since I already have a relativly successful CLI text edit tool written in it, and it's fast as fuck too.

Here is link number 1 - Previous text "sad"

https://github.com/ms-jpq/sad - when you need PCRE in sed

what you really want is sad, https://github.com/ms-jpq/sad

sad CLI search and replace | Space Age seD tcount Count your code by tokens, types of syntax tree nodes, and patterns in the syntax tree. A tokei/scc/cloc alternative. nushell A new type of shell fclones Efficient Duplicate File Finder hunter The fastest file manager in the galaxy! teip Select partial standard input and replace with the result of another command efficiently cb Command line interface to manage clipboard semiuniq A uniq-like tool for removing nearby repeated lines in a file" dua-cli View disk space usage and delete unwanted data, fast. htmlq Like jq, but for HTML. pipecolor A terminal filter to colorize output crowbook Converts books written in Markdown to HTML, LaTeX/PDF and EPUB delta A viewer for git and diff output mdcat cat for markdown pueue Manage your shell commands. gitui Blazing 💥 fast terminal-ui for git written in rust 🦀 pipr A tool to interactively write shell pipelines. rename Rename your files using your favorite text editor bropages Highly readable supplement to man pages from http://bropages.org. Shows simple, concise examples for commands with syntax highlighting. html2md convert simple html documents into markdown bk Terminal Epub reader rs A safe Rust crate for working with the Wayland clipboard. viu Simple terminal image viewer written in Rust. alacritty A cross-platform, OpenGL terminal emulator. wezterm A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust

Check it out at my github

sad

Thanks, if you like it you can also try my batch text editor.