nvf icon indicating copy to clipboard operation
nvf copied to clipboard

`fidget.nvim`: `notification.override_vim_notify` not working

Open derethil opened this issue 7 months ago • 1 comments

I have confirmed that this is a bug related to nvf

  • [x] This is a bug, and not an user error or a support request. I understand that my issue will be closed if it is not a bug in nvf.
  • [x] I have checked the issues tab and confirmed that my issue has not yet been reported. I understand that my issue will be closed if it is a duplicate.

Description

The option to override vim_notify doesn't seem to be working as expected. I reproduced the issue with the following config:

vim.visuals.fidget-nvim = {
  enable = true;
  setupOpts = {
    notification = {
      override_vim_notify = true;
    };
  };
};

and running :lua vim.notify("hello, world") did not create a fidget.nvim notification.

Overwriting it manually does work as a workaround.

vim.luaConfigRC.fidget_notify = ''
  vim.notify = require("fidget").notify
'';

Installation Method

Standalone (flake outputs, nix profile install, etc.)

Installation Method (Other)

I am creating a standalone flake that installs and manages NVF.

nvf Version

flake input - master

Reproduction steps

  1. Set up minimal configuration and run Neovim
  2. Try running vim.notify
  3. Observe that no fidget notification was created

Expected behavior

fidget.nvim should overwrite vim.notify as expected

Actual Behavior

vim.notify is unchanged from its standard behavior

💻 Metadata

- system: `"x86_64-linux"`
 - host os: `Linux 6.15.5-arch1-1, EndeavourOS, noversion, 2022.08.28`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.28.3`
 - nixpkgs: `/nix/store/lwncz8ms8l9s8riq1z0ans5ksgnmfdxk-nixpkgs/nixpkgs`

📝 Relevant log output

N/A - if someone can point me towards getting log output, I'll gladly put it here

derethil avatar Jul 19 '25 21:07 derethil

oof another lazy-loading bug - fidget isn't loaded when you called vim.notify()

not sure what the best way to fix this is, maybe we can override vim.notify ourselves, outside of the lazy loading setup

horriblename avatar Sep 23 '25 08:09 horriblename