On 05/02/00, "Tim Hammerquist <[EMAIL PROTECTED]>" wrote:
> "Ian D. Stewart" wrote:
> >
> > This is one area where the UNIX shebang excells. No need to create new
> > extensions or use the fullpath on the command line. Just specify the
> > executable you want to use in the script itself.
{snip}
> Yes. The cygwin bash prompt will scan the first line of potential
> scripts to see if they contain the shebang line. Apache also
> (independently) supports use of the shebang line, but won't support
> cygwin's symlinks. {snip} If I try to make a hard link with cygwin, it
> just copies the file (plus it loses the contents of @INC); I guess the
> FAT system won't support multiple hard links to the same file?
I am not an expert but I am pretty sure that's quite exactly the problem.
The FAT partition isn't a place to get maximum value out of Cygwin. On NTFS
you can make links etc. work better.
> Anyway, if anyone has any input to this problem, I'd like to hear it.
Like I say, I am no expert on this. I am not sure I understood completely
what you are trying to do. But one thought that occurs to me is whethere
you couldn't use the "alias" facility of a bash to change what happens when
a certain command is input. That is, alias a new interpretation to a simple
command. My Cygwin bash is set up to run .bashrc on login and my .bashrc
has these entries:
#ALIASES
#opens directory in 'open' view:
alias openthis="explorer ."
#opens current directory in 'double-pane (Explorer-style)' view:
alias explorethis="explorer /E, ."
alias cpan='perl -MCPAN -e shell'
alias perldoc='perldoc.bat'
-----------------------------------------
Maybe you could set something up that would take care of some of what you
need.
Running ActiveState Perl under Cygwin bash isn't a perfect solution for
everyone IMO (in fact I have a different Perl set up to run when I fire up
bash, a Cygwin Perl build) but the basic idea here that was also recently
suggested in another form by other contributors on this list is what I have
found to be most workable, that is, to create customized environments
through the use of batch files rather than to try to memorize sequences of
complex commands and variations for different situations. Needing to do
more with Perl has caused me to learn a lot about shell scripting
particularly the native NT shell. I have a growing collection of somewhat
powerful bat files that do some cool stuff. However, no, of course the NT
shell can't be made to (or can it ... hmmmm with a little fancy footwork,
why not??) parse the shebang line of scripts, that it doesn't do on its
own.
soren andersen
http://www.wonderstorm.com/techstuff/Perl_dex.html
---
You are currently subscribed to perl-win32-users as: [archive@jab.org]
To unsubscribe, forward this message to
[EMAIL PROTECTED]
For non-automated Mailing List support, send email to
[EMAIL PROTECTED]
