I think stdio calls (getC, putC) could need some documentation what userspace can expect from drivers and what not. Of course, it can always happen that a certain device cannot fulfill those expectations, but in that cases you at least know that you may have to update every userspace tool too, and not only make a glue.asm for the kernel.

Examples/Questions:

• What character set is every stdi

See #158 for context.

1. Game Boy Crib Sheet - A handy printable reference sheet with ASM opcodes, memory locations, and much more (repository).
2. OP Codes cheatsheet
3. [gb-opcodes](https://gbdev.g

elastic 의 timelion 이라는 도구에서는 위와 같이 line 그래프에 커서를 올리면 동일한 시간대에 다른 그래프에도 세로 줄이 생깁니다.
어떤 이슈가 발생했을 때 동일 시점에 다른 항목들이 어떤 상태인지를 쉽게 볼 수 있는 방법인 듯 해요.

기능 추가 검토 요청 드립니다. ^^;

Context

While trying to debug FabricMC/fabric-mixin-compile-extensions#1, I came across three things which don't appear right to me but I may just be missing the bigger picture for some of them.

Disclaimer

I was debugging using Fabric's Mixin fork and mapping provider. The respective sources code concerning the issues appears to be the same in fork and upstream

The machine the wiki is on:

• Is old and slow
• Costs @suborb money every month
• Only @suborb has access to

Steps to do this:

• Enable wiki on the GitHub project
• Run the migration script
• Upload the wiki
• Fix up any migration errors
• Move examples into examples directory in the main repo
• Provide a redirect script on z88dk.org so google links remain

Instructions are already highlighted and it would be nice if they contain tooltips with some description or/and be clickable with URL to some documentation.