Timeline for Tips for golfing in Bash

7 events

when toggle format	what		by	license	comment
Sep 10, 2019 at 2:04	comment	added	mikeserv		@user16402 - you should have a fccing name to my purview... anyway, the `:` intrinsic eats not at all... if you supposit input to colon you might flood a pipe to in out error... but you can float a redirect by a colon, or drop a process with it... `:\| while i>&$(($??!$?:${#?})) command shit; do [ -s testitsoutput ]; done` or however that pseudo suggestion applies... also, are you aware youre nearly so ghosty as me? ... avoid at all costs the `< <(psycho shit i can alias to crazy math eat your world; okay? anyway, ksh93 has a separate but equal composite char placement)`
Jan 24, 2017 at 17:20	comment	added	F. Hauri - Give Up GitHub		Yes, it's a SIGPIPE problem: `tee >(:) < <(seq 1 10)` will work, but `tee /dev/stderr \| :` won't. Even `a() { :;};tee /dev/stderr < <(seq 1 10)\| a` don't print anything.
Feb 20, 2015 at 2:55	history	wiki removed	Doorknob
Nov 7, 2014 at 15:56	comment	added	kernigh		There is a race: `echo a\|tee /dev/stderr\|:` did print a on my computer, but elsewhere SIGPIPE might kill tee first. It might depend on version of `tee`.
Nov 7, 2014 at 6:27	comment	added	jimmy23013		No, it will crash the program with SIGPIPE in most cases. `echo a\|tee /dev/stderr\|:` will not print anything.
Jun 3, 2014 at 20:37	review	Low quality posts
Jun 3, 2014 at 22:44
Jun 3, 2014 at 20:18	history	answered	user16402	CC BY-SA 3.0