You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
We can now specify our own whitelisting file, overriding the default of 'lenchk-excludes' which must stay in the same directory as lenchk, at least for now. The custom file can be wherever you want it, however. I'd like to use the `readarray`/`mapfile` BASH built-in for populating the array variable, but it didn't seem to want to work, so I just went for another `while read` loop. It's working very nicely as-is, though. I've changed the required whitelist format to one of simplicity: one filename per line. Why the previous format? Because of files which may have a newline character in them, but I realised in this environment that's just not going to happen; force of habit, I guess. I'd like to allow users to be able to whitelist entire directories, but I don't see that being so high on the priority list, for now. What do you think? |
4 years ago | |
---|---|---|
see_also | 7 years ago | |
sheets | 4 years ago | |
tests | 4 years ago | |
LICENSE | 7 years ago | |
README.md | 4 years ago |
README.md
cheat.sheets
Own cheat sheets repository of the cheat.sh.
If you want to add a cheat sheet to cheat.sh directly, add it here (please also consider adding your cheat sheet to one of the upstream repositories).
When adding a cheat sheet please use the following format:
# Command name
# Short command description
# Command usage example1 started with some comments
# and followed with a command example/switches.
command1
# Command usage example2.
# Each block separated with an empty line.
command2
For example:
# curl
# Command-line tool for transferring data with URL syntax
# Process a single GET request, and show its output on stdout.
curl http://path.to.the/file
Requirements and constraints:
- Maximum length of a comment line (including comment sign) is 80
Other requirements can be proposed and discussed in #101