Re: openin_any removal for TL'26?

Hi Nicola,

    Does this mean that `kpsewhich --var-value=openin_any` will treat 
    `openin_any` as undefined for TL'26?

Thanks for the heads-up. I'm planning to leave openin_any in texmf.cnf,
defined as a, for exactly that reason.

I'm also thinking to have the code give a warning if it sees any value
besides a, since that would imply the user thinks they specified the
reading restriction, but there is no such restriction now.

My theory is that there are zero such users (apart from testing),
otherwise I would be taking a different tack. Do you know of anyone
using openin_any != a?

The code itself (the in_name_ok functions) will always return true,
regardless of the setting. I don't plan to (ever) remove the functions,
to avoid gratuitous linking problems.

Thanks Nicola. -k