Yes, in *NIX land. However, I should be able to write to the registry and have subsequent shells pick up my changes. And it ALMOST works. If I write directly to the PATH, no issues. If I write the PERL_PATH variable and stick it into the PATH, then subsequent shells do NOT expand PERL_PATH in PATH. If, however, all I do is fire up the Environment Variable dialog, see that all my changes are there and then click OK (no editing, no updates), the NEXT command box has the expansion properly done. That leads me to believe that there's some other 'bit' that has to be flipped. I'll have to test by looking at the registry directly which I cannot do on the current box. More to follow.

In reply to Re^2: windows environment variable regression by mpersico
in thread windows environment variable regression by mpersico

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.