Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3EC1679B.5080305@kleckner.net> Date: Tue, 13 May 2003 14:46:03 -0700 From: Jim Kleckner User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3 X-Accept-Language: en-us MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Does cygstart always expand arguments? References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Igor Pechtchanski wrote: > On Tue, 13 May 2003, Jim Kleckner wrote: ... > I think you're confused about what cygstart does. Cygstart is for > situations when, given a data file, you want to run the associated > application, like double-clicking it in explorer. While you can use it to > launch .exe's (by definition), it's probably not what you want in this > case. Try invoking gvim without cygstart, i.e., simply > > $ gvim "file with spaces.txt" > > Hope this helps, > Igor > Running with gvim "file with spaces.txt" & is close to what I want but it is still attached to the shell as a subprocess. cygstart will nicely launch a completely independent process. So that I can exit the original bash and not have any issues with accidentally foregrounding that process. I do have the .txt file type associated with gvim but I use a text editor frequently to look at arbitrary file types or file types that correctly are registered to other programs. e.g. .html. Thanks for the suggestion though. Jim -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/