i wonder how many times i've typed the "ls" command

[aeva@mastodon.gamedev.place]

i wonder how many times i've typed the "ls" command

[snoopj@hachyderm.io]

@aeva can probably get a good upper bound by measuring (or estimating) number of times in a single day and coming up with some reasonable number of days.

my guess: lots

[chagrins@mastodon.gamedev.place]

@aeva I'd love it if there was a command counter.

[ireneista@adhd.irenes.space]

@aeva one of life's true unknowables

[oblomov@sociale.network]

@Chagrins @aeva

If we ignore pipes, history | cut -f1 -d' ' | sort | uniq -c gives a zero-order approximation. Maybe we can ask a developer of more modern shells to implement the feature as a built in? 8-D

[brooke@bikeshed.vibber.net]

@aeva if they'd named it just "l" you could've saved half the accumulated time

[rotopenguin@mastodon.social]

@aeva once. For everything else, there's the up arrow.

[j12t@j12t.social]

@aeva I wonder how many times i mistyped the ls command.

[chagrins@mastodon.gamedev.place]

@oblomov @aeva Sounds like a request worth making.

[q_observations@mstdn.social]

@aeva it’s why they invented scientific notation

[oblomov@sociale.network]

@Chagrins @aeva

also I forgot the history prints the line number in front, so instead of cut it's better something like awk '{ print $2 }'

[adrake@sfba.social]

@aeva "bash wrapped, your 2025 command line in numbers!"