Timeline for How to keep a set of commands in history?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 23, 2017 at 11:10 | vote | accept | ideasman42 | ||
| Oct 21, 2017 at 17:22 | history | edited | Thomas | CC BY-SA 3.0 | improved formatting |
| Oct 21, 2017 at 7:36 | answer | added | Stephen Kitt | timeline score: 5 | |
| Oct 21, 2017 at 6:13 | comment | added | ideasman42 | I do this already, as noted in the question, some commands need edits on each use - so don't make much sense to wrap into an alias/function/script. While they could take arguments, this means I'm writing my own commands with their own argument syntax - which is too much overhead for my taste. Said differently, there are times when I'd rather use history search. | |
| Oct 21, 2017 at 6:09 | history | edited | ideasman42 | CC BY-SA 3.0 | added 108 characters in body |
| Oct 21, 2017 at 5:33 | history | edited | ideasman42 | CC BY-SA 3.0 | added 4 characters in body |
| Oct 21, 2017 at 5:05 | comment | added | Basile Starynkevitch | I would instead recommend defining several zsh functions in your ~/.zshrc | |
| Oct 21, 2017 at 5:01 | history | edited | ideasman42 | CC BY-SA 3.0 | added 286 characters in body |
| Oct 21, 2017 at 4:53 | history | asked | ideasman42 | CC BY-SA 3.0 |