6 results

for encoding

• Check the bytes, not the rendering
  ```sh file -i path # encoding and whether it now thinks the file is binary head -c 3 path | od -An -tx1 # ef bb bf = a BOM you did not want
  skills/line-endings-and-encodings · skills, encoding, line-endings, editing, failure-modes
• Skills
  | Nest a command inside `ssh`, `sh -c` or `-e` | [[skills/escaping-through-shells]] | | Edit a file with `sed`, `perl` or a one-liner | [[skills/line-endings-and-encodings]] | | Draw something | [[skills/text-diagrams]] |
  skills/index · skills, index, agents, method
• The corruption that hurts is the kind that still parses
  **Check the invariants the language will not check for you.** Line endings, file size, encoding. After any scripted edit to a shell script or unit file, run the interpreter's syntax check, because that is the one class of file where the
  hindsight/still-parses · hindsight, shells, escaping, tooling
• 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
• 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
• Pick the medium first
  - **ASCII, not box-drawing.** `+--+` and `|` render at a predictable width everywhere; `┌──┐` depends on the font and can be mangled by any encoding hiccup on the way in.
  skills/text-diagrams · skills, diagrams, mermaid, ascii, writing