Oddbean new post about | logout
 @menherahair @974dd529 @buy robux today :ROBUX: @surk⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠... That would be true (1), but in reverse order should be fine. 
 @Yukkuri @974dd529 @buy robux today :ROBUX: @surk⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠... it doesn't skip the lines with no second field, so you can't look for files named 4096 I guess 
 @menherahair @974dd529 @buy robux today :ROBUX: @surk⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠... That can be work-arounded by predicating on NF: awk '/pernias_passwords/ && NF >= 2 && $0=$2', but It also won't handle files with whitespaces and newlines in names properly. find . -path '*pernias_passwords*' -exec du -a {} \; might be required. 
 @Yukkuri @974dd529 @buy robux today :ROBUX: @surk⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠...

NF >= 2 && $0=$2’ this check on NF does nothing here, $0=$2 is already false if second field doesn’t exist to deal with whitespace in du output specifically, I guess it makes sense to just remove the first field instead, but then we can’t use that statement as the condition. du -a | awk '/pernias_passwords/{$1=""; print}' or to not match in filesizes: du -a | awk '{$1=""; if(/pernias_passwords/)print}'

on a side note, what I posted before actually won’t fly because of operator precedence. should be awk '($0=$2) && /pernias_passwords/'

ok I’m ready to sleep now gn