############################################################################# ### ### By default, the desktop will read your standard $HOME/.profile ### or $HOME/.login files. This can be changed commenting out the ### DTSOURCEPROFILE variable assignment at the end of this file. The ### desktop reads .profile if your $SHELL is "sh" or "ksh", or .login ### if your $SHELL is "csh". ### ### The desktop reads the .dtprofile and .profile/.login with a simulated ### terminal via the sdt_shell program. The sdt_shell program will create ### a controlling terminal. Shell output will be logged to the location ### $HOME/.dt/startlog. Any shell requested input will receive an end ### of file character (Control-D). ### ### This being the case .profile/.login should avoid requiring interaction ### with the user at login time. Any messages printed in these scripts will ### not be seen when you log in and any prompts such as by the "read" ### command will return an end-of-file to the calling script. ### ### With minor editing, it is possible to adapt your .profile or .login ### for use both with and without the desktop. Group user interaction ### statements not appropriate for your desktop session into one section ### and enclose them with an "if" statement that checks for absence of ### of the "DT" environment variable. When the desktop reads your .profile ### or .login file, it will set "DT" to a non-empty value for which your ### .profile or .login can test. ### ### example for sh/ksh ### ### if [ ! "$DT" ]; then ### # ### # commands and environment variables not appropriate for desktop ### # ### echo "Please enter some data:" ### read data ### ... ### fi