Contact

Questions, bug reports or suggestions are always welcome.

Write to hello@shelltrainer.com. One person reads that inbox, so please keep it to the topics below and you'll get a real answer.

What's most useful to report

• Simulator differences. If a command behaves differently here than in a real shell, that's a bug worth fixing — the whole point is that what you learn transfers.
• Confusing lessons. If an exercise is unclear, ambiguous or harder than the ones around it, say which number. The course is meant to be followable without outside help.
• Missing commands. The reference covers the commands people actually type, and the list grows based on what readers ask for.
• Errors in the book. Corrections ship free to everyone who bought it, so a typo you report today reaches every reader.

What we can't help with

We can't debug your specific server or fix a broken production system — for that, the right places are your distribution's forums, Unix & Linux Stack Exchange, or the manual page for the command in question (man command). What we can do is make the explanation of that command clearer for the next person, so tell us which one tripped you up.

Response time

This is a small project run by one person, so replies take a few days. Bug reports about the simulator get priority, because they affect everyone using the course.