Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!cbmvax!grr From: grr@cbmvax.UUCP (George Robbins) Newsgroups: comp.unix.ultrix Subject: Re: Bug in /bin/csh: echo "`date`" in script Keywords: Ultrix 3.0 csh bug Message-ID: <7285@cbmvax.UUCP> Date: 12 Jul 89 19:31:02 GMT References: <49802@csvax1.cs.tcd.ie> Reply-To: grr@cbmvax.UUCP (George Robbins) Organization: Commodore Technology, West Chester, PA Lines: 29 In article <49802@csvax1.cs.tcd.ie> Eamonn McManus writes: > There is a bug in the Ultrix 3.0 csh which was not present in Ultrix 2.2. > I would guess that support for 8-bit characters is the reason for the change. > > #!/bin/csh > echo "`date`" > causes character 0xFF to be output before each character of the date. There are quite a few places where 8-bit characters vs. traditional internal "quoting" mechanisms or their replacements read threir ugly head. The workaround for this one is supposedly to install /usr/new/csh (aka tcsh) as /bin/csh. Supposedly tcsh doesn't have this bug and is otherwise reasonably compatible. You also get an inactivity logout, which can be irritating unless you put 'unset autologout' in your .login file. Other places with 8-bit screw-ups: When csh types out "job names" with the jobs command, fg, bg and when a task terminates. When you use one of the filename substitition metachacters in a shell escape from vi/ex. Example: :!pr % will get 'pr: can't open xyz' even though xyz already exists. -- George Robbins - now working for, uucp: {uunet|pyramid|rutgers}!cbmvax!grr but no way officially representing arpa: cbmvax!grr@uunet.uu.net Commodore, Engineering Department fone: 215-431-9255 (only by moonlite)