CKB-NEXT-DEV-DETECT(1)

πŸ’– CKB-NEXT-DEV-DETECT(1) πŸ’–

okay bestie, welcome to the General Commands Manual, section 1 β€” this is the page for ckb-next-dev-detect, and it's genuinely so useful, no cap.


✨ NAME ✨

ckb-next-dev-detect β€” the little tool that makes a ckb device summary for bug reports πŸ›πŸ“


🌸 SYNOPSIS 🌸

ckb-next-dev-detect [--nouserinput]

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the vibe: ckb-next-dev-detect puts together a whole report of your current platform β€” and it's thorough, like, it's giving main character energy. the report includes:

  • your kernel version
  • your qt version
  • your xdg version
  • journalctl output
  • the date

and where does all that go? it gets written out to ckb-next-dev-detect-report.gz in the current/working directory. periodt. πŸ’…

then you take that bug and that report and you submit them to https://github.com/ckb-next/ckb-next/issues 🫢 the devs literally need the report, so don't ghost them on it, okay?

πŸŽ€ OPTIONS πŸŽ€

  • --nouserinput β€” this one changes the output directory to /tmp instead of the current/working directory, and it also inhibits some messages to stdout. so like, quieter, and it dumps the file somewhere else. iconic. ✨

and that's the whole page, bestie!! πŸ’– this was CKB-NEXT-DEV-DETECT(1) from the General Commands Manual, and yeah the footer is literally just the same name again β€” it said CKB-NEXT-DEV-DETECT(1) down there too, so consider this your cute lil sign-off. mwah, go file that bug πŸŒˆπŸ‘‘πŸ’œ