allow not clearing mark when it re-added about vim-mark HOT 2 CLOSED

The plugin assumes direct use, so a user wouldn't add a pattern again that's already highlighted, and so it instead interprets such as the desire to un-highlight it. This toggling behavior is quite deeply embedded in the plugin's implementation, as you've already found out :-)

I understand that in your integration use case, the toggling is not desirable; as in your mapping, the highlighting is more a side effect, whereas the Fugitive grep is the main action.

I think a separate plugin function that allows you to query whether a pattern / literal text is already highlighted offers even more flexibility than adding alternative functions that do not toggle. In your proposed implementation, you would have to replace the :Mark invocation with calling the new mark#DoMarkAndSetCurrentDontClear() function, whereas with a separate query function, you would call that first and only on a negative result invoke :Mark (a positive result means that the mark already exists).

I've added mark#GetMarkNumber() to the code.

With it, your mapping would look like this:

nnoremap gr :let @/=""<CR>:if !mark#GetMarkNumber(expand('<cword>'), 1, 0)<Bar>execute 'Mark' expand('<cword>')<Bar>endif<CR>:silent exec ":Ggrep! -w <C-R><C-W>"<CR>:copen<CR>:redr!<CR>

I hope that addresses your problem; let me know that you think!

from vim-mark.

Hi @inkarkat Your patch with new plugin function mark#GetMarkNumber() is a perfect solution for my case! Thanks a lot for such a quick and helpful reply!

Also big thanks for such a useful plugin!

Closing as done.

from vim-mark.