| ▲ | jawns 5 hours ago | |||||||
I would love for someone to package up some kind of script or AI skill that evaluates your current terminal config/set-up and applies all of these tips and tricks. For instance, it might detect that you currently use ag, install ripgrep, and offer a short tutorial on how users accustomed to ag should use it. Or it might look at the history of git commands you've run and offer tips on efficiency improvements. | ||||||||
| ▲ | kccqzy 5 hours ago | parent | next [-] | |||||||
Going from ag to ripgrep is not unequivocally better. Sure ripgrep is faster, but its file filtering using -g is so much more cumbersome than -G in ag. The latter uses a regex and the former uses glob. I type many more characters to do the same search, and the same search is maybe 0.1s faster for a medium codebase. So no for me. Maybe it’s worth it for a larger codebase that isn’t large enough to require indexing. | ||||||||
| ||||||||
| ▲ | farrellm23 5 hours ago | parent | prev | next [-] | |||||||
I doubt you need a full script or skill for that. I would try something like this straight in Claude Code (and will as soon as my 5 hour quota resets :-): Review this page: https://will-keleher.com/posts/small-programming-tricks-matt... Then, review my shell init scripts (both bash and fish) and shell history. Make recommendations based on the tips and tricks from the page. | ||||||||
| ▲ | popzxc 5 hours ago | parent | prev [-] | |||||||
I think it's a great way to stop understanding what's going on in your terminal. IMHO the value of these nuggets is that you understand what you're doing and why; opening yourself to large amounts of non-default behavior likely will end up in a less than pleasant setup. Not taking into account that different users might disagree on what is convenient and what is not, which is basically the point of making things configurable. | ||||||||