From: Ingo Schwarze <schwarze@usta.de>
To: tech@mdocml.bsd.lv
Subject: Re: post-p2k11 resync
Date: Sun, 27 Nov 2011 01:57:28 +0100 [thread overview]
Message-ID: <20111127005728.GA20233@iris.usta.de> (raw)
In-Reply-To: <4ED12F7E.2010207@bsd.lv>
Hi Kristaps,
Kristaps Dzonsons wrote on Sat, Nov 26, 2011 at 07:27:10PM +0100:
> On 26/11/2011 17:57, Ingo Schwarze wrote:
>> the OpenBSD part of the resync is done (well, there are still a few
>> minor patches outside the mandocsb/apropos area, i'll resend those
>> later).
>>
>> Here is the bsd.lv part, mostly removing trivial differences and
>> cleaning up whitespace. But there are a few real issues:
>>
>> * -M overrides MANPATH, not the other way round;
>> -m _prepends_ to the path, it doesn't _append_.
>> That was both implemented and documented the wrong way.
[...]
> Great---ok kristaps!
Thanks, done.
> As you can see, I tried to shove all of the
> MANPATH handling into manpath_parse(), which should set everything
> up from MANPATH, -m, -M, and man.conf/manpath(1)
Yes, i like that approach.
> (which, yes, is extremely ugly).
Sure, but maybe you are right that the portable version on
bsd.lv needs it; i didn't merge the #ifdef's to OpenBSD, though.
We are not getting manpath(1) anytime soon. ;-)
[...]
> Incidentally, I still think there's a case for MANPATH acting like
> -m as mentioned before. How else does one maintain a private manual
> tree? Using "-m" each time man(1) is invoked is ugly.
Well, i see your point there, though i'm not sure how important
it is. If we think that we need this kind of functionality, we
might consider implementing the following approach found
in Linux manpath(1):
MANPATH
If $MANPATH is set, manpath displays its value rather than
determining it on the fly. If $MANPATH is prefixed by a colon,
then the value of the variable is appended to the list deter-
mined from the content of the configuration files. If the colon
comes at the end of the value in the variable, then the deter-
mined list is appended to the content of the variable. If the
value of the variable contains a double colon (::), then the
determined list is inserted in the middle of the value, between
the two colons.
But i'd at least recommend to wait some time until the dust has
settled, basic functionality is working and integrated and consider
fancy new features after that.
Until then, for people desperately needing this, a simple
alias man='man -m "/my/very/private/manpath"'
might do the trick.
Yours,
Ingo
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2011-11-27 0:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-26 16:57 Ingo Schwarze
2011-11-26 18:27 ` Kristaps Dzonsons
2011-11-27 0:57 ` Ingo Schwarze [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111127005728.GA20233@iris.usta.de \
--to=schwarze@usta.de \
--cc=tech@mdocml.bsd.lv \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).