Hacker News Reader

Comment by w1ntermute | Hacker News Reader

Bash one-liner to play sedtris:

wget http://uuner.doslash.org/forfun/sedtris.sed && curl http://uuner.doslash.org/forfun/sedtris.sh | bash

Or if you're afraid, gem install gosh; wget http://uuner.doslash.org/forfun/sedtris.sed && curl http://uuner.doslash.org/forfun/sedtris.sh | gosh

https://github.com/sstephenson/gosh

Uh oh, you threw the stone in the proverbial argument well again:

http://news.ycombinator.com/item?id=2420509

You should be piping that into bash instead of sh.

With sh, it infinitely prints out

    [: 48: unexpected operator
    read: 48: Illegal option -s

Haha, I take it you're on Ubuntu? Ubuntu uses dash[0] as its default shell to speed things up. Funny thing is I've run into this same issue before in another context with sh vs bash on Ubuntu. In any case, updated.

0: https://secure.wikimedia.org/wikipedia/en/wiki/Debian_Almqui...

You know I almost specified my distribution but thought 'surely that wouldn't make a difference'. lol

Ubuntu uses dash as its default shell to speed things up.

Actually it is (sadly) the major reason, but not the only one:

The Debian policy manual has long mandated that "shell scripts specifying '/bin/sh' as interpreter must only use POSIX features"; in fact, this requirement has been in place since well before the inception of the Ubuntu project. Furthermore, any shell scripts that expected to be portable to other Unix systems, such as the BSDs or Solaris, already honoured this requirement. Thus, we felt that the compatibility impact of this change would be minimal. [1]

Personally I think that assuming nothing but POSIX is a more compelling reason than efficiency.

[1] https://wiki.ubuntu.com/DashAsBinSh

Reply on news.ycombinator.com