Currently we can only choose every filetype or some manually defined set of filetypes. I think more commonly we would want [every filetype - a manually defined set of exclusions]

Currently the highlight included the same symbol in strings, which doesn't make sense to me. For example, the "vim" in the string "shiracamus/vim-syntax-x86-objdump-d" is not a lua symbol and should not have been highlighted. I believe treesitter is capable of avoiding this.

Love the idea!

I have placed the following in my _vimrc:

        'tzachar/local-highlight.nvim',
        config = function()
          require('local-highlight').setup({
              file_types = {'python'},
              hlgroup = 'TSDefinitionUsage',
          })
        end
    },

(I didn't copy the separate setup code from your README as it seems to duplicate the above).

Still nothing happens in my python file. I tried to verify activation by manually typing :LocalHighlightOn but still nothing happens. (BTW, all LocalHighlight* commands do not prompt the current status, might be helpful to add).

Anything that might indicate what the problem is? Or did I get something wrong in the install/use?

Thanks!

I've installed the plugin with the given example using Lazy.
Upon starting neovim the following error appears:

Failed to run `config` for local-highlight.nvim
...e/nvim/lazy/local-highlight.nvim/lua/local-highlight.lua:224: attempt to index local 'config' (a nil value)

The plugin doesn't work on the first buffer I open, I have to switch to another buffer then the plugin will work.

For example:

1. Open nvim ./general (Doesn't highlight but I can use LocalHighlightToggle to enable)
2. Switch to any other buffer (Highlight now activated)

return {
    {
        "tzachar/local-highlight.nvim",
        event = "VeryLazy",
        config = function()
            require("local-highlight").setup({
                file_types = nil,
                disable_file_types = nil,
                hlgroup = "Error",
                cw_hlgroup = "Error",
            })
        end,
    },
}

Pretty self explanatory. I can start a pull request if you want. So far as a work around, I created a autocmd and call the preexisting clear function so it should be pretty easy to implement. You can set a boolean in the setup function.

vim.api.nvim_create_autocmd({ 'CursorMoved', 'CursorMovedI' }, {
	buffer = event.buf,
	callback = function()
		require('local-highlight').clear_usage_highlights(event.buf)
	end,
})

Any idea why I'm seeing a 4 second highlight delay? I checked the source to see if I could find a config for the delay for debounce, etc, but I didn't see anything. It also takes 4 seconds to de-highlight. I'm 99% sure this delay is synthetic, but I can't find the source. I commented all of my Lazy packages except yours (mason also commented, so no lsps running). Still 4 second delay.

• WSL on windows (vmmem 100%-CPU bug not in action). Everything else "snappy".
• Editing my small init.lua file. 277 lines.
• nvim 0.9.2
• Tmux if that matters

    {
        'tzachar/local-highlight.nvim',
        config = function()
            require('local-highlight').setup({
                file_types = {'python', 'cpp', 'lua'}, -- If this is given only attach to this
                -- OR attach to every filetype except:
                disable_file_types = {'tex'},
                hlgroup = 'Search',
                cw_hlgroup = nil,
                -- Whether to display highlights in INSERT mode or not
                insert_mode = false
            })
        end
    }

:LocalHighlightStat
Total Usage Count : 2
Average Running Time : 0.210606 msec

tzachar/local-highlight.nvim
neovim/nvim-lspconfig
lukas-reineke/indent-blankline.nvim
nvim-treesitter/nvim-treesitte
hrsh7th/nvim-cm
numToStr/Comment.nvim
nvim-telescope/telescope.nvi

Thanks!

Just a suggestion here:

• if file_types is not provided, the plugin can work for all file types
• if file_types is provided explicitly, the plugin works for only those file types

This uses a blue highlight color instead of the default one. Can this be changed to be the default highlight color or any other?

I'm using the default configuration. When i highlight travelers in the commented line the matches does not get highlighted, only if i uncomment the line.

Actual behavior

Expected to work in commented line

Hi, thanks for your effort,
Right now there is no way to prevent highlighting in cases when there is only 1 occurrence.
Minimum number of occurrences to highlight would be a nice to have feature.

Hi,
I couldnt find a solution for this yet: How can I start neovim with this plugin loaded but disabled?
If I want to use it, I would like to execute the user command "LocalHighlightToggle" explicitly.

I tried it via
config = function() require('local-highlight').setup({ default = false, })

but it did not work.
I'm not sure if I miss something obvious here.

Hi, I wanted to test this freshly merged feature: #22 (thank you @tzachar for merging)

So I updated local-highlight.nvim to the current master branch.

However, I have no changed behavior than before. When same words occur multiple times in the buffer, only the OTHER words are highlighted, not the one which my cursor is at.

This is my local-highlight.nvim config:

return {
  'tzachar/local-highlight.nvim',
  config = function()
    require('local-highlight').setup({
      file_types = {'xyz'},
      highlight_single_match = true
    })

    vim.keymap.set('n', '<leader>ph', vim.cmd.LocalHighlightToggle, { expr = false, silent = true, desc = "Toggle local-highlight.nvim"})
  end,
}

The red rectangle shows the current behaviour.

Do you have any suggestions for me?
Regards

Hi, by default config M.config.file_types has been set to {}

by checking for nil value of this line

i can solve it by changing this line to next(M.config.file_types) == nil

Edit: Created PR #15

First of all, thanks for this plugin.

These are some options it would be great to add because it seems that as of now, there are no other plugins offering these features:

• Enable word highlight in all buffers (e.g. quickfix), not just certain file types.

• Customize highlight colour for the current word.

• Define custom keywords to always highlight, with highlight groups. For example:

{
  keywords = {
    { "TODO",  "Todo" },
    { "ERROR", "Error" },
    { "FIXME", "Error" },
    { "NOTE",  "Comment" },
  },
}

and custom highlight groups, for example:

{
  highlight = {
    Todo    = { gui = "bold,italic", guifg = "Red" },
    Error   = { gui = "bold,italic", guifg = "Orange" },
    Comment = { gui = "bold,italic", guifg = "Grey" },
  },
}

also, it would be great to let the user define the custom keywords as regex patterns if needed.

After installing the plugin, I found that here:

it is defined a highlight which is not existent in my setup, thus the plugin doesn't highlight any word.

I wonder where that highlight comes from, also it would be great to let the user configure the highlight by choosing something different (or by manually defining a new one with background, foreground, style etc.).