From: Maurice Lombardi Newsgroups: comp.os.msdos.djgpp Subject: Re: bash command file and windows pifs Date: Wed, 15 Nov 2000 20:41:41 +0100 Organization: Universite Joseph Fourier - Grenoble 1 Lines: 34 Message-ID: <3A12E6F5.2C0FBD90@ujf-grenoble.fr> References: NNTP-Posting-Host: knautie.ujf-grenoble.fr Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: amazone.ujf-grenoble.fr 974317307 92354 193.54.234.27 (15 Nov 2000 19:41:47 GMT) X-Complaints-To: abus AT ujf-grenoble DOT fr NNTP-Posting-Date: 15 Nov 2000 19:41:47 GMT X-Mailer: Mozilla 4.7 [fr] (Win98; U) X-Accept-Language: fr,it,en To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Todd Beckering a écrit : > > I'm trying to associate a bash command file with a windows file type, and am > having a problem. I set up the associating pif command line: > bash_path my_command_file_path %1 > but when I double click on a file, bash executes the file I click on (%1), > instead of my command file. It looks like windows is executing: > bash_path %1 > I've used pifs for other command files, and they work fine, including > parameters. It's the %1 that seems to throw a monkey wrench in things. > Any pointers on how to do this? > Thanks. > > I'm running Windows ME. I have only a pif for bash, which contains only c:\djgpp\bin\bash.exe in the command line (and a setdjgpp.bat in the third line "command file" of the pif (not sure of the wording, I have a french version of W98), since I use different compilers which may conflict) Then I set the "open" command for the windows file type as c:\djgpp\bin\bash.exe my_command_file_path '%1' (the pif is selected automatically) For me it works. If not the problem is with ME. -- Maurice Lombardi Laboratoire de Spectrometrie Physique, Universite Joseph Fourier de Grenoble, BP87 38402 Saint Martin d'Heres Cedex FRANCE Tel: 33 (0)4 76 51 47 51 Fax: 33 (0)4 76 51 45 44 mailto:Maurice DOT Lombardi AT ujf-grenoble DOT fr