terminal-life is run by one editor. The best way to reach them is email:
There's no contact form, no account, and no mailing list. Your address is only used to reply to you.
Good reasons to write
- A command didn't work. Something failed when you pasted it, behaved differently on your system, or a flag no longer exists.
- A correction. A fact, version number, install line, or explanation is wrong or out of date.
- A tool or trick worth covering. Something you use every day that deserves a proper write-up. Say what it replaces and why you keep it.
- A guide request. A workflow you'd like explained end to end.
- Anything about the site itself. Broken links, pages that don't render properly, accessibility problems, or privacy questions.
How to report a problem so it can be fixed fast
Please include:
- The page URL.
- The exact command you ran.
- Your operating system and version (e.g. Ubuntu 24.04, Fedora 41, macOS 15), plus your shell.
- The tool version (
toolname --version). - What you expected, and the output or error you got. Copy and paste the text rather than sending a screenshot if you can.
Corrections policy
- Every report is read.
- If a problem is confirmed, the page is fixed and gets an "Updated" date with a short note on what changed.
- If a command turns out to be dangerous (for example, it can delete or overwrite data in a way the page didn't warn about), the page is corrected or taken down first, and the details are filled in afterwards.
- If something can't be reproduced, you'll get a reply asking for more detail rather than silence.
Response time
Replies usually arrive within a few days. This is a one-person site, so complex questions may take longer. Please don't send personal support requests for production systems. The site can't offer consulting or emergency help.
What not to send
- Passwords, private keys, API tokens, or other secrets. If you're sharing output, redact them first.
- Sponsored-post or link-placement offers. The site doesn't accept them.