Tropibyte Tropibyte CShW →
Tropibyte / C Shell for Windows / Report a bug
Alpha feedback

Found a bug? Tell us about it.

CShW is in alpha. Real-world reports are what shape what ships next. The more specific you can be, the faster we can fix it — and the more likely we’ll get back to you with a real answer.

What to include

The two questions that block almost every bug investigation are what version and what command. If you can answer both, you’ve already done most of our work for us. A good report has:

  • cshw version — run version at the prompt
  • Windows build — run ver at the prompt, or use Settings → System → About
  • The exact command you ran, copy-pasted (including any pipe, redirect, or quoting)
  • What you expected to happen
  • What actually happened — output, error message, hang, crash, weird behavior
  • Reproducible steps if it’s not obvious from the command itself

Quick diagnostic snippet

Paste this into cshw and include the output in your report:

version
ver
echo "PATH=$PATH"

That covers the “what version, what OS, what environment” baseline for 90% of reports.

For crashes

If cshw crashes outright, run it again from a Windows Terminal tab so the crash trace appears in the scrollback. Include the last few lines of output and the command that triggered it. If you have WerFault dump files in %LOCALAPPDATA%\CrashDumps\, mention that — we may ask for one.

Feature requests & questions

Not a bug? Email hello@tropibyte.com instead. We read everything, even when we can’t reply quickly.

Privacy

Bug reports are not shared, sold, or used to train anything. We only use them to fix the thing you’re reporting.