Closed mox-mox closed 6 years ago
Have you tried:
let g:less = { 'enabled': 0 }
Ok, I tried to, but #221 has more or less prevented any experimentation. I'll try if I can cook up a solution for this, then I'll try again.
Are you sure that is the right issue? I fixed that in master.
Well, I got the same error messages. But after a fresh pull, the problem was gone.
let g:less = { 'enabled': 0 }
Works nicely. And I feel stupid. After writing my comment I found the same command in the readme. Sorry for wasting your time on that question.
Hi,
is there some simple way of having vimpager not map or unmap any key bindings? And to not have the nomodifiable status set? I would like to have all the cool features (links in man pages, proper highlighting, etc) but also keep my normal bindings, cursorline, customized statusline, plugins, etc*..
Some years ago, I set up my vimpager and eventually commented out all the bindings and I loved it**. Now, when I switched to neovim, I tried to modify a recent version of vimpager, but I it really has grown in all the time and I can't seem to get this right/running.
*Yes, I know that I'm trying to have my cake and eat it.
**Please don't get this wrong, I really appreciate all the effort to make vimpager, and this is not meant to be disrespectful. It is just that I am looking for a way to integrate this great plugin into my own workflow which is a bit different.