On Sun, 12 Jan 2014 11:09:02 -0500 mh <[email protected]> said: > Thanks, I appreciate your reply Raster! > On 01/11/2014 08:34 PM, Carsten Haitzler (The Rasterman) wrote: > > On Sat, 11 Jan 2014 16:19:37 -0500 mh <[email protected]> said: > > > >> On 01/11/2014 04:02 PM, Shawn Haworth wrote: > >>> Ahoy! > >>> > >>>> I don't understand. Running e18.2, efl 1.8.4, if I echo $PATH in a > >>>> terminal I get: /opt/e18/bin:/usr/local/bin:/usr/bin:/bin. I have e > >>>> installed in /opt/e18/. > >>>> > >>>> If I logout and then login to xfce, echo $PATH, I get: > >>>> /usr/local/bin:/usr/bin:/bin > >>>> > >>>> I looked in ~/.bashrc but there is nothing there adding /opt/e18/bin to > >>>> PATH. Where is that set? > >>> First off, install the bash-doc package. ie $ sudo apt-get install > >>> bash-doc Which contains: > >>> > >>> Bash_aliases Some useful aliases (Fox). > >>> Bash_profile Sample startup file for bash login shells (Fox). > >>> bash-profile Sample startup file for bash login shells (Ramey). > >>> bashrc Sample Bourne Again SHell init file (Ramey). > >>> Bashrc.bfox Sample Bourne Again SHell init file (Fox). > >>> README README > >>> > >>> apple Example Start-up files for Mac OS X. > >>> apple/aliases Sample aliases for Mac OS X. > >>> apple/bash.defaults Sample User preferences file. > >>> apple/environment Sample Bourne Again Shell environment file. > >>> apple/login Sample login wrapper. > >>> apple/logout Sample logout wrapper. > >>> apple/rc Sample Bourne Again Shell config file. > >>> apple/README README > >>> > >>> I've _attached_ the example bash-profile and bashrc. I suggest you > >>> read docs and learn about bash(1) before you consider using it as your > >>> long term shell. > >>> > >>> Also, remember, in bash(1): ~/.profile: executed by the command > >>> interpreter for login shells. This file is not read by bash(1), if > >>> ~/.bash_profile or ~/.bash_login exists. > >>> > >>> Shawn > >> Thank you. As I said, I have been reading all the bash docs I could > >> find, and I understand that non-interactive login shells use > >> /etc/profile or ~/.profile for environmental variables, and that > >> interactive shells use /etc/bash.bashrc or ~/.bashrc. I also said that I > >> looked at the bashrc files and could not find anything put /opt/e18/bin > >> in my usr PATH. > >> > >> This led to my question about whether or not the e18/bin path was > >> something that was added during the compile process. It seems that this > >> would be useful to do. > > we can't go adding it to your shell during compile. > > > > 1. it may be a non-interactive build on a build server or packaging system. > I compiled and installed from a bash shell with xfce running.
not important to know from you - *IF* some makefile etc. were to have to modify a users shell envrionment to append such paths... how would it tell which sell the user uses - eg to launch e or as their regular interactive shell. yes - i know about $SHELL... but is that the shell they normally use? yes - we can check /etc/passwd and poke around for the shell. but what if the user installing/building is not the user USING it? :) > > 2. shells vary. it may be zsh, bash, dash, tcsh, ksh, ... which one does the > > user actually use? > using bash as above. not for you to answer here. it's a rhetorical question. ask yourself how a build script/makefile has to figure this out and get it RIGHT.. and not mess everything up AND cover all bases... :) think about it. > > 3. how users set up their shell rc files varies a lot - there is no way we > > can sensibly PARSE them to find out where path is set and do this right - > > maybe append at the end, but modifying a usewrs config files during a > > compile of e or efl is so anti-social it's not funny. this will *NEVER* > > happen. if we ever did do it the world would rise up in revolt. > > 4. if you - the user, are unable to fix your own path because you compiled > > e to go into let's say /opt/e18 - well sorry. that's your problem. :( it's > > your job to integraye to your system based on where you put it. we can't do > > that. now imagine we change your user files... what about other users? we > > miss them too. then we have to start editing system shell files as above. > > that's just ASKING to destroy a persons system. > Absolutely. It looked like my problem here, and I spent quite some time > searching and reading to try and understand what was happening. I > checked the system wide and local bashrc setting and couldn't see where > PATH was being appended. I noticed that PATH wasn't appended when I ran > xfce. It seemed like a clue, but one I couldn't understand. I looked for > help here. I think your comment about enlightenment_start below may be > the answer. > > When I compile/install the release tarballs, I use ./configure > --prefix=/opt/e18. > > it's not a useful thing to do. it's probably the worst idea ever. :) no one > > does this - ever. there are good reasons, and probably more than i listed > > above by a vast margin... but the above is enough to just begin to give a > > taste for it. > It sounded like a bad idea to me. > > > > if you want to modify your path put: > > > > export PATH=dir1:dir2:dir3... > > > > in your .bashrc. you can source your .profile from your .bashrc too: > > > > . ~/.profile > > > > yes the . command reads in another file and "runs it" (sources it). > > > > you could modify the system profile if you want: > > > > /etc/profile > > /etc/bashrc > Thanks for that. > > > > i personally use zsh - it's my favorite interactive shell. > > > > as for what adds e's install path to PATH - enlightenment_start does. and > > enlightenment_start is the babysitter for enlightenment - enlightenment > > inherits it.. and anything enlightenment launches also inherits it, unless > > it resets it. > So this is the answer to my question. When I start e by calling > enlightenment_start, e adds (in my case) /opt/e18/bin to my PATH. That's > what I was trying to ask, not very clearly I guess. I couldn't see how > the PATH was changed in any of the bashrc files and just wanted to > understand how/where the PATH was being modified. > > Thanks!! > > mike > > > > >> Can you shed any light on this, or just provide shell recommendations? > >> > >> mike > >> > >> > >> ------------------------------------------------------------------------------ > >> CenturyLink Cloud: The Leader in Enterprise Cloud Services. > >> Learn Why More Businesses Are Choosing CenturyLink Cloud For > >> Critical Workloads, Development Environments & Everything In Between. > >> Get a Quote or Start a Free Trial Today. > >> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > >> _______________________________________________ > >> enlightenment-users mailing list > >> [email protected] > >> https://lists.sourceforge.net/lists/listinfo/enlightenment-users > >> > > > > > ------------------------------------------------------------------------------ > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > Learn Why More Businesses Are Choosing CenturyLink Cloud For > Critical Workloads, Development Environments & Everything In Between. > Get a Quote or Start a Free Trial Today. > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > _______________________________________________ > enlightenment-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-users > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
