[aerique]

I do not understand your last paragraph. Don't your wrapper scripts have "#!/bin/sh" at the top?

[vietor]

That's being explicit, the problem is with wrapper scripts that omit that, assuming a sh compatible shell.

Still running fish on one of my systems, excited to see new development work as it was getting past the point where I was comfortable using it on anything new.

[nikkaelle]

An old trick for convincing (some) shells that your script is an sh-compatibile shell is to use a colon on the first line. Support for this trick was added to fish back in 2007: https://gitorious.org/~ridiculousfish/fish-shell/fishfish/bl...

[akkartik]

Thanks for the pointer. I can't say how much I wish more people would include pointers to code fragments or specific commits on a site called hacker news.

Tangential question: is gitorious's syntax highlighting usually this awful? The first thing I need from syntax highlighting is distinguishing comments from code.

[cheatercheater]

I'm not sure how to use it. Can you give an example of where it works, and what changes if this is not done?

[sirclueless]

The point isn't executables that happen to be written in {ba,}sh, it's wrappers that attempt to add functionality to your commandline. For example, Python's virtualenv and Ruby's rvm presumably don't work.

[ash]

I agree with your point. But virtualenv has support for fish:

    . your_env/bin/activate.fish

https://github.com/pypa/virtualenv/blob/develop/virtualenv_e...

[aerique]

Ah, I didn't think of that (no experience with neither virtualenv nor rvm). So thanks for the clarification.