nion's blog

For those who didn't notice yet that their shell[tm] sucks (or are too lazy to switch) while there are better alternatives out there, there is a possibility for bash users to get a minimal spelling correction by doing:

shopt -s cdspell (or put this into your rc file).

Then you get spelling correction for the cd command.

To be serious, this is really not one of the typical shell vs. shell evangelist flames since I really used bash for some years before realizing that there are better alternatives which can do this for example with nearly everything and not just single commands (thats just one nice-to-have).

I really don't understand this, everyone is consequently looking for tools to fit their purposes best but just with their shells people are content with what they have and always had even if it's the rusty version of this shiny car you could have. I mean it's ok if you don't need it but before you use things like shopt -s cdshell just get a better shell.

[via: 256bit]

I recently had a nice discussion on a mailinglist about #!/bin/bash vs #!/bin/sh as the shebang line in shell scripts.
In general I support to use #!/bin/sh, maybe there are some corner-cases in which it makes sense to use #!/bin/bash, I am not a shell programmer.
But since the guy from shellscripts.org (btw why shellscripts and not bashscripts?) told me that I have to use a bashism to
alter a variable outside the scope of a loop because of the created subshell and in my opinion this is a common misunderstanding I blog this.



results in 123 because the loop has its own subshell and no access to foo outside of its scope.



is the proposed bashism to solve this issue, it will result in 456.



Also results in 456 and is sh-compliant (or at-least runs in ksh93 which is the reference implementation for the POSIX standard.
What also surprised me is that this is not running in bash, dash but in zsh
I reported this as a bug in bash and dash for Debian, please correct me if I am wrong.