feat: allow disabling the plugin dynamically#34
Open
SVendittelli wants to merge 2 commits into
Open
Conversation
Enable disabling the plugin either globally, or locally for a buffer by setting an option.
It wasn't picking up the buffer previously.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sometimes when screen sharing, I always want to show line number not relative, but the auto-commands clobber that. This lets me dynamically disable them either globally or just for one buffer. This gives the added advantage of being able to have this plugin only be enabled for some file types via an
ftpluginif desired.I use
vim.g.numbertoggle_disablefor globally disabling andvim.b.numbertoggle_disablefor disabling in only a given buffer.I found these features useful locally so I thought I'd upstream them!