So, this thread Use `/etc/paths` or `/etc/paths.d` to add items to the PATH in macOS Sierra? discusses /etc/paths and /etc/paths.d briefly in connection with macOS (ne OS X 12, sierra) /usr/libexec/path_helper, which helpfully puts /usr/bin:/bin:/usr/sbin:/sbin (the contents of /etc/paths, one per line) at the start of your PATH.I understand the intent (along with the intent behind SIP), but what if one actually does know what one is doing and actually does want to have executables in one's own ~/bin (for example) that supercede the executable with the same name that Apple, in its unlimited beneficence, has modified or limited in one of its many unhelpful ways.  Or, perhaps, wants /opt/... versions to be found before Apple's defaults.  (If one wants to run a windowed version of emacs, for example.)I'm willing to use this mechanism.  My understanding is that I will need to disable SIP before I can modify /etc/paths.d/ but does anyone know if it is possible to put a file (00LookHereFirst, say) in /etc/paths.d/ that will prepend even those in /etc/paths?  (OW, of course, modify /etc/paths.  But I am trying to play nice.  And, of course, it will be trashed if I ever let them harass me into downgrading to a newer release.) Answers of the form If you want to be treated like a grown-up stick to BSD would not be considered helpful.(Sorry for the tags.  They're as close as I can come with my limited powers.)
macOS /etc/paths.d
osx;path;init script