bash:cheat_sheet
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| bash:cheat_sheet [2021/01/09 14:28] – [Command Completion] peter | bash:cheat_sheet [2021/01/26 11:55] (current) – [String Operators] peter | ||
|---|---|---|---|
| Line 84: | Line 84: | ||
| ===== Here Documents ===== | ===== Here Documents ===== | ||
| - | Bash allow here documents like this | + | Bash allows |
| <code bash> | <code bash> | ||
| Line 179: | Line 179: | ||
| -h FILE True if file is a symbolic link. | -h FILE True if file is a symbolic link. | ||
| -L FILE True if file is a symbolic link. | -L FILE True if file is a symbolic link. | ||
| - | -k FILE True if file has its `sticky' | + | -k FILE True if file has its sticky bit set. |
| -p FILE True if file is a named pipe. | -p FILE True if file is a named pipe. | ||
| -r FILE True if file is readable by you. | -r FILE True if file is readable by you. | ||
| Line 226: | Line 226: | ||
| ===== Simulate Reading From a File ===== | ===== Simulate Reading From a File ===== | ||
| - | Sometimes you might need to pass a file name when you want to pipe output from a commands. Then you could write to a file first and then used it, but you can also use the "> | + | Sometimes you might need to pass a file name when you want to pipe output from a commands. |
| + | |||
| + | Then you could write to a file first and then used it, but you can also use the "> | ||
| + | |||
| + | This can be used with all tools that demand a file name parameter: | ||
| <code bash> | <code bash> | ||
| Line 252: | Line 256: | ||
| </ | </ | ||
| + | |||
| + | ---- | ||
| ==== Adding Timestamps ==== | ==== Adding Timestamps ==== | ||
| Line 260: | Line 266: | ||
| HISTTIMEFORMAT=" | HISTTIMEFORMAT=" | ||
| </ | </ | ||
| + | |||
| + | ---- | ||
| ==== Easier History Navigation ==== | ==== Easier History Navigation ==== | ||
| - | If you do not like Ctrl-R to nagivate | + | If you do not like Ctrl-R to navigate |
| <code bash> | <code bash> | ||
| Line 269: | Line 277: | ||
| " | " | ||
| </ | </ | ||
| + | |||
| + | ---- | ||
| ==== History Hardening ==== | ==== History Hardening ==== | ||
| Line 311: | Line 321: | ||
| wait | wait | ||
| </ | </ | ||
| + | |||
| + | ---- | ||
| ==== Kill childs on exit ==== | ==== Kill childs on exit ==== | ||
| Line 322: | Line 334: | ||
| ==== Command Completion ==== | ==== Command Completion ==== | ||
| - | How to setup your own bash completion schemas. Here is a git example: | + | Setup your own bash completion schemas. |
| + | |||
| + | Here is a git example: | ||
| <code bash> | <code bash> | ||
| Line 350: | Line 364: | ||
| ==== Apply ulimit Changes Instantly ==== | ==== Apply ulimit Changes Instantly ==== | ||
| - | The problem behind this is documented in this blog post but it boils down to try to use the " | + | Try to use the " |
| <code bash> | <code bash> | ||
| Line 356: | Line 370: | ||
| </ | </ | ||
| - | If it doesn' | + | <WRAP info> |
| + | **NOTE: | ||
| + | </ | ||
| ---- | ---- | ||
bash/cheat_sheet.1610202525.txt.gz · Last modified: 2021/01/09 14:28 by peter