songbird (12024-07-10): > but for my own purposes i also like to do things for > terminals when they open up (my session manager and the > overall desktop will store multiple desktops and all of > the terminals i have open in each of them when i ask it > to).
This is absolutely legitimate. Note that tings in .bashrc will not affect terminals that run directly another program, like “xterm -e vim”. > then in my .bashrc file i check to see what directory > the terminal opens in and create aliases and other things > for the specific project that i've got in that directory. > it's very nice to have just the aliases and environment > variables and other commands all set up and ready to go. This too is absolutely fine. I have even seen done this in pre-prompt functions to have it exec when changing directory in the same shell. > it's not a hack This is not the hack. The hack comes when (1) you put things to initialize the extended environment in .bashrc, (2) you source .bashrc when it is not sourced. All because this idiot bash does not have a .bashenv. Regards, -- Nicolas George
