...Not being am emelfm user please provide specifics.
Under 3.8rc3, the PATH as reported by emelfm2 is:
But, under 3.8rc2, the PATH as reported by emelfm2 is:
I have configured a pair of buttons on the central toolbar of emelfm2, each of which calls a script that is located in ~/.local/bin/
Since /.local/bin/ is added to the PATH by ~/.profile, it was not necessary to configure the buttons with the full path to the scripts because the application, emelfm2, used a PATH inherited (possibly indirectly) form the login shell.
With 3.8rc3, the buttons no longer work. They do work in 3.8rc2. A little investigation revealed the PATH listings shown above, which were generated from within emelfm2 under 3.8rc2 and 3.8rc3.
While it would be relatively simple to reconfigure the buttons to use full paths to the scripts they invoke, I worry that this or other environment settings required by this or other applications might cause problems if not set.
I'm supposing that the Xserver gets its initial environment from the login shell and the application gets its initial environment from the Xserver. Since my working environment is the same other than the rc level of tinycore.gz, I'm wondering what change in tinycore.gz might have caused the observed behavior.