dukerutledge@programming.dev to Programming@programming.devEnglish · 2 years agoCommand Line Interface Guidelinesclig.devexternal-linkmessage-square14fedilinkarrow-up141arrow-down10cross-posted to: programming@programming.devhackernews@lemmy.smeargle.fansprogramming@programming.dev
arrow-up141arrow-down1external-linkCommand Line Interface Guidelinesclig.devdukerutledge@programming.dev to Programming@programming.devEnglish · 2 years agomessage-square14fedilinkcross-posted to: programming@programming.devhackernews@lemmy.smeargle.fansprogramming@programming.dev
minus-squareharuki@programming.devlinkfedilinkEnglisharrow-up6·2 years agoI’ve been using this guide for writing a CLI tool for my company. Kudos to the authors for the amazing insights.
minus-squarenivenkos@lemmy.worldlinkfedilinkEnglisharrow-up4·2 years agoFWIW a good library will do a lot of this for you - e.g. clap for Rust.
minus-squareharuki@programming.devlinkfedilinkEnglisharrow-up4·edit-22 years agoYes. I’m using Python Click FYI. I mean I’ve been writing a CLI tool, not a CLI engine.
I’ve been using this guide for writing a CLI tool for my company. Kudos to the authors for the amazing insights.
FWIW a good library will do a lot of this for you - e.g. clap for Rust.
Yes. I’m using Python Click FYI.
I mean I’ve been writing a CLI tool, not a CLI engine.