2017-10-13 22:25 GMT+09:00 LCD 47 <[email protected]>:
> On 13 October 2017, Kazunobu Kuriyama <[email protected]>
> wrote:
> > 2017-10-13 21:04 GMT+09:00 LCD 47 <[email protected]>:
> >
> > > On 13 October 2017, Kazunobu Kuriyama <[email protected]>
> > > wrote:
> > > > HI,
> > > >
> > > > To get your patch to work for macOS, I needed to add some tweaks
> > > > to that. Please find the attached patch and consider merging it
> > > > into yours. Of course, it's fine to me that you reject or modify
> > > > it freely; I leave that to you.
> > > >
> > > > More precisely, contrary to the description it claims (:h
> > > > manpager), I haven't been able to get manpager.vim to work for
> > > > macOS since it was introduced. As Bram asked for confirmation if
> > > > your patch worked for other platforms, I looked into the issue and
> > > > found a way to have it work properly for the OS.
> > > >
> > > > Hopefully, with your patch, the issue is all fixed for the BSD
> > > > clan.
> > >
> > > Sorry, my patch only fixes how manpager.vim works on systems
> > > that set $MAN_PN, i.e. _some_ Linuxes.
> > >
> >
> > Did you mean you didn't want to go further beyond those Linuxes? Oh
> > my...I thought Bram's word "various systems" meant systems other than
> > Linux.
>
> I don't think the MANPAGER way can be salvaged without MAN_PN (i.e.
> the problem of "man Xorg" and "man Net::DNS" can't be solved reasonably
> without it). That's why my patch only addresses the case where "man"
> sets $MAN_PN. That only covers some Linux systems. On other systems
> I suggest using a wrapper script instead, that tries to syntesize a
> $MAN_PN before running "man".
>
I didn't try addressing the issue for systems not having MAN_PN.
But, according to :h manpager, it clams that it works for macOS with
export MANPAGER="env MAN_PN=1 vim -M +MANPAGER -"
Since macOS doesn't has MAN_PN, I have no idea as to what it is and what it
is for, and I hadn't known about the mentioned wrapper script solution
until you told me. True, macOS doesn't have MAN_PN, but the help asks to
set it to 1, and I'm following the instructions...
>
> I tried to explain all this in the previous messages. But I suppose
> nobody can really decrypt what I'm trying to say. :)
>
> > OK, if you don't like my patch, it's also fine to me that I send it
> > here again separately, though I'm still wondering if we should go
> > separately.
> [...]
>
> It isn't that I don't _like_ it. Your patch changes the non-MAN_PN
> branch, it's unrelated to mine. As I said, I'm suggesting the wrapper
> script as a possibly better solution for that ("better" as in, it solves
> the "man Xorg" and "man Net::DNS" problem I described in my first
> message).
>
No, my patch actually changes the MAN_PN branch ("if MAN_PN is 1"), and now
I can use Vim as a stand-alone man pager which can work nicely with both
"man Xorg" and "man Net::DNS", which I think shares the same goal of your
patch.
> /lcd
>
Kazunobu
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
