head	1.1;
access;
symbols
	pkgsrc-2026Q2:1.1.0.42
	pkgsrc-2026Q2-base:1.1
	pkgsrc-2026Q1:1.1.0.40
	pkgsrc-2026Q1-base:1.1
	pkgsrc-2025Q4:1.1.0.38
	pkgsrc-2025Q4-base:1.1
	pkgsrc-2025Q3:1.1.0.36
	pkgsrc-2025Q3-base:1.1
	pkgsrc-2025Q2:1.1.0.34
	pkgsrc-2025Q2-base:1.1
	pkgsrc-2025Q1:1.1.0.32
	pkgsrc-2025Q1-base:1.1
	pkgsrc-2024Q4:1.1.0.30
	pkgsrc-2024Q4-base:1.1
	pkgsrc-2024Q3:1.1.0.28
	pkgsrc-2024Q3-base:1.1
	pkgsrc-2024Q2:1.1.0.26
	pkgsrc-2024Q2-base:1.1
	pkgsrc-2024Q1:1.1.0.24
	pkgsrc-2024Q1-base:1.1
	pkgsrc-2023Q4:1.1.0.22
	pkgsrc-2023Q4-base:1.1
	pkgsrc-2023Q3:1.1.0.20
	pkgsrc-2023Q3-base:1.1
	pkgsrc-2023Q2:1.1.0.18
	pkgsrc-2023Q2-base:1.1
	pkgsrc-2023Q1:1.1.0.16
	pkgsrc-2023Q1-base:1.1
	pkgsrc-2022Q4:1.1.0.14
	pkgsrc-2022Q4-base:1.1
	pkgsrc-2022Q3:1.1.0.12
	pkgsrc-2022Q3-base:1.1
	pkgsrc-2022Q2:1.1.0.10
	pkgsrc-2022Q2-base:1.1
	pkgsrc-2022Q1:1.1.0.8
	pkgsrc-2022Q1-base:1.1
	pkgsrc-2021Q4:1.1.0.6
	pkgsrc-2021Q4-base:1.1
	pkgsrc-2021Q3:1.1.0.4
	pkgsrc-2021Q3-base:1.1
	pkgsrc-2021Q2:1.1.0.2
	pkgsrc-2021Q2-base:1.1;
locks; strict;
comment	@# @;


1.1
date	2021.05.29.17.21.42;	author pin;	state Exp;
branches;
next	;
commitid	RMrRlJrMoLNve4VC;


desc
@@


1.1
log
@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.
@
text
@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.
@