Re: info: can we add a way to get the default path?
Karl Berry <karl@cs.umb.edu> writes:
> I suggest we adopt your solution #2 in this form: make a leading or
> trailing or doubled colon expand into the default path. That's what I
> did for tex/web2c/kpathsea many years ago and I haven't had any
> complaints about it.
Sounds OK, though it does mean you have to be careful about variables
that expand to "". For example, if you say INFOPATH=${FOO}:/usr/info,
and if $FOO is for some reason unbound, then you get the default path
expanded there rather than no path. I suppose if you haven't had and
complaints, it's probably not a common failure mode, but if you
requred some special token rather than treating colons specially, this
couldn't happen.
> If you do the work, great. (I'll need you to sign a disclaimer.) I
> won't be able to get to this until after the release, whenever that
> is :(.
You mean the FSF copyright assignment? I'd love to :>
--
Rob Browning <rlb@cs.utexas.edu> PGP=E80E0D04F521A094 532B97F5D64E3930
Reply to: