3 ms·
OK but not writing your own Cron expressions is just sad.
by rpmisms 2y ago
OK but not writing your own Cron expressions is just sad.
- fartfeatures 2y agoNot everyone knows how to use Cron, the comment is a good tip for those that don't. The target audience for a solution like this might be less technical than the average Github user.
- anonymousiam 2y agoI'll assume that your comment was not intended to reflect on the average Bluesky user, but there might also be something there too.
- rpmisms 2y agoWe can be a little sassy, as long as we acknowledge that the average X user is no better.
- simonw 2y agoI've been using Cron for over 20 years. I still use https://crontab.guru https://crontab.guru rather than trying to remember the syntax for those fields.
- rpmisms 2y agoCron expressions aren't bad. Now regex.... nope.
- ASalazarMX 2y agoI can't even remember tar or find options reliably.
- Fnoord 2y agoTry tldr find or tldr tar for examples. Use fzf on history to find past success. Consider a toollike ouch [1] or fd instead of find. [1] https://crates.io/crates/ouch https://crates.io/crates/ouch
- nozzlegear 2y agoThe only tar command I can remember reliably is this one: tar -tf ./archive.tar It lists all of the files in the archive. I only remember it because of the mnemonic "tar the fuck is in this archive."
- mhitza 2y agojournalctl -fu some-service Also feels appropriate, because most of the time when I have to type in that command I'm thinking FU service file for not showing me by default why a service failed to start/restart.
- dmonitor 2y agoFor some reason regex just clicked for me very easily. Granted, I use regexr.com to check my work and tune it, but I find that the syntax just makes sense when I know what I want to find.