loading...
Cover image for Right click to explain commands..That's what's next.
kmdr

Right click to explain commands..That's what's next.

_ianeta profile image Ianeta Hutchinson ・Updated on ・1 min read

With a foundation of explanations established, we are now looking to bring kmdr more seamlessly into different development workflows. A browser extension will allow users to quickly check what all of the attributes of a command do before copying to the terminal.

fig1
Kmdr description webpage in the design phase

kmdr being in the terminal is particularly handy for those testing their memory of options or getting help via irc; however developers are also finding new commands on their browsers via sites like Stack Overflow or in a projects online documentation. The kmdr web extension is for devs in a β€œresearch session” within their browser, who value time over tabs and want concise and accurate explanations of a command ASAP.

The two-steps-away vision is the ability to select a command from anywhere in your browser and right click for access to the kmdr description.

The first milestone in the web-extension will be the ability to share kmdr descriptions via a URL provided by the CLI client. Users will be able to send and bookmark the URL of a kmdr description which will be rendered as an orphaned web page.

Invitations to early iterations and access to the browser extension will be coming to folks via our newsletter. Sign up today.

Tally-ho!

Discussion

pic
Editor guide
Collapse
jmfayard profile image
Jean-Michel Fayard πŸ‡«πŸ‡·πŸ‡©πŸ‡ͺπŸ‡¬πŸ‡§πŸ‡ͺπŸ‡ΈπŸ‡¨πŸ‡΄

ah ah great, adding a browser extension exactly the idea I wanted to give after reading your last article

There is something missing in the command line tool though Ianeta

I think kmdr explain should default to use the last command that was enterred in bash

a bit like github.com/nvbn/thefuck
but to explain thing instead of fixing them

Collapse
_ianeta profile image
Ianeta Hutchinson Author

Good idea! I hadn't thought about users explaining commands they'd just executed. But when you're kicking the tires it's precisely what you're after. I'm especially curious whether single word queries will go down after implementation. That'd be a win.
Heads to GitHub to log it