Create manpages, insert preinst, postinst, prerm and postrm
Markdown manpages
lite command line tldr client; simplified and community-driven manpages
manpages from node api reference
Convert manpages to PDF
TypeScript HTTP client for the zig-serve REST API — chat, workflows, sessions, manpages, users
a grunt-task for using marked-man to generate manpages from markdown
A Hubot script for searching, and viewing examples in a collection of simplified, and community-driven man pages (powered by http://tldr-pages.github.io/).
Wrapper around Apple's simctl binary
A command line utility that allows read/write (i.e copy/paste) access to the system clipboard.
Structured Node.js bindings for MySQL.
Wrapper around Apple's simctl binary
extract metadata and provisioning information about an .ipa file
Send HTTP requests, scrape webpages, and stream data in your JavaScript/Node.js/Sails.js app with a simple, `jQuery.get()`-like interface for sending HTTP requests and processing server responses.
Work with strings.
Work with child procs and the running process.
Work with the local filesystem; list files, write files, etc.
Machines for working with URL strings.
Node.js/TypeScript bindings for nono capability-based sandboxing
Produce interactive prompts in the console and consume the answers.
Raw sockets for Node.js.
Structured Node.js bindings for MSSQL.
Miscellaneous utilities for everyday tasks with arrays, dictionaries, strings, etc.
The Yandex Smart Home skills for the different device types.
Converts a clap cli into a basic manpage that can be further customized
keybinding to open man page currently typed command
Generate LLM-powered exam questions from YAML books, manpages, mdbooks, tealdeer pages, and code.
coreutils ~ GNU coreutils (updated); implemented as universal (cross-platform) utils, written in Rust
Find your lost manual pages
A CLI for Bugzilla, inspired by gh
Keep track of all the git repositories on your machine.
Generate Bash/Zsh completions from manpages or JSON/KDL files
AI-powered manpage assistant using local LLM
A manpage generator for clap
Help to Options - Parse help or manpage texts and generate shell completion scripts
Library for writing application manpages
With this gem the rubygems command will detect man pages within gems and exposes them to the man command.
Converts markdown into UNIX manpages and HTML webpages.
Produces UNIX manual pages for executable scripts.
view manpages in an ncurses window and navigate with vim bindings
RONN plugin for Detroit build system. Build roff manpages for your project.
You've seen Getopt::Long, OptionParser, Thor? What the world needs now is one more command-line parser. This serves as a backend command line parser that passes the option-parsing portion of it off to OptionParser, Trollop, or any other option-parser that has an adapter[^adapter]. But the parts it *does* do are really exciting: It features arbitrarily deeply nested subcommands, optionally colorized help screens with smart formatting, automatically generated usage syntaxes, manpage generation[^maybe2], lazy-loading of subcommands, and (get this:) you can turn your command line app into a web app. (is processing a form then displaying a record really that different from CLI that does the same?)[^maybe3]
Have you ever wanted to call <code>exit()</code> with an error condition, but weren't sure what exit status to use? No? Maybe it's just me, then. Anyway, I was reading manpages late one evening before retiring to bed in my palatial estate in rural Oregon, and I stumbled across <code>sysexits(3)</code>. Much to my chagrin, I couldn't find a +sysexits+ for Ruby! Well, for the other 2 people that actually care about <code>style(9)</code> as it applies to Ruby code, now there is one! Sysexits is a *completely* *awesome* collection of human-readable constants for the standard (BSDish) exit codes, used as arguments to +exit+ to indicate a specific error condition to the parent process. It's so fantastically fabulous that you'll want to fork it right away to avoid being thought of as that guy that's still using Webrick for his blog. I mean, <code>exit(1)</code> is so passé! This is like the 14-point font of Systems Programming. Like the C header file from which this was derived (I mean forked, naturally), error numbers begin at <code>Sysexits::EX__BASE</code> (which is way more cool than plain old +64+) to reduce the possibility of clashing with other exit statuses that other programs may already return. The codes are available in two forms: as constants which can be imported into your own namespace via <code>include Sysexits</code>, or as <code>Sysexits::STATUS_CODES</code>, a Hash keyed by Symbols derived from the constant names. Allow me to demonstrate. First, the old way: exit( 69 ) Whaaa...? Is that a euphemism? What's going on? See how unattractive and... well, 1970 that is? We're not changing vaccuum tubes here, people, we're <em>building a totally-awesome future in the Cloud™!</em> include Sysexits exit EX_UNAVAILABLE Okay, at least this is readable to people who have used <code>fork()</code> more than twice, but you could do so much better! include Sysexits exit :unavailable Holy Toledo! It's like we're writing Ruby, but our own made-up dialect in which variable++ is possible! Well, okay, it's not quite that cool. But it does look more Rubyish. And no monkeys were patched in the filming of this episode! All the simpletons still exiting with icky _numbers_ can still continue blithely along, none the wiser.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.