Obviously, both of those things could easily be added in a script
yeah way to easily to make them worth adding out of the blue...
alias tab return $chr(9)
alias tabbed { var %r = $tab, %i = $0 | while (%i) { var %r = $+($tab,$($+($,%i),2),%r) | dec %i } | return $mid($left(%r,-1),2) }
but then again, so could "alias true return 1" and "alias false return 0".
No they cant, at least in any constructive fashion...
alias true return 1
alias false return 0
//echo -a $!true = $true & $!false = $false
$true = $true & $false = $false* built in identifiers cant be replaced, and any logical purpose of using /TRUE or /FALSE folowed by $RESULT eludes me.
PS: The TABBED identifier is prone to collapsing a script, since each passed parameter can be the max string length, you can potentially pass it more than it can return/ contain in the %r value. ex...
//echo -a $tabbed($str(a,400),$str(b,400))
aaaa....aaaa<tab>bbbb....bbbb//echo -a $tabbed($str(a,400),$str(b,400),$str(c,400))
* String too long: $+ (line 2, tab&tabber.mrc)This would be the case with a internal command also.