3 ms·
A typical command I run is never going to be something I look up again, so I would prefer to optimize for writing instead of reading. Dumping every command to a
by jefftk 3y ago
A typical command I run is never going to be something I look up again, so I would prefer to optimize for writing instead of reading. Dumping every command to a file adds no friction to my regular work, while attempting to categorize garbage commands would add a lot of friction.
Also, when I do want to reference my deep history I often find that seeing the full list of what I was doing is helpful at getting myself back into the frame of mind I was in when I ran the commands originally, which can be more valuable than seeing exactly which commands I ran.
- mathfailure 3y ago> A typical command I run is never going to be something I look up again, so I would prefer to optimize for writing instead of reading. Dumping every command to a file adds no friction to my regular work Then why write history at all? Just discard it.
- jefftk 3y agoBecause even with the friction of my history not having been pruned or otherwise tidied it's still a really valuable resource when I do need it!