Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!caip!princeton!allegra!ulysses!mhuxr!mhuxt!houxm!ihnp4!oddjob!mrl From: mrl@oddjob.UUCP (Scott R. Anderson) Newsgroups: net.unix Subject: Re: setenv problem in C-shell (and "tset") Message-ID: <1473@oddjob.UUCP> Date: Sun, 14-Sep-86 09:15:13 EDT Article-I.D.: oddjob.1473 Posted: Sun Sep 14 09:15:13 1986 Date-Received: Mon, 15-Sep-86 20:18:37 EDT References: <3454@brl-smoke.ARPA> <1427@tektools.UUCP> <1446@tektools.UUCP> Reply-To: mrl@oddjob.UUCP (Scott R. Anderson) Organization: University of Chicago, Department of Physics Lines: 30 In article <1446@tektools.UUCP> jerryp@tektools.UUCP (Jerry Peek) writes: >In article <1427@tektools.UUCP>, net.unix-wizards, I followed up to a >followup article about "tset": >> In article <3454@brl-smoke.ARPA> DU>@brl-smoke.ARPA writes: >> > set noglob; eval `tset ... ` >> Not just that! Don't forget to do "unset noglob" -- otherwise, the shell >> won't expand filename wildcard characters afterwards. Do this: >> set noglob; eval `tset ...`; unset noglob >Since then, I've noticed that under 4.3BSD and C-shell, "tset" outputs >both the "set noglob" and "unset noglob" commands automatically. This is also true of the 4.2 systems around here; unfortunately, that first "set noglob" doesn't do you any good, as any globbing on `tset ...` occurs before eval gets to it. The command "echo `tset ...`" shows you the arguments that eval actually sees, and they probably aren't what you want, unless globbing has been turned off. So, it looks like the mininum we can get away with is >> > set noglob; eval `tset ... ` -- * * * Scott Anderson * * * * uucp: ihnp4!oddjob!kaos!sra * * ** arpa: oddjob!kaos!sra@lbl-csam * * * * * * * * bitnet: sra%kaos@UChicago * * * * * * * * * * * * * * * * * * * * * * * * * * * * *