On Oct 3, 2010, at 2:52 PM, Amit Kulkarni wrote: > Then why is it placed there in the FAQ entry? Somebody thought there's a > relation there.
It's there because when you start an X terminal (xterm), you can tell xterm (via X resource DB) if you want shells it starts to be "login shells", and that's what that resource setting is doing. It is not a resource setting for ksh. Further, it's in the FAQ about "why isn't my .profile being read" for the ksh because most people are completely unaware of what is going on when they click that "Terminal" button. .Xdefaults may or may not be read by X-based applications, and is often loaded into the Resource DB of the X server on login (depending on the system -- everything does it differently). At one point is was .Xresources (which may be what X reads still -- I don't know anymore, I stopped thinking about xrdb about 8 years ago). The space is completely irrelevant, and this thread should die. > IMHO, I think ksh should be able to read .profile by default The rules of what ksh reads and when are based on ancient login mechanisms -- .profile was read only on login. In the csh, .login was read on login, and .cshrc was read on every invocation of csh. ksh reads the file pointed to by the environment variable ENV on invocation. Put things you want to happen when you log in (via SSH, for example) into .profile, and also set ENV=$HOME/.kshrc into it. Then put everything into .kshrc that you want to invoke with all subshells. It's no good to say "I think ksh should do. . ." because it ain't gonna happen. It would break all sorts of crap if it did. Sean PS Linux's pdksh sucks, and does all sorts of weird shit. OpenBSD's ksh is much more sane. > On Sat, Oct 2, 2010 at 10:39 PM, Abel Abraham Camarillo Ojeda < > acam...@verlet.org> wrote: > >> .Xdefaults has nothing to do with .profile ...
