This is mostly useful for the gui since :!man in the builtin terminal is unusable. Maybe it should be done only when the gui is running? Although I think also terminal users would prefer the man.vim plugin
I also added an option to man to only search in relevant sections, for example man -s2,3 open opens the man page for the syscall instead of the user program with the same name.
https://github.com/vim/vim/pull/19222
(1 file)
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
I don't think this makes sense. You can already use <count>K on any function to open the manpage for the identifier under the cursor (in section <count>) it. This sounds more like something for user configuration, but I don't think we should add this by default.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Even if it was considered for inclusion, sourcing man.vim every time c filetype is detected is wrong.
I agree, this should be user configuration.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
I agree with both of you, I didn't think this through.
But K is still not usable in gui, maybe a solution is sourcing man.vim somewhere else and add an autocmd in c.vim?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
I opted for another approach using :term but only for the gui. I added ++close because closing the terminal window after exiting the pager was annoying, the downside is that in case of an error nothing is shown.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
@mateoxh pushed 1 commit.
—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
We already have this sort of behaviour implemented in some other ftplugins. E.g.,
The approach should probably be generalised.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Yes, same thing for go
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()