Mail Archives: djgpp/2000/11/25/03:08:48
You might want to take a look at:
http://www.fvu.myweb.nl/Projects/Bash/Web/bash.htm
This page describes how to hook the bash shell into the Windows Operating
System in various ways.
Gr, Freddy Vulto
Jason Green <news AT jgreen4 DOT fsnet DOT co DOT uk> wrote in message
news:cvlo1t47lh70t10duksb8o31vhoql4g0ov AT 4ax DOT com...
> "Todd Beckering" <ToddBeckering AT worldnet DOT att DOT net> wrote:
>
> > 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?
>
> From your description of the problem it looks like you are entering
> the %1 in the "Cmd line" field of the PIF settings. The %1 is treated
> literally, but it's possible to use a ? to generate a dialog box each
> time the program is run, asking for the parameter value.
>
> If that's not what you wanted, then I don't think you really want a
> PIF file either (except perhaps one to set memory requirements etc.)
> Instead the %1 will form part of the action field in the File Type
> edit box (as someone else has suggested).
>
> Sorry for the late reply. I hope this helps in some way, or that you
> already solved the problem.
- Raw text -