Next | Query returned 5 messages, browsing 1 to 10 | previous

History of commit frequency

CVS Commit History:


   2021-10-07 17:02:49 by Nia Alarie | Files touched by this commit (1162)
Log message:
textproc: Remove SHA1 hashes for distfiles
   2021-08-03 10:58:42 by pin | Files touched by this commit (1)
Log message:
textproc/molybdenum: simplify Makefile
   2021-06-11 22:33:13 by pin | Files touched by this commit (2) | Package updated
Log message:
textproc/molybdenum: update to 0.1.5

-Added support for folder output via -L.
   2021-06-02 19:19:02 by pin | Files touched by this commit (3) | Package updated
Log message:
textproc/molybdenum: update to 0.1.4

-Removed warnings and dead code.
-Add support for searching hidden and ignored files.
   2021-05-29 19:21:42 by pin | Files touched by this commit (5)
Log message:
textproc/molybdenum: import package

Recursive _search and replace_ CLI application.

Powerful search can be found without problems, eg, grep, ack, ag, ripgrep
or broot.

Tools for replacing recursively in a folder are more difficult to find,
although some exist: fart-it. Typically, people use a combination of searching,
xargs and a replacement tool like sed or rpl.

I use code searching a lot to investigate a large source code base before
attempting a replace. Even with 100k files, search is fast and fairly easy.
Recursively replacing text is much more dangerous, especially if it requires
the combination of several less frequently used tools; it's difficult to
remember a search-xargs-replace combination if not used on a daily basis.
On top of this, the search tool used to filter the set of files and perform a
dry-run, is not per-se using the same search query as the replace tool.
After all, these are different tools. It would be better if a single tool could
be used for every-day searching and replacing.
This is exactly what The Molybdenum Replacer intends to achieve.

Next | Query returned 5 messages, browsing 1 to 10 | previous