IRC fun

<adnauseaum> ello m8s

<adnauseaum> is dis where i bash ye fookin head in m8s?

<adnauseaum> ill hook ye in the gabber i swear on me mum

<greycat> Now, do you begin to understand what I mean when I write things like "In my experience, commercial Unix flavors tend to have rather poorly written shell scripts." ...

<realeyes> u wot m8

<adnauseaum> u cheeky cunt u av fuckin eyes m8?

<adnauseaum> i'll #bash ye fookin 'ead in

* Jetchisel waits for it to happen

<adnauseaum> wot u w8ing 4 m8?

<geirha> at least the osx one used ${1+"$@"}, but still utterly pointless

<adnauseaum> u scared u lil cheeky cunt?

<greycat> adnauseaum: Please stop.

<adnauseaum> fook u m8 stop wot?

<adnauseaum> u want sum fuk?

<Tjololo12> if I have a line of script like "if /bin/nice -n 19 /bin/gzip -f $COMPRESS; then"...How could I store the output of stderr to a variable for that command, so that I can see WHY it failed, not just THAT it failed?

<geirha> The only use for it I can think of is to check if some input ends with a newline or not

<greycat> Tjololo12: if err=$(nice -n ... 2>&1 >/dev/null); then     # this will discard stdout

<greycat> geirha: the word "execable" in mine seems to indicate that it's required to be present for something like find . -exec read

<Tjololo12> greycat: ty!

<greycat> geirha: I don't know of any *practical* purpose for it, though.

<adnauseaum> BASH IS GAY AND I HATE IT

<geirha> oh, that could make the -exec be true for the first two cases only

* ChanServ gives channel operator status to greycat

<adnauseaum> NO GAY CAT

<adnauseaum> PLS

* greycat sets ban on *!*@99.32.15.3

* greycat has kicked adnauseaum from #bash (adnauseaum)

* greycat removes channel operator status from greycat