On Sep 24, 2009, at 12:46 PM, Mike Dubman wrote:
> Im not familiar with :\n semantics, how does it force Bourne shell
> and what it actually does :)? (seems like leftovers from 1960....)
Yes, it might be left over from 1960. :-) But the nice thing is that
you then don't have to identify /bin/sh or /usr/bin/sh. It's
convenient and it works everywhere.
> I think when interpreter is not explicitly specified - the default
> user`s shell is used.
> see in the DoCommand::Cmd() ..... it check the buffer`s first line
> for #!/... semantic and if found - saves buffer to file, adds +x
> perm, and just executes it as a regular script.
I don't think that's universal, is it?
> When I passed a buffer with shell commands but 1st line was not #!/
> bin/sh - it failed with syntax errors.
Right. Try passing with ":" as the first line. :-)
--
Jeff Squyres
jsquyres_at_[hidden]
|
![[Flag]](../../../../../community/mirrors/flag-us.gif){kind=small}