Re: /bin/sh startup file processing

[Robert Elz <kre%munnari.OZ.AU@localhost>]

    Date:        Thu, 13 Dec 2018 18:36:35 +0100
    From:        Edgar =?iso-8859-1?B?RnXf?= <ef%math.uni-bonn.de@localhost>
    Message-ID:  <20181213173634.GE46682%trav.math.uni-bonn.de@localhost>

  | > unless /etc/profile changes it, $HOME (for .profile)
  | So, would it make sense to treat relative paths as relative to $HOME, then?
  | That way, you don't break existing setups where that was intended.

For .profile, yes, that's exactly what I would do (if anything happens at all).
For $ENV it isn't that simple, as arbitrary shells start in arbitrary 
directories, the only current use for the (posix "is undefined") relative
path in $ENV is if the intent is to run the script  relative to whatever 
directory the shell happens to start in.    I doubt that is often intended.

kre