This way, you can set your own keymaps instead of NeoComposer doing it for you. You can disable keymaps you don't need.

Example:

require("NeoComposer").setup({
  keymaps = {
    play_macro = false,
    yank_macro = false,
    stop_macro = false,
    toggle_record = false,
  },
})

-- OR
require("NeoComposer").setup({
  keymaps = false
})

Hi,
Actually when you display the status of NeoComposer in Lualine, you can customize the icon foreground and background colors but you can't modify the text colors near the icon.
It would be nice if we could modify them too.

Please see : (Here RecordingSymbol background color is set to none but the text isn't using this color.)

Hello,

When I stop recording macro, it would be convenient to have a possibility to play it straightaway with the "play_macro" action. However, I noticed that the macro list is appended instead of prepended, so the newest macro ends up as the last one in the list. Is there any option to change this behavior?

Hi,

I really like NeoComposer. It reminds me of a plugin I use in normal Vim named Marvim but which hasn't seen much activity lately.

As they basically serve the same purpose (I still haven't tested Marvim in Neovim), I was wondering if you planned on additional some additional features that it supports that I don't see in NeoComposer such as:

• filetype-specific macros
• namespaces to more easily manage macros

Thanks

Attempting to try out the new execute macro in visual mode and get the following error:

Error  08:15:09 AM msg_show.lua_error E5108: Error executing lua vim/_editor.lua:0: bad argument #1 to 'min' (number expected, got nil)
stack traceback:
	[C]: in function 'min'
	vim/_editor.lua: in function 'region'
	...are/nvim/lazy/NeoComposer.nvim/lua/NeoComposer/macro.lua:136: in function 'get_count'
	...are/nvim/lazy/NeoComposer.nvim/lua/NeoComposer/macro.lua:165: in function 'play_macro'
	...are/nvim/lazy/NeoComposer.nvim/lua/NeoComposer/macro.lua:32: in function 'toggle_play_macro'
	[string ":lua"]:1: in main chunk

This happens when using hydra.nvim - the window management hydra from the wiki more specifically. It may be as simple as calling is_closing to ensure it's not already closing before calling close. Happy to contribute a PR if that would be acceptable, just figured I'd create an issue first.

i'm using lazy.nvim for setup and i'm trying to override a single keymap, however, neither lazy.nvim's opts key nor calling neocomposer's setup in a config function seem to achieve it.

in both cases the plugin seems to already be set up and the setup function does an early return.

I'm not sure what could be causing this, but I get the following error semi-frequently:

Error executing vim.schedule lua callback: ...ack/packer/start/NeoComposer.nvim/lua/NeoComposer/ui.lua:137: handle 0x558caffc4660 is already closing
stack traceback:
        [C]: in function 'close'
        ...ack/packer/start/NeoComposer.nvim/lua/NeoComposer/ui.lua:137: in function ''
        vim/_editor.lua: in function <vim/_editor.lua:0>

The error occurs when opening large files sometimes or while editing text and performing operations. My pc is very low spec - I'm not sure if this is valuable info to mention or not. These errors do not occur when actively using features of the plugin, which seems strange to me.

My plugin config:

require('NeoComposer').setup({
  delay_timer = '200',
  keymaps = {
    toggle_record = 'q',
    play_macro    = 'Q',
    stop_macro    = 'cq',
  },
  colors = {
    bg = 'StatusLine'
  }
})

vim.keymap.set('n', '<leader>eq', ':EditMacros<CR>')
vim.keymap.set('n', '<leader>qq', ':ToggleDelay<CR>')

Cool plugin. I am trying it out rn.

I noticed that the lualine was not working and realized that the docs have require('NeoComposer.ui').status_recording() while it should be require('NeoComposer.ui').status_recording

opts = {
  queue_most_recent = true,
}

Makes it so the most recently made macro is queued.