Skip to main content
replaced http://unix.stackexchange.com/ with https://unix.stackexchange.com/
Source Link

Okay, my last answer got forced into a comment as it was too trivial ?! So maybe if I just ramble for a bit, it will confused stack exchange's super advanced AI. Well that was me rambling and this is me providing the answer (fingers crossed) :

http://unix.stackexchange.com/questions/90509/path-not-modified-inside-lxde-on-raspbianhttps://unix.stackexchange.com/questions/90509/path-not-modified-inside-lxde-on-raspbian

Okay, my last answer got forced into a comment as it was too trivial ?! So maybe if I just ramble for a bit, it will confused stack exchange's super advanced AI. Well that was me rambling and this is me providing the answer (fingers crossed) :

http://unix.stackexchange.com/questions/90509/path-not-modified-inside-lxde-on-raspbian

Okay, my last answer got forced into a comment as it was too trivial ?! So maybe if I just ramble for a bit, it will confused stack exchange's super advanced AI. Well that was me rambling and this is me providing the answer (fingers crossed) :

https://unix.stackexchange.com/questions/90509/path-not-modified-inside-lxde-on-raspbian

Source Link

Okay, my last answer got forced into a comment as it was too trivial ?! So maybe if I just ramble for a bit, it will confused stack exchange's super advanced AI. Well that was me rambling and this is me providing the answer (fingers crossed) :

http://unix.stackexchange.com/questions/90509/path-not-modified-inside-lxde-on-raspbian