sqlite.lua VS lazy.nvim

I have been working on restructuring telescope-frecency.nvim. One of the biggest changes is removing dependency for sqlite.lua.

I'd like to share my first real attempt at a Neovim plugin and hopefully get feedback and help on how whether this is something others would be interested in and how to improve it. annotate.nvim is a plugin that allows you set/edit brief notes that are tied to lines in your code. It uses Neovim's extended marks for tracking the location of your notes and kkharji's sqlite.lua plugin to allow you to restore the annotations when you restart Neovim. I'd been experimenting with using scratch buffers to hold notes while working to avoid my habit of cluttering code with comments, but this felt limited. When I saw this plugin I wanted to see if I could combine the ideas to get something more on-demand.

I'm currently working on a plugin that, it appears, is going to require the sqlite.lua package. According to its own README, it would require a couple of sqlite system packages (at least for linux) in order for it to run. However I've also come across some packages that have sqlite.lua as a dependency, but they don't inform the user in the readme about setting up sqlite on the system.

If you need to persist a lot of files, you could use sqlite3 as database through something like sqlite.lua

legendary.nvim v2.5.0 now supports frecency sorting! It will be enabled by default if kkharji/sqlite.lua is also installed.

I think it is. Some neovim plugins such as Telescope which is widely used and praised use SQLite[1]

[1] https://github.com/kkharji/sqlite.lua#-powered-by-sqlitelua

First, I installed NeoSolarized.nvim via lazy.nvim, so the code would be simple like the following one.

In my case, I have switched to Lazy.nvim for all of my Neovim plugin needs ( Thanks again Folke! ), so it would be great if you were at least minimally familiar with how Lazy works as well.

If you've read old tutorials about Neovim configuration you've find the way they create keymaps is a little bit different from what people do now. And if you check other people's configuration sometimes you'll find they create their keymaps using lazy.nvim. This is causing confusion among Neovim users.

The basic plugins will be downloaded on the first run using Lazy, a package manager for Neovim that loads only the necessary plugins as you use them. Once it's done you should be looking at a full-fledged IDE.

it looks more like something is wrong with your neovim install rather than your config. based on this lazy.nvim issue you may have an updated neovim binary but your neovim runtime files are not up to date. try completely reinstalling neovim.

It is possible to manage plugins yourself, but I would recommend a plugin manager such as Lazy (https://github.com/folke/lazy.nvim). There are many more plugins that most would argue are virtually essential, but these should at least be able to get you some autocompletion and highlighting without too much messing about. Be sure to read the install instructions for each of these plugins!

whenever i add this: ``` -- bootstrap lazy.nvim local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim" if not vim.loop.fs_stat(lazypath) then vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", "--branch=stable", -- latest stable release lazypath, }) end vim.opt.rtp:prepend(lazypath)

Easily updatable. Versions are stored in manifests and can be easily updated with a single command. neovim's lazy-lock.json however is managed separately by lazy.

require("keymaps") local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim" if not vim.loop.fs_stat(lazypath) then vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", "--branch=stable", -- latest stable release lazypath, }) end vim.opt.rtp:prepend(lazypath) require("lazy").setup({ "folke/tokyonight.nvim", {"nvim-treesitter/nvim-treesitter", build = ":TSUpdate"}, { 'nvim-telescope/telescope.nvim', tag = '0.1.4', dependencies = { 'nvim-lua/plenary.nvim' } } })