cppman vim/nvim pager incompatible with vim plugin bogado/file-line
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.4k
- Forks
- 89
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I just noticed that when using cppman with vim/nvim as pager
and when using https://github.com/bogado/file-line as a plugin (it opens a file on a line if the filename is formatted as /file/name.ext:<line_nr>)
then the resulting vim/nvim buffer is empty.
I tend to use https://github.com/gauteh/vim-cppman which doesn't have an issue with this.
Just to let you know, maybe there is an easy workaround or something.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing cppman with vim/nvim configured as the pager and the bogado/file-line plugin enabled. Compare the resulting empty buffer with the behavior of gauteh/vim-cppman; done means the cppman output opens as visible manual-page content without breaking file-line.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- neovim, python, vim
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100