From owner-freebsd-current Sun Apr 21 11:30:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from ns.rim.or.jp (ns.rim.or.jp [202.247.128.2]) by hub.freebsd.org (Postfix) with ESMTP id 2A6B437B404 for ; Sun, 21 Apr 2002 11:30:23 -0700 (PDT) Received: from rayearth.rim.or.jp (uucp@rayearth.rim.or.jp [202.247.130.242]) by ns.rim.or.jp (8.9.3/3.6W-RIMNET-98-06-09) with ESMTP id DAA69769; Mon, 22 Apr 2002 03:30:21 +0900 (JST) Received: (from uucp@localhost) by rayearth.rim.or.jp (8.8.8/3.5Wpl2-uucp1/RIMNET) with UUCP id DAA07274; Mon, 22 Apr 2002 03:30:20 +0900 (JST) Received: from turkey.aslm.rim.or.jp (turkey.aslm.rim.or.jp [192.168.0.1]) by mail.aslm.rim.or.jp (8.11.4+3.4W/3.7W-SMTP) with ESMTP id g3LIM8I58407; Mon, 22 Apr 2002 03:22:08 +0900 (JST) Date: Mon, 22 Apr 2002 03:22:08 +0900 Message-ID: <87r8l8q5db.wl@turkey.aslm.rim.or.jp> From: Masafumi NAKANE To: current@FreeBSD.org Subject: noglob in recent tcsh User-Agent: Wanderlust/2.8.1 (Something) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/20.7 (i386--freebsd) MULE/4.0 (HANANOEN) X-PGP-Fingerprint: EB40 BCAB 4CE5 0764 9942 378C 9596 159E CE35 6B59 X-ICQ-UIN: 46494717 MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, As I upgraded my current and 4-stable boxes to recent ones, I noticed that eval `tset -s` no longer works on the stock tcsh. It gives error message such as ``Missing ].'' I tried to figure out what is going wrong and here's my finding: 1. If an open brace is included in the string to be executed through the command substitution mechanism (i.e. enclosed in ``'), any `{' and `[' that appear after the first occurrence of `{' (including this first one) is not escaped even when the shell variable noglob is set. So, for example, the following doesn't work: % eval `tset -s` 2. This doesn't happen if you give name of the file that contains the same string to tcsh as the command-line argument. So, for example, the following works: % tset -s > tset.out % tcsh tset.out This is all I have been able to find out, and I don't have much clue where to look into. Or, has there been any change to tcsh which causes this problem? Cheers, Max To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message