Tiny Core Base > Release Candidate Testing

tinycore_v3.8rc3

<< < (7/7)

roberts:
To answer my own question:
--- Quote ---Not being am emelfm user please provide specifics.

--- End quote ---
There is a run command input area at lower right bottom of emelfm2.
Typing echo $PATH displays the PATH issue that Lee is experiencing and can be reproduced.

Lee:
Hi Curaga,

In either 3.8rc2 or 3.8rc3, at a shell prompt, I get the expected PATH:

/home/tc/.local/bin
/usr/local/bin
/usr/local/sbin
/usr/sbin
/usr/bin
/sbin
/bin

Its only in emelfm2 that I see the difference.  I don't see any config files getting created at extension load time, but shouldn't they be the same anyhow?

--- a little time passes, during which I do some testing and roberts does also ---

I'm not a rox-filer user but I was able to verify that this issue affects rox-filer as well.  I also determined that if I close down X completely (exit to prompt)  and restart it, the symptoms disappear.

roberts:
I have a fix. I was attempting a temporary PATH for the coreutils and util-linux-ng issues. I will use an alternate method. Now that I know how to use emelfm2 to test. I can verify all three cases for the next cut.

Navigation

[0] Message Index

[*] Previous page