#!/usr/bin/python or #!/usr/bin/env python?

[Erik Max Francis]

Stephan Kuhagen wrote:

> Yes, the same happens with all Tcl-Scripts. I like to see this as a bug in
> "file", not in the scripting...

How does that make sense?  `file` cannot possibly understand the 
semantics of files at that level, at least not without executing them. 
And that's exactly what you _don't_ want to do when you're using `file` ...

The file _is_ a /bin/sh executable.  You're just having that /bin/sh 
executable run something else -- how could `file` figure that out 
without a ridiculously complicated set of rules that rise to the level 
of a sh interpreter -- thereby, defeating the purpose?

-- 
Erik Max Francis && max at alcyone.com && http://www.alcyone.com/max/
  San Jose, CA, USA && 37 20 N 121 53 W && AIM erikmaxfrancis
   Only those who dare to fail greatly can ever achieve greatly.
    -- Robert F. Kennedy