command_help
dotfiles
Our great sponsors
command_help | dotfiles | |
---|---|---|
8 | 5 | |
88 | 125 | |
- | - | |
0.0 | 6.5 | |
over 3 years ago | about 1 month ago | |
Shell | Shell | |
- | The Unlicense |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
command_help
-
Ask HN: What do you use to make CLIs?
I use a lot of CLI tools, but haven't written many for myself. Mostly, aliases/functions and some scripts in Bash/Python.
Extract details for command options from man/help: https://github.com/learnbyexample/command_help/blob/master/c...
cut-like syntax for field manipulations with regexp, negative indexing, etc: https://github.com/learnbyexample/regexp-cut/blob/main/rcut
simple calculator using python syntax: https://learnbyexample.github.io/practice_python_projects/ca...
- A better way of displaying help text on the command line
-
Enter a command to see help text for each arg
I wrote a Linux CLI tool [0] that parses the man/help pages to extract option details. Works most of the time for me, but there are plenty of corner cases that don't work.
-
What tools / utilities have you written that you use regularly?
https://github.com/learnbyexample/command_help to extract help text from builtin commands and man pages, ex:
-
What's a program you made that you actually use regularly?
https://github.com/learnbyexample/command_help is big enough to warrant a repo, examples, limitations, etc. I had a list of todo items to improve the script, but after years of usage, I'm fine with the limitations since I rarely encounter them. This helps me to extract documentation of particular options, here's an example:
-
Save Time Using Manop to Print Only Selected Content From the Man Page using Manop
I wrote one a few years back (https://github.com/learnbyexample/command_help). It has a few corner case issues, but works most of the time for me and supports multiple options to be retrieved.
-
Explainshell - A tool that takes any shell commands, looks up the syntax and options from man pages, and steps you through what it does!
I particularly wanted to lookup documentation for command options from my terminal (instead of the website), so wrote a script for it: https://github.com/learnbyexample/command_help ... Have a long pending todo list, but despite the issues, the tool is good enough for my needs.
-
Testing
When I start a project, I usually try to write the programs incrementally. Say I need to iterate over files from a directory. I will make sure that portion is working (usually with print() statements), then add another feature — say file reading and test that and so on. This reduces the burden of testing a large program at once at the end. And depending upon the nature of the program, I'll add a few sanity tests at the end. For example, for my command_help project, I copy pasted a few test runs of the program with different options and arguments into a separate file and wrote a program to perform these tests programmatically whenever the source code is modified.
dotfiles
- Extended Inline ASM for custom memset(ptr, 0, len) segfault? It usually does not do so in identical extern ASM.
- skeeto/dotfiles: My personal dotfiles
-
(x86-64, Windows) Pushing variable to stack for call
Intel's manuals: fantastic reference once you learn how to read it. I looked up push in here when I helped you, which is how I knew there was no 64-bit immediate push. I use it so often I built a tool to quickly jump to specific mnemonics: x86-index builds an index and x86-lookup opens the PDF to the right page (works on Windows given a proper shell).
-
What tools / utilities have you written that you use regularly?
qpkg: personal package manager, for managing custom-built packages in ~/.local.
-
Linux graphics from scratch
I know what you mean, which is part of why I don't run any of the mainstream desktop environments. Instead I run Openbox (config) without a taskbar or anything like that. If I really want to focus, or I'm working on a remote machine, then I'll fullscreen the terminal (not maximize, actually fullscreen) and essentially just use tmux as my window manager.
What are some alternatives?
pinpoint - Keystroke launcher and personal command central. Alternative to Spotlight and Alfred for Windows. Alternative to Wox, PowerToys.
smenu - smenu started as a lightweight and flexible terminal menu generator, but quickly evolved into a powerful and versatile CLI selection tool for interactive or scripting use.
hn-reader - A dark mode reader app for Hacker News
nbrowser - 🔗 🌐 : an easy way to open links in browsers, mimic the "Open URL with..." dialog on Android, `nbrowser` help you open links in a browser
tera - Interactive Bash script terminal music radio player. Play your favorite radio station, CRUD your favorite lists, and explore new radio stations from your terminal.
hastyhex - A blazing fast hex dumper
ffupdate - A shellscript to automatically install and update firefox on linux.
td-cli - A todo command line todo manager ✔️
sc2-replay-go
kks - Handy Kakoune companion.
ledger - Double-entry accounting system with a command-line reporting interface