An interactive cheatsheet tool for the command-line

Post by rmetzler » Sat, Sep 21, 2019, 2:03 PM UTC

OJFord wrote: post #11

This looks cool, a common workflow of mine is `cmd --blah --blah ` ah damn I don't know the value for blah, okay, fzf ` --blah=(blahgen | fzf) ` oh I'm also missing [...] This seems like it can help do the same thing more quickly, so I'm keen to give it a go. I do like shell history though, a shame to just have a bunch of `navi` entries - I wonder if it could be faked; populated with the chosen command afterwards?

Post by mikelward » Sat, Sep 21, 2019, 4:01 PM UTC

davidjhall wrote: post #15

Is there a key command or way to find out what's below the cheat? For instance, I tried the "local ip address" example in the demo and it gave the IP address but now 'how' -- ifconfig? was it in a text file? env var? script?

Post by kissgyorgy » Sat, Sep 21, 2019, 4:58 PM UTC

crispyambulance wrote: post #29

kissgyorgy wrote: post #4

Once I tried a tool like this, but just realized, there is already a method of that: the ~/bin folder. You can write bash scripts, or scripts in any programming language with the proper shebang line, you can download other people's scripts, and you don't need bash history to keep them. Listing all of them is just an ls. I tend to not put file extensions of them and use good naming, so you can see everything without l…

> ... there is already a method of that: the ~/bin folder. More power to you if you can do that, but for me it's a memory problem and a problem of being able to figure out WTF options I need when I am in the middle of something. man pages (and --help) are great if you have the time to sit down, ponder and experiment. But when you're trying to get stuff overwith, a massive wall of historically interesting text just is…

Post by dnsfr » Sat, Sep 21, 2019, 11:32 PM UTC

DavideNL wrote: post #27

Looks really nice; I don't like the fact that an unknown command is executed before i can see/inspect what it is. Currently you won't even see what command was executed afterwards, you only see the result... Would be nice to be able to also show the command below the item/result. --print is possible, but it's cumbersome and not interactive: you can't "accept" the command after inspecting, and execute it.

Post by dnsfr » Sat, Sep 21, 2019, 11:37 PM UTC

obituary_latte wrote: post #26

Looks neat. I wish, though, there was a way to try it out in the browser as advertised without having to sign up or login. Might be a requirement of the site hosting the demo but whoever it is, forcing login is always and forever a deal breaker for me.