13 lines
1.4 KiB
Org Mode
13 lines
1.4 KiB
Org Mode
#+title: neogrep - The Recursive Line Checker That Sucks Less
|
|
#+author: Neo-Sekai Club
|
|
#+options: html-postamble:nil html-preable:nil toc:nil
|
|
|
|
It's cool to be able to grep your code to see where you may have made some sort of mistake, or when you're doing a debug or valgrind and go "Hey, this is like how many hundreds of lines of code! Where is this problematic function!?". If you're a psychopath, you pipe to grep. If you enjoy using garbage that eats your resources on compile-time, you use ripgrep. neogrep is the option that is meant to suck less and be far simpler.
|
|
|
|
Is it as robust as real grep? No, but it doesn't need to be. Does it fill the exact same needs as ripgrep? You bet it does. We managed to do this simple task in 115 lines of C code, with a more sane directory structure and build system. ripgrep spans across how many source files, but we narrowed neogrep down into just one. It doesn't need to do more, it needs to do what it's designed to do, and do that efficiently.
|
|
|
|
Due to neogrep's design, it's easily hackable if you are a C programmer yourself, allowing you (the end user) to add any features you may desire out of neogrep.
|
|
|
|
* Requirements
|
|
neogrep runs on any system that is POSIX compliant or allows for POSIX compliancy. We build neogrep with the intent that it will be used on everything that is a UNIX, UNIX-like, or Linux. This means that it does not run on Windows. Sorry, Wintoddlers.
|