Solve the dang cygwin windows newline problem, everywhere

[earthbound19]

UPDATE: stop using any gnu utilities ports that create windows newlines (such as those that come with cygwin), and use only ones that don't (such as from MSYS2).

items in this problem:

• [ ] standardize array creation via find command (applies to many scripts, underway); a previous way that may appear in some scripts is: find . -name '*.svg' | sed 's|^./||' > all_svgs.txt. Do instead something like: array=( $(find . -maxdepth 1 -type f -iname \*.png -printf '%f\n') )
• [x] consistentize sed usage in scripts (stop using gsed). see comments in installUsedBrewPackages.sh
• [x] Find gnu ported utilities for windows that don't destroy variables by adding windows newlines which confuse assigning results to a variable. Cygwin tools do this apparently randomly, and it is UNACCEPTABLE. It has caused so many hours of troubleshooting, repeatedly, before I go "OH, DUH! CHECK THE STUPID CYGWIN PROBLEM!" ~ Meanwhile (/OR?), a workaround:
• [x] ~In every script that needs it, and as standard practice, implement: the following tr -d command eliminates a maddening problem of gsed (et al) returning windows-style line endings, which muck up echo and varaible concatenation commands so that elements after one varaible with a bad line ending disappear; RE: https://stackoverflow.com/a/16768848/1397555~ ~ secondOfPair=gsed "$sedCommand" numberedCopies.txt | tr -d '\15\32' ~ Uh, better yet, pipe to tr -d .. when the text file is created.

Case with find vs. gfind: https://serverfault.com/a/354407/121188

[earthbound19]

For the umpteenth time I've discovered that sed / gsed (EDIT: but what about the cygwin version?) on windows inserts #@$! windows newlines, and that any stream-created variables with that must append this--as it says in this issue:

| tr -d '\15\32'

(removes windows newline)

[earthbound19]

python strings passed via argsparse are mucky on windows. solved with stringVariable.rstrip() re a genius breath yonder

[earthbound19]

Investigate whether msys2 tools don't cause CRLF (control linefeed / windows newline) problems?

OR per updated issue note (first sentence).

[earthbound19]

the sed.exe that ships with MSYS2 does not cause this issue. It's 100% an issue with Cygwin's sed.exe. Witnessed in fixing a bug manifest on Windows in hexplt2ppm.sh (it produced wrong colors via Gygwin sed.exe (hax renamed to gsed.exe by me), and did not produce the issue with MSYS2 sed.exe (hax renamed to gsed.exe by me).

Dumping Cygwin sed. DELETE the blankety-blank file after install unless/until migration to MSYS2 toolchain.

[earthbound19]

Updated OP with checklist and progress of checklist.

[earthbound19]

But this may be a more efficient way to remove windows newlines if you must; test before using:

re: https://stackoverflow.com/a/19347380/1397555 variable=${variable//[$'\t\r\n']}

[earthbound19]

^ THAT!