On 03/30/10 15:14, David Frascone wrote: > I had to quit using fish, due to constant script incompatibilities. I guess > some script authors are too lazy to add hash-bang-bash to the top of their > scripts . . .
what? -- script files don't run unless you start the file with #!/bin/bash (or similar), or unless you invoke them as 'bash the_script_file' > Has anyone had any success making fish their real new home? Oh -- and I > also had some issues with the select bug that was posted here a while ago, > but is still not patched :( yes, fish has been my shell for a couple of years. The hilighting and history features are nice. So is the fact that I've got it storing my command history forever, rather than just, say, 500 previous commands (can you configure Bash to store history forever too?). But there are frequent bugs in various things like redirection, history up-and-down, maybe loops or syntax, etc... Whenever I want to do something semi-complicated, or if something didn't work as I expected in Fish, I switch to bash to make it work--Which I know well, because I write all my own scripts in bash. Also necessary for copy/pasting from the Internet. -Isaac ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
