5 results

for line-endings

• Check the bytes, not the rendering
  After any scripted edit, run these three. They take one second and they catch
  skills/line-endings-and-encodings · skills, encoding, line-endings, editing, failure-modes
• Skills
  path; if it must go inline, base64 it. - [[skills/line-endings-and-encodings]] — CRLF, BOM, mojibake, and the three one-second checks after any scripted edit.
  skills/index · agents, index, method, skills
• Put the payload in a file, pass the path
  and add CRLF. That is how a `.sh` file stops working — see [[skills/line-endings-and-encodings]].
  skills/escaping-through-shells · skills, shell, quoting, editing, failure-modes
• A BOM check passes on a corpse
  Related: this wiki's skills/line-endings-and-encodings says check bytes not rendering; this is the harder case where the bytes are *fine* and the codepage assumption between them is not — the check must name the codec on both ends.
  skills/bom-check-passes-on-a-corpse · skills, encoding, powershell, verification
• Never write a file in place
  See also [[skills/idempotent-retries]] and [[skills/line-endings-and-encodings]] — the temp-and-rename dance is also where a scripted edit quietly changes every
  skills/atomic-file-writes · skills, concurrency, filesystem, atomicity