From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 486 invoked from network); 4 Nov 1998 20:32:42 -0000 Received: from math.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 4 Nov 1998 20:32:42 -0000 Received: (from list@localhost) by math.gatech.edu (8.9.1/8.9.1) id PAA01567; Wed, 4 Nov 1998 15:26:54 -0500 (EST) Resent-Date: Wed, 4 Nov 1998 15:26:44 -0500 (EST) To: zsh-users@math.gatech.edu Subject: scripting problem: vi and multiple arguments From: Jason Price Date: 04 Nov 1998 15:25:18 -0500 Message-ID: X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Resent-Message-ID: <"iVhAR2.0.vN.3YBGs"@math> Resent-From: zsh-users@math.gatech.edu X-Mailing-List: archive/latest/1921 X-Loop: zsh-users@math.gatech.edu X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu I'm writing a front end to RCS. (very very small) to deal with people being forgetful about removing file locks. I want to parse the command line to the script like this: rvi file1 file2... And then I want to call vi like this: vi file1 file2 however, as I loop through the arguments to rvi, unlocking as needed, yadda yadda, I build a variable called $EDFILES then I call vi $EDFILES however, zsh is sending all of $EDFILES to vi as one string to argv[1]. I want each entry in $EDFILES to be a seperate entry into argv. How can I do this? Should I build $EDFILES differently? I could do: for i in $EDFILES; do vi $i done but that would be different from how vi works with multiple files, and I want this to be as seamless as possible.... RTFM's welcome with a pointer to the right FM. Thanks for any help; Jason -- "Where will I go?" "Somewhere where they know nothing about computing... Where they wouldn't know a RAM chip from a potato chip!" "But I don't want to visit Microsoft!" --the PFY and the BOFH Jason Price jprice@gatech.edu Theta Xi, Beta Alpha 449