docopt

docopts

Shell2019–2023

docopt / docopts

docopts

Shell interpreter for docopt, the command-line interface description language.

Command Line Languages & Compilers

Explore on GitHub Read Hacker News discussions

5Distinct people

5Mentions

0Explicit recommenders

519GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Shell interpreter for docopt, the command-line interface description language.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year5 dated mentions

Observed mentions: 2019-02-21 21:59:59 UTC to 2023-03-20 18:02:54 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	1	1
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	1	1
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	0	0
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	1	1
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	2	2

What Hacker News says

5 sources

tveyben·Mar 20, 2023

I have great pleasure when using docopt in Python. I see docopts is ‘the same’ implementation but for shell, have never tried it though. ==== docopt helps you: - define the interface for your command-line app, and - automatically generate a parser for it. ==== http://docopt.org/ https://github.com/docopt/docopts

In Argbash – Bash Argument Parsing Code Generator

Joker_vD·Mar 20, 2023

Huh, it uses M4 to build its DSL, how quaint. I wish there were more projects on the other side of the spectrum: take the script's self-reported usage string, à la docopt [0], and derive argument-parsing code from that. After all, we have GPT-4 now. [0] https://github.com/docopt/docopts

In Argbash – Bash Argument Parsing Code Generator

RhysU·Mar 3, 2022

Feels like https://github.com/docopt/docopts

In Argc – A handy way to handle sh/bash CLI parameters

OJFord·Oct 2, 2020

Docopt exists (now, think it was originally python) for many languages including bash [0] (or perhaps it's POSIX, haven't checked). I like it too, not least because I can use ~the same thing in multiple languages and not have to remind myself how the arg parser for language X works each time. [0] - https://github.com/docopt/docopts

In Bash code generator for command-line arguments

jasonpeacock·Feb 21, 2019

Yes! So much yes. Many developers write crappy Bash scripts because they don't see it as a real language, but it's an interpreted language just like Ruby, Python, Perl, etc. If you're going to design modular libraries and scripts with best practices, unit tests, etc, for those languages, then you should be doing the same with Bash. If you're writing production scripts using Bash, you should be following software best practices - don't give me any "it's just Bash" excuses. Mocking In addition to bats-mock (part of the bats library in the article), there is another mocking approach: https://pbrisbin.com/posts/mocking_bash/ They both have their uses. Documentation NaturalDocs ( https://www.naturaldocs.org/ ) can happily parse & extract doc comments from your bash scripts & libraries: https://www.naturaldocs.org/ Just define your own language

Read the rest

: https://www.naturaldocs.org/reference/languages.txt/#adding_... Format: 1.4 Language: bash Shebang Strings: bash Extensions: bash sh Ignore Extensions: bats Line Comments: # Linting Use shellcheck, it's amazing: https://www.shellcheck.net/ If you use Vim, w0rp/ale knows how to integrate with it for real-time feedback: https://github.com/w0rp/ale/tree/master/ale_linters/sh Argument Parsing Use Docopt ( http://docopt.org/ ) to get modern arg-parsing in your Bash scripts. Don't waste your time trying to roll your own or use the built-in anemic arg-parsing. Shells implementation: https://github.com/docopt/docopts Use Bash built-ins Stop invoking external processes for features already available in Bash: https://github.com/dylanaraps/pure-bash-bible More good resources: * http://www.tldp.org/LDP/abs/html/ * https://www.gnu.org/software/bash/manual/bashref.html * http://mywiki.wooledge.org/BashGuide BUT why are you using Bash? Go use a modern language and don't suffer the idiosyncrasies of Bash where you have to re-invent many common libraries already available like JSON parsers, etc. My favorite Bash replacement is Python + Plumbum: https://plumbum.readthedocs.io/en/latest/ All the convenience of Bash when invoking commands (no more subprocess()!) with the joy of Python.

In Testing Bash with BATS