9 ms·

I've been curating my .bash_history for years; it's a great way to recall all those contorted commands which come in handy every year or so: https://github.com

by l0b0 10y ago

I've been curating my .bash_history for years; it's a great way to recall all those contorted commands which come in handy every year or so: https://github.com/l0b0/tilde/blob/master/.bash_history https://github.com/l0b0/tilde/blob/master/.bash_history Git GUI plus a simple Makefile target to sort it is all the tooling necessary: https://github.com/l0b0/tilde/blob/b16794f2ff209a6bc64813f0218168cca34e603f/Makefile#L94 https://github.com/l0b0/tilde/blob/b16794f2ff209a6bc64813f02...

monsieurbanana 10y ago
Holy guacamole. You madman, you put your whole bash_history on a public github? If someone put a gun on me and asked to give him my bash history, I'll probably do it but not before thinking twice. I've also kept my bash history (well, more like my zsh history actually) for a few years and across a few re-installs now. I'm sure there's a few cleartext passwords in there (for nothing too important), a couple of dubious wget commands, all the videos I've ever watched (I use a CLI video player) and who knows what else. Oh and a bunch of confidential work stuff, I'm sure. Now that I think about it, maybe I should delete it...
- gknoy 10y ago
  That was my initial thought as well, but looking at it, it seems like he really takes the time to _curate_ it: rsync --rsh='ssh -p 2020 -i ~/.ssh/host.pem' --archive --human-readable --progress --verbose host:/path /target # network transfer In examples like the above, he appears to have sanitized things to be useful from the perspective of "How do I do X again?" -- very cool.
makefu 10y ago
For me, the *_history is a deeply personal thing as it shows how i work and how i changed my working over the years. I think you are very brave to make this document available to the world - it is not something i would like to do. EDIT: I think of it like the browser history for your daily work. EDIT 2: It seems quite a lot of people think it is a good idea to store their bash_history on github, who knew! google dork: "inurl:github.com intitle:bash_history"

by l0b0 10y ago

monsieurbanana 10y ago

Holy guacamole. You madman, you put your whole bash_history on a public github? If someone put a gun on me and asked to give him my bash history, I'll probably do it but not before thinking twice. I've also kept my bash history (well, more like my zsh history actually) for a few years and across a few re-installs now. I'm sure there's a few cleartext passwords in there (for nothing too important), a couple of dubious wget commands, all the videos I've ever watched (I use a CLI video player) and who knows what else. Oh and a bunch of confidential work stuff, I'm sure. Now that I think about it, maybe I should delete it...

gknoy 10y ago
That was my initial thought as well, but looking at it, it seems like he really takes the time to _curate_ it: rsync --rsh='ssh -p 2020 -i ~/.ssh/host.pem' --archive --human-readable --progress --verbose host:/path /target # network transfer In examples like the above, he appears to have sanitized things to be useful from the perspective of "How do I do X again?" -- very cool.

makefu 10y ago

For me, the *_history is a deeply personal thing as it shows how i work and how i changed my working over the years. I think you are very brave to make this document available to the world - it is not something i would like to do. EDIT: I think of it like the browser history for your daily work. EDIT 2: It seems quite a lot of people think it is a good idea to store their bash_history on github, who knew! google dork: "inurl:github.com intitle:bash_history"