Julia Evanswhat's a popular command line tool (other than git) that you wish had a clearer / more intuitive UI? I'm thinking of tools like `dig` which has this IMO pretty arcane output format
Alanfor ffmpeg: ffmprovisr is am amazing list of ffmpeg recipes https://amiaopensource.github.io/ffmprovisr/
I often wish I could search through other people's shell histories for commands I'm learning, to see how they're using them (in some kind of privacy-preserving way)
Tim Penhey 🇳🇿@b0rk I wonder if https://github.com/ellie/atuin could be used in some way for this?
@thumper that's really cool!
b4ux1t3 
#1️⃣
#[deprecated] Qyriad@thumper @b0rk See also https://github.com/xonsh/xonsh which has a similar kind of rich history by default
Andreas Helbech Kleist@thumper
I think it would be against the core privacy principle in atuin.
@ellie did you consider this feature?
I'm wondering if keeping statistics of a SHA of each command could be abused? Assuming that often used commands are most interesting of course.
It might be safe if each user could be asked to approve sharing of specific commands.
Ellie HuxtableI have been wanting to do something like this for ages! But doing so in a safe way is difficult, and I don’t want to even risk the perception that your data is not private
The two options we have that could work
1. Opt in sharing of “atuin stats” output
2. As you say, some kind of opt in SHA fingerprint sharing
There’s a bunch we’re working on atm, with marking a command “public”/“shareable” potentially happening in the future
Gaëtan Duchaussois@b0rk you can gather a full list of typos with mine ! Not sure if helpful!
Florian Schmidt@b0rk
In a way, you can do this on https://www.commandlinefu.com
In case you didn't know it already, people post their favourite one-liners along with explanations, and vote for/against possible alternatives.
Lisa W. E.@schmidt_fu @b0rk Oh, that's cool!
In the same vein, I like Cheat (https://github.com/cheat/cheat) - it's *kind of* like seeing how people use commands (because people contribute to the cheat sheets). I use the cheat command way more often than man, that's for sure.
GitHub - cheat/cheat: cheat allows you to create and view interactive cheatsheets on the command-line. It was designed to help remind *nix system administrators of options for commands that they use frequently, but not frequently enough to remember.
cheat allows you to create and view interactive cheatsheets on the command-line. It was designed to help remind *nix system administrators of options for commands that they use frequently, but not ...
An Agora
Jeremy Allen@b0rk I thought I saw a shell recently that had social features, but now I cannot remember the name. I’ll look around.
Mandar Vaze (desipenguin)@mandarvaze @b0rk yeah that’s the one. It has a drive feature letting you save workflows that can be searched and accessed by your team
Joe Cooper 🇺🇦 🍉@b0rk I get so mad and frustrated at documentation if it doesn't have several examples in a prominent location. Going from Perl, where by convention the first section of a pod doc (what you get when you type `perldoc Module::Name`) is a Synopsis containing usage examples, to Python, where it decidedly, seemingly aggressively, is not the convention, was very painful. Examples are the only way I can learn something fast.
Chris [list of emoji]There's tldr, of course. That's in the distant neighbourhood of what you want.
JJ Celery@b0rk oh no Julia, no! 😦 It's garbage!
It's muscle memory and copy pasta... Half of us don't know what we're doing and the other half forgot the reason why this combination of switches "works" 🥲
@jjcelery archaeology is fun though
@b0rk I work with other sysadmins and I have seen / grepped our shared history to solve problems. Archeology is an appropriate term. We're all fossils 🥲
: j@fabrica:~/src; 
@jjcelery @b0rk I sometimes want to go through that garbage to improve my helper scripts. Or create stubs to remind me I wrote a script to chamfer the sharp edges off.
Like how I repeatedly cd deep into my ~/src directories then edit the current dir, when I have a `ze` script to present a fzf selector and open in $editor.
rhizome@b0rk
Mine is just "sudo !!"
Mine is just "sudo !!"
mhoyeThe ergonomic-improvement possibilities there are pretty huge, if you could get community buy-in.
What command combinations are so frequently used that they might deserve their own shortcut? What commands to people need to go to the man page before using most often, and how can they be improved?
I bet even just gathering usage stats from something like tldr would be a cli-ergo goldmine.
Brice Ruth@b0rk that would be … sick. Imagine having that at your ctrl-r disposal?!? 😍
David Blume@b0rk Related, you can usually tweak your shell's history settings to only keep unique and interesting commands you've executed, so it's easier to find them. https://medium.com/@dblume/have-only-unique-lines-in-your-bash-history-941e3de68c03
Mike Zamansky@b0rk Back in the day, you kindof could - when I was first learning, most users on the systems I were on left everything open so you could learn by exploring others directories. At least on some of the systems I was on, it was accepted and in fact encouraged.
It was another time.
Ben Lopatin> git rebsas —interactive
> git rebase —intectv
> gitrbsse—interactive
> sudo shutdown
Dan Copeland 🇨🇦🇺🇦🇵🇸@b0rk this was a thing I loved about full time pairing— the chance to learn from how everyone on your team used their tools
Norman Wilson@b0rk I used to learn a lot while looking (consensually) over friends' shoulders. The disappearance of the shared terminal room/lab is a loss.
Jeroen Baert@b0rk oh this is lovely, bookmarked
jimmyhartington@b0rk @caseyliss seems like something for you?
Jon Steege@b0rk Working on editing a bunch of video today via command line and other tools.. this is amazingly prescient!
Lou Katz@b0rk The ffmprovisr is a spectacular resource. Thank you
Reed Mideke@b0rk Oh that's great, thanks! Like a grown up, actually knows what it's doing version of the .txt file I paste complicated commands in after I get them working
joel cretan@b0rk yeah, this one. ffmpeg is impossible. Thanks!
Steve Young@b0rk
Thanks! That looks very useful. I have spent a lot of time looking through the command line flags for what I need, and this will help a lot.
Thanks! That looks very useful. I have spent a lot of time looking through the command line flags for what I need, and this will help a lot.
Florian Voggeneder@b0rk thats such a helpful resource! I just have a messy txt with recipies that might have worked or not prevously...