▲ 429 ▼ Linux Cat (lemmy.zip) submitted 1 week ago by shark_byte@lemmy.zip to c/programmer_humor@programming.dev 68 comments fedilink hide all child comments ahh ~$ which cat
[–] rumba@lemmy.zip 12 points 6 days ago (1 child) tac permalink fedilink source hideshow 2 child comments replies: [–] Sprocketfree@sh.itjust.works 3 points 6 days ago (1 child) I've always wondered what a good use case for tac would be... permalink fedilink source parent hideshow 2 child comments replies: [–] rumba@lemmy.zip 3 points 6 days ago (1 child) Reverse chronological order, mostly tac log.txt |head # would give you newest first no good for sort because sort already supports -r no need it for tail on large files because tail already skips to the end. I do a lot of impromptu bash to sus crap out of logs. when you're balls deep in cat log|grep -v foo| rev|cut -f 1-3 -d \ | |rev Sometimes tac comes in clutch. permalink fedilink source parent hideshow 2 child comments replies: [–] Sprocketfree@sh.itjust.works 4 points 6 days ago That's fair. I'd usually just use less and drop to the end. My use cases would always need the older log before a newer log though because that's the start of the problem. At least that's how I operate. permalink fedilink source parent
[–] Sprocketfree@sh.itjust.works 3 points 6 days ago (1 child) I've always wondered what a good use case for tac would be... permalink fedilink source parent hideshow 2 child comments replies: [–] rumba@lemmy.zip 3 points 6 days ago (1 child) Reverse chronological order, mostly tac log.txt |head # would give you newest first no good for sort because sort already supports -r no need it for tail on large files because tail already skips to the end. I do a lot of impromptu bash to sus crap out of logs. when you're balls deep in cat log|grep -v foo| rev|cut -f 1-3 -d \ | |rev Sometimes tac comes in clutch. permalink fedilink source parent hideshow 2 child comments replies: [–] Sprocketfree@sh.itjust.works 4 points 6 days ago That's fair. I'd usually just use less and drop to the end. My use cases would always need the older log before a newer log though because that's the start of the problem. At least that's how I operate. permalink fedilink source parent
[–] rumba@lemmy.zip 3 points 6 days ago (1 child) Reverse chronological order, mostly tac log.txt |head # would give you newest first no good for sort because sort already supports -r no need it for tail on large files because tail already skips to the end. I do a lot of impromptu bash to sus crap out of logs. when you're balls deep in cat log|grep -v foo| rev|cut -f 1-3 -d \ | |rev Sometimes tac comes in clutch. permalink fedilink source parent hideshow 2 child comments replies: [–] Sprocketfree@sh.itjust.works 4 points 6 days ago That's fair. I'd usually just use less and drop to the end. My use cases would always need the older log before a newer log though because that's the start of the problem. At least that's how I operate. permalink fedilink source parent
[–] Sprocketfree@sh.itjust.works 4 points 6 days ago That's fair. I'd usually just use less and drop to the end. My use cases would always need the older log before a newer log though because that's the start of the problem. At least that's how I operate. permalink fedilink source parent