Timeline for Using vim as manpager: works on Linux, fails on macOS
Current License: CC BY-SA 3.0
22 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jul 21, 2022 at 20:54 | history | suggested | chicks |
add manpages tag
|
|
| Jul 21, 2022 at 19:33 | review | Suggested edits | |||
| S Jul 21, 2022 at 20:54 | |||||
| S Jan 6, 2018 at 19:25 | history | bounty ended | J. Chomel | ||
| S Jan 6, 2018 at 19:25 | history | notice removed | J. Chomel | ||
| Jan 6, 2018 at 8:58 | vote | accept | Ryan Lue | ||
| Jan 6, 2018 at 8:58 | answer | added | Ryan Lue | timeline score: 2 | |
| Jan 6, 2018 at 8:57 | history | edited | Ryan Lue | CC BY-SA 3.0 |
deleted 203 characters in body
|
| Jan 5, 2018 at 13:17 | comment | added | J. Chomel | Once you've found enough material, you should answer your own question, at least for part one. | |
| Jan 4, 2018 at 14:01 | history | edited | Ryan Lue | CC BY-SA 3.0 |
added 203 characters in body
|
| S Jan 2, 2018 at 7:03 | history | bounty started | J. Chomel | ||
| S Jan 2, 2018 at 7:03 | history | notice added | J. Chomel | Draw attention | |
| Jan 2, 2018 at 2:58 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Dec 3, 2017 at 2:48 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Nov 3, 2017 at 2:19 | history | edited | Ryan Lue | CC BY-SA 3.0 |
added 525 characters in body
|
| Nov 3, 2017 at 1:50 | comment | added | Ryan Lue |
Thanks for helping me take the next step, @ChristianBrabandt. The first line of a manpage is actually blank on a Mac (or at least on my machine); the second is the one that contains the manpage name. Changing it to getline(nextnonblank(1)) made it work. I'll shoot out an email to the maintainer now. (Unfortunately, I'm still getting the same error as above when trying to navigate with <C-]>...)
|
|
| Nov 2, 2017 at 19:36 | comment | added | Christian Brabandt | what does the first line look like? BTW: You should report that to the plugin maintainer (or if he is unresponsive to vim-dev) | |
| Nov 2, 2017 at 17:59 | answer | added | phildobbin | timeline score: -1 | |
| Nov 2, 2017 at 11:00 | comment | added | Martin Tournoij | I think the format of the manpages might be different on macOS? I don't have a mac machine myself, so unfortunately I can't test it. | |
| Nov 2, 2017 at 10:51 | comment | added | Ryan Lue |
There's a line in the s:MANPAGER() function that looks like this: let manpage = matchstr( getline(1), '^' . pagesec_pattern ). getline(1) is returning an empty string, which I think is what's causing the problem. Beyond that, I don't really know how to diagnose it. Any chance you could point me in the right direction?
|
|
| Nov 1, 2017 at 11:07 | comment | added | Martin Tournoij |
Is this a bug -> Possibly? The code that errors out is in $VIMRUNTIME/plugin/manpager.vim. It's not very long or complicated. Adding some strategic echos might help debug the problem.
|
|
| Nov 1, 2017 at 2:17 | history | edited | Ryan Lue | CC BY-SA 3.0 |
added 182 characters in body
|
| Oct 31, 2017 at 14:16 | history | asked | Ryan Lue | CC BY-SA 3.0 |