Skip to content

Added documentation for the fill command in debugger#380

Merged
indigodarkwolf merged 1 commit into
X16Community:masterfrom
JimmyDansbo:debug_fill_doc
Mar 6, 2026
Merged

Added documentation for the fill command in debugger#380
indigodarkwolf merged 1 commit into
X16Community:masterfrom
JimmyDansbo:debug_fill_doc

Conversation

@JimmyDansbo
Copy link
Copy Markdown
Contributor

I have been unable to find documentation for the fill command in the emulator debugger, but I have tested it and tried to document the functionality.

@stople
Copy link
Copy Markdown
Contributor

stople commented Feb 6, 2026

I was looking for the same thing just now. Thumbs up!

By the way, I also took this a step further, trying to modify this function to allow manipulation of IO and ROM, see #382 .

Comment thread README.md
|d %x|Change the code panel to view disassembly starting from the address %x.|
|m %x|Change the data panel to view memory starting from the address %x.|
|v %x|Display VERA RAM (VRAM) starting from address %x.|
|f %x %v [%n]|Fill memory address %x with value %v, optionally for %n number of bytes. In banked memory, the bank currently being displayed in the data panel is used, otherwise bank 0
Copy link
Copy Markdown
Contributor

@stople stople Feb 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is also an additional, optional "incr/step" parameter, specifying how much the address should increment between each consecutive write. Default is 1, as for the N number of bytes.

By the way, is there a reason for using " " instead of " " here?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I is to ensure it does not create a linebreak

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Working with HTML, I have seen the code   used before (without properly understanding its purpose until reading up on the topic now). It makes perfect sense to add a nbsp character, although the source code may become less readable.

I am not sure what is used elsewhere in the documentation (if it is used at all). But, could the code   instead of   perhaps give the reader of the source code some better insight what this is, compared to a magic number?

At least now I know this is intentional, and that it serves a particular purpose. Always nice to learn something new!

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know that we have a standard here, and I don't have strong feelings going either way, so I'm inclined to approve this as-is. If someone with a vested interest wants to hold a conversation or contradict me, feel free to do so. Heck, I'll even volunteer to swap the characters here myself, if necessary.

@indigodarkwolf indigodarkwolf merged commit e4ace9b into X16Community:master Mar 6, 2026
8 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants