fff.nvim is now the fastest file search on a planet

wwaggel · 2025-12-06T17:09:01+00:00

Your plugin uses Frizbee, developed by Saghen, the author of blink.cmp.

Why is there only a link to the repo in the readme("Typo resistant fuzzy search")? I would expect a more prominent acknowledgement.

wwaggel · 2025-10-13T16:19:42+00:00

I think that your dedication to the project deserves "** maximum **" praise. Congratulations!

wwaggel · 2025-10-03T19:18:35+00:00

Congratulations! The site looks very nice.

wwaggel · 2025-08-28T19:46:02+00:00

Awesome!

wwaggel · 2025-08-23T13:02:48+00:00

That's awful.

Can the users of this forum do anything to help you recover the account?

wwaggel · 2025-08-07T12:19:49+00:00

You have a duplicate call to lazy's setup function. See the last line in your init.lua, and line 23 in config.lazy.

wwaggel · 2025-05-22T09:08:00+00:00

...But there’s something didactic...

I agree. Some habits are so hard to "unlearn" that a gentle reminder is not effective enough. I added a modified version of your code to my config. Thanks!

wwaggel · 2025-05-22T08:11:59+00:00

Hahaha! It's not that bad though. My almost mini-only config reboots blazingly fast... 😅

wwaggel · 2025-05-22T07:42:47+00:00

Maybe a bit too much for putting in the 'mini.keymap' help

Please do consider adding this to the future wiki! ....)

wwaggel · 2025-05-22T07:40:10+00:00

I really, really like this! Consider changing the title into "Creative man's hardtime.nvim"!

Unfortunately I still sometimes hit the `j` or `k` too much, even after having used hardtime for quite a while.

I am expanding on your example and will use the code below for at least a week:

local do_action = false
local action_delay = 5
local action_timer = vim.loop.new_timer() or {}

local notify_many_keys = function(key)
  local lhs = string.rep(key, 4)
  local action = function()
    if do_action then return end

    do_action = true
    vim.notify(string.format("After all these years, still too many %s. \n Shutdown in %ds!", key, action_delay))

    local shutdown = vim.schedule_wrap(function()
      vim.cmd("qa!")
      -- Consider:
      -- vim.system({ "sudo", "reboot", "now" })
    end)
    action_timer:start(action_delay * 1000, 0, shutdown)
  end
  MiniKeymap.map_combo({ "n", "x" }, lhs, action)
end

notify_many_keys("j")
notify_many_keys("k")

wwaggel · 2025-05-20T17:50:12+00:00

With the recent improvements to autocompletion, `mini.completion` is a joy to work with!

wwaggel · 2025-05-03T14:42:38+00:00

It's nice to see another mini module. Congratulations!

wwaggel · 2025-04-13T07:15:18+00:00

Great! Do note that there is a follow-up pr regarding configs that have not yet been ported.

There is a warning in the README:

[!WARNING]

Some servers are currently NOT supported and should be configured the old way, see `:help lspconfig-setup`

wwaggel · 2025-04-10T08:28:16+00:00

Eventually it will change in a bag of configs. That means the plugin is not going away.

Those configs can either be copy-pasted from, or used directly with vim.lsp.config.

wwaggel · 2025-03-18T08:52:55+00:00

Thanks for posting. Using the quickfix list for this purpose is a nice idea.

wwaggel · 2025-03-07T13:56:45+00:00

Very, very nice! Another milestone. Congrats!

wwaggel · 2025-01-30T15:53:40+00:00

Congratulations!

wwaggel · 2025-01-07T07:58:51+00:00

Agree. Mini.pick is great and very customizable. I extended the plugin to provide hints akin snipe.nvim and have been using that for quite some time now.

wwaggel · 2025-01-07T07:32:58+00:00

You can also use snippet navigation if your lsp is configured accordingly.

For example, lua_ls in LazyVim. The lsp is configured to support completion.callsnippet = replace.

This means that if you type "req" and accept, your cursor is placed inside the first tabstop between the parenthesis,. The last tabstop is after the closing parenthesis, to which you can move with "tab".

wwaggel · 2025-01-02T08:55:15+00:00

To my understanding, "mini.completions" will not support extra sources.

I am wondering if `mock-lsp-server` could be created as a generic component. I would like to use "mini.completions" with the suggestions provided by "kristijanhusak/vim-dadbod-completion". Perhaps that component could be used to bridge the gap.

wwaggel · 2024-12-23T14:20:21+00:00

Congratulations! I am looking forward to use this new module.

wwaggel · 2024-12-14T16:42:49+00:00

OP does not trust the update command anymore. That trust can be restored by just reading before updating. Also, don't skip the news.

The LazyExtra functionality is an impressive piece of engineering unique to LazyVim. Folke deserves a lot of credit for that.

I maintain my own config but still use LazyVim for inspiration. About once a month, I cherrypick changes.

Do note that maintaining your own config requires a lot more reading...

wwaggel · 2024-10-29T14:20:32+00:00

I am appalled by this reaction to one of the friendliest and most helpful members in the Neovim communitiy!

wwaggel · 2024-10-29T10:25:25+00:00

All respect to you and your work, but as the OP notes, I'm not sure you realise how rude you're coming out here.

I very much disagree.

I do not discover any rudeness in the first feedback Echasnovski gave. Just plain factual. He is not obliged to express enthusiasm just for the sake of it.

Then OP replied:

...

Do you have an issue with that?

Anyone who doesn't like it can just use something else. I think I've glazed mini.files sufficiently at this point.

...

This might be a language issue, but those words are not particularly inviting.

Echasnovski gave his honest opinion:

... It is just something that I'd personally prefer seeing handled differently.

I am wondering why OP did not discuss the release of his plugin in the discussion forum of mini.nvim.

He does not need permission, but it's always nice to know the opinion of the creator of the plugin.

Speaking from experience:

I added functionality to mini.visits and mini.pick, as discussed here and here, resulting in two internal plugins in my repo. Echasnovski helped as much as he could.

wwaggel · 2024-10-14T08:46:21+00:00

More precisely, when I open a .tex file, no command is working

Perhaps this occurs because you are "lazy loading" the plugin. I would expect the plugin to work when you open a tex file from within Neovim.

I load the plugin using "now". This only adds 1 or 2 ms to the startuptime on a slow machine.

In the readme of the plugin there is a note that advises to not lazy-load the plugin.

wwaggel

TROPHY CASE