Showing macro recording was started and finished

[yart]

Did you check docs and existing issues?

• I have read all the noice.nvim docs
• I have searched the existing issues of noice.nvim
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

NVIM v0.9.5 Build type: Release LuaJIT 2.1.1713773202

Operating system/version

ArchLinux Kernel version: 6.8.9-arch1-1

Describe the bug

I'm using NvChad 2.0.

Here is my settings for noice and lualine

return {
  {
    "folke/noice.nvim",
    event = "VeryLazy",
    opts = {
      -- add any options here
    },
    dependencies = {
      -- if you lazy-load any plugin below, make sure to add proper `module="..."` entries
      "MunifTanjim/nui.nvim",
      -- OPTIONAL:
      --   `nvim-notify` is only needed, if you want to use the notification view.
      --   If not available, we use `mini` as the fallback
      "rcarriga/nvim-notify",
    },
    config = function()
      require("noice").setup({
        lsp = {
          -- override markdown rendering so that **cmp** and other plugins use **Treesitter**
          override = {
            ["vim.lsp.util.convert_input_to_markdown_lines"] = true,
            ["vim.lsp.util.stylize_markdown"] = true,
            ["cmp.entry.get_documentation"] = true, -- requires hrsh7th/nvim-cmp
          },
        },
        -- you can enable a preset for easier configuration
        presets = {
          bottom_search = false, -- use a classic bottom cmdline for search
          command_palette = true, -- position the cmdline and popupmenu together
          long_message_to_split = true, -- long messages will be sent to a split
          inc_rename = false, -- enables an input dialog for inc-rename.nvim
          lsp_doc_border = false, -- add a border to hover docs and signature help
        },
        cmdline = {
          view = "cmdline",
        },
        -- routes = {
        --   view = "mini",
        --   filter = {
        --     event = "msg_showmode",
        --     any = {
        --       { find = "recording" },
        --     },
        --   },
        -- },
      })
    end,
    keys = {
      { "<leader>Nt", "<cmd>Noice telescope<cr>", desc = "Show all notifications using Telescope" },
      { "<leader>Nl", "<cmd>Noice last<cr>", desc = "Show the last notification" },
    }
  },
  {
    'nvim-lualine/lualine.nvim',
    dependencies = {
      'nvim-tree/nvim-web-devicons',
      "folke/noice.nvim",
    },
    config = function()
      require("lualine").setup({
        sections = {
          lualine_x = {
            {
              require("noice").api.statusline.mode.get,
              cond = require("noice").api.statusline.mode.has,
              color = { fg = "#ff9e64" },
            }
          },
        },
      })
    end
  },
}

When I type q in normal mode to start recording a macro, I don't see any notification or another sign, that it was started. But the recording goes as usual. And I can use the recorded macros as usual.

Anyway, it's slightly annoying when I can't control this process. Of course, in many cases I don't need any visualization of this process, but sometimes it's needed.

Steps To Reproduce

1. Install NvChad following the instruction here
2. Load my config to ~/.config/nvim/lua/custom/plugins.lua
3. Try to start recording a macro typing q
4. Just be sure, that you don't have any notification about the macro recording starting

Expected Behavior

The macro recording notification must be shown.

Repro

-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/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", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  "folke/noice.nvim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

[ilias777]

Try this:

routes = {
    {
        view = 'notify',
        filter = {
            event = 'msg_showmode',
            any = {
                { find = 'recording' },
            },
        },
    },
}

This is described here

[bbil]

This works ok, and is much better than the recipe from the link. The recipe from the link will also create notifications for entering insert mode!

But I am also not having any luck with integrating this into Lualine like that link suggests... Get an error message around noice not being found.

[dandyrow]

I've also found the same issue when trying to use with Lualine. My LSP is saying that the statusline property of noice is deprecated.

[yart]

Guys, I was incorrect when have been writing this issue. I see the message like @a recording, but I don't see any message after the q key is pressed. So, I can press q randomly and start recording a macro. On the one side this is not a problem: I can stop it any moment, but on the other side this is annoying, because it looks like I'm losing the control.

I've tried to catch the moment when I pressed q and show a notification with this, but it looks like pressing q pausing other processes and I see both notifications (about pressed and the macro recording) at the same time, when chosen the register.

So, if somebody knows a solution of how to indicate this state, I would be really grateful to this person.

[ilias777]

I don't understand what you mean.

In normal Neovim, without noice.nvim and nvim-notify, if you press q, only one time a message appears recordong @{key} at the bottom and that is. After a keysequence and pressing q again the message disappears and you have recorded the macro. There is no other message that you are done with the macro.

Same with noice.nvim and nvim-notify. With the code snippet above, the message appears only once as notify message.

I don't know the integration with lualine. I use feline as my statusline and it shows the recording message there.

Take a look:

Bildschirmaufnahme.2024-06-11.um.21.55.23.mov

I press here qa and the message appears as long I don't press q. If I'm done with my macro, I press q again and the message disappears. So I know the recording is finished. For me is this the best way to know that I am writing a macro.

[yart]

@ilias777 let me explain: when I press q in nvim w/o any plugins, it firstly shows the q letter on the right side of the command line. When I press another letter (to put a register), it removes the q letter from the right side of the command line and shows @<key> recording on the left side of the command line instead.

If I misclicked the q key, I can see this letter q on the right side of the command line, and it indicates me, that nvim (or vim) is ready to record the macro. I can cancel it with ECS or continue to create a macro because I see what is happening right now.

But in case with hidden command line, I can't see this indicator on the right side of the command line, and sometimes it's annoying me.

So this is what I mean.

[ilias777]

Oh, I see. Ok what about this → Send the commands to the mini view like this:

routes = {
  {
    view = 'mini',
    filter = {
      event = 'msg_showcmd'
    }
  }
}

Every time you press q it shows at the bottom right corner in the mini view. With this you can see also the commands like ciw, yiw and so on, same as Neovim without any plugins.

If you want to see only the q, you can use this:

routes = {
  {
    view = 'mini',
    filter = {
      event = 'msg_showcmd'
      any = {
        { find = 'q$' } -- $ to indicate that q is the last letter
      }
    }
  }
}

Try it out. Maybe this is what you want.

[yart]

@ilias777 it almost works. I did the following:

        routes = {
          {
            view = "notify",
            filter = { event = "msg_showmode" },
          },
          {
            view = 'mini',
            filter = {
              event = 'msg_showcmd',
              any = {
                { find = '[mq]$' }
              },
            },
          },

But when I press one of these keys the first time, it doesn't show anything, while I put a register. After that, it shows me both letters. In case with q, it also shows me the letter when I finish a macro recording.

As I told, it looks like nvim pauses any process while waiting for a register letter input. Then it continues work as usual.

Another question: how can I combine events? I want to show notification when I'm stopping a macro recording. Sorry if the question is stupid, but this day was a bit long for me and my brain is tired.

[ilias777]

But when I press one of these keys the first time, it doesn't show anything, while I put a register. After that, it shows me both letters. In case with q, it also shows me the letter when I finish a macro recording.

As I told, it looks like nvim pauses any process while waiting for a register letter input. Then it continues work as usual.

Yes, this is normal behavior. If you press q, Neovim is waiting to press the next letter and then it shows the message recording @{key}.

Another question: how can I combine events? I want to show notification when I'm stopping a macro recording. Sorry if the question is stupid, but this day was a bit long for me and my brain is tired.

No, your question is not stupid. To show a message if you stop a macro, you can use a autocmd, like this:

local macro_group = vim.api.nvim_create_augroup('MacroRecording', { clear = true })
vim.api.nvim_create_autocmd('RecordingLeave', {
    group = macro_group,
    callback = function()
        -- Display a message when macro recording stops
        print('Macro recording stopped')
    end,
})

stop-recording-message.mov

Keep in mind that this auto command don't trigger a third time the RecordingLeave event and I don't know why!

I think that is, right?

[yart]

@ilias777 sorry for the long answer — I was busy. And thank you for the idea, that is!

And I have a similar question, but about numbers for motions in normal mode. When I'm typing, for example, 11j or 317g it doesn't show me the numbers until I press a movement key. Have you an idea how to show the numbers before I pressed any other key?

[ilias777]

To see the numbers before the movement key, it's not possible if you send the msg_showcmd event to the mini view.

I tried LazyVim (because LazyVim uses lualine.nvim and I use feline.nvim) to see how folke has setting up Lualine to display the showcmd and Lualine in this distro has same functionality like msg_showcmd event in the mini view by noice.

The only way to see the numbers first, is when you have cmdheight set to 1. But with noice you can't use cmdheight, because noice automatically set this option to 0. Only if you disable noice you can set cmdheight to 1 and see the numbers first like 11j or 11k.

You can see folkes comment → here

[yart]

This is really sad info… Hmm… Looks like we need to commit something into the nvim repo to bypass zero cmdheight and achieve a result. Ok. Will learn it.

Anyway, I thank you for the information you gave me. It reduces my time to search the info.