Nicolas George wrote: > Greg Wooledge (12024-07-10): >> There are many legitimate or semi-legitimate situations where a .bashrc >> file might be read by a shell that's not running inside a terminal. >> >> One of them is if someone chooses to dot in ~/.profile from their >> ~/.xsession file, or something analogous to it. Or perhaps their >> operating system does this automatically in certain kinds of login. >> >> Another might be a scripted ssh session being run from cron, or some >> other parent that's not in a terminal. Analogously, the ancient >> predecessors of ssh (rsh, rexec) had exactly the same issues. > > What you describe is not legitimate, even semi-, these are hacks by > people who cannot be bothered to organize their configuration properly.
i see no problem with that at all. 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). 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. it's not a hack, it's a way of being efficient and working the way that suits me. it also helps eliminate some problems because i can also set my various PATH environment variables to just what is needed and not any thing more. ... songbird
