Yes, that is correct. In pre-jaguar, the tcsh example scripts automatically ran when a new terminal was started. Also, in Jaguar, there is a bug in one of the example scripts, that forces the initialization to interrupt. By fixing the bug, and putting the following command in the .tcshrc-file in the user's home folder, the original functionality can be restored: source /usr/share/tcsh/examples/rc The bug that needs fixing, is in this file: /usr/share/tcsh/examples/aliases Change this line: if ("$TERM_PROGRAM" == "Apple_Terminal") then to: if ("$?TERM_PROGRAM" == Apple_Terminal") then That should avoid any errors when launching new terminals using other terminal programs than Terminal.app (xterm, iTerm, ssh, telnet, etc). / Sincerely, David Remahl On Monday, May 19, 2003, at 07:12 PM, Sam Hotchkiss wrote: > On Mon, 19 May 2003 8:42AM -0700, Jesse Brown wrote: >> >> I'm sorry Sam, thanks for the clarification. I've worked on numerous >> Unix >> systems and have never seen any documentation where "ls -l" ( list >> contents >> in long format) referred to as ll. >> >> In BSD (OS X) "ll" does not work from the command line, so I'm at a >> loss as >> to why it was used to illustrate this example. > > If I remember correctly, both "l" and "ll" worked the same as "ls -l" > on 10.1, but not in 10.2 > -- > Sam Hotchkiss > s at swh.cn > This message was sent wirelessly from a T-Mobile SideKick