On Mon, Oct 30, 2006 at 03:56:02AM +0900, Andreas S wrote:
> 
> 
> 
> >From: "Robert Klemme" <shortcutter / googlemail.com>
> >
> >So basically you should *always* use the shebang line to make clear which 
> >interpreter is supposed to execute a script - even if "it works without" 
> >and you do it only for documentation reasons.
> >
> Just seconds after I posted I found I made a fool of myself. %x{testme.sh} 
> doesn't work as well.
> 
> You're point is well taken and I must agree with you. However, I'm also 
> curious about what's going on under the hood. What does ruby do when I use 
> double quote in backtick why it runs the command while without double quote 
> it doesn't? (Sometimes I made my life harder by not knowing where to stop 
> and keep moving along)
> 
`simple` # Ruby thinks, I can handle this myself
`"simple"` # Some extra chars in there huh, I'd better start a shell and
let it parse this craziness

The side-effect being of course that the shell decides to run it as a
shell script, or whatever.
> -andre
> 
> _________________________________________________________________
> Try the next generation of search with Windows Live Search today!  
> http://imagine-windowslive.com/minisites/searchlaunch/?locale=en-us&source=hmtagline
>