bash-fuck
bash-fuck is a new command introduced to linux. You can install it on a bash shell and use it via the command "fuck". (by Ruesa18)
command_help
:information_source: Extract help text from builtin commands and man pages (by learnbyexample)
Our great sponsors
bash-fuck | command_help | |
---|---|---|
1 | 8 | |
0 | 88 | |
- | - | |
2.4 | 0.0 | |
almost 3 years ago | over 3 years ago | |
Shell | Shell | |
GNU General Public License v3.0 only | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
bash-fuck
Posts with mentions or reviews of bash-fuck.
We have used some of these posts to build our list of alternatives
and similar projects.
-
Give me your funniest alias ideas and I might add them for the lols
Also consider installing fuck
command_help
Posts with mentions or reviews of command_help.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-08-26.
-
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.