sejo
/
compudanzas
2
3
Fork 3
Code Issues Pull Requests Projects Releases Wiki Activity

updated cli output and uxnemu controls

This commit is contained in:
sejo 2021-11-16 19:55:31 -06:00
parent 6c9e4186d5
commit c82156bfe2
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
src/uxn_tutorial_day_1.gmo
View File

@ -206,6 +206,7 @@ if everything went alright, you'll see many messages in the terminal and a littl
* F1 circles between different zoom levels * F1 circles between different zoom levels
* F2 shows the on-screen debugger * F2 shows the on-screen debugger
* F3 takes a screenshot of the window * F3 takes a screenshot of the window
* F4 loads a boot.rom that lets you browse and open roms in the current directory
## using the toolchain ## using the toolchain
@ -275,8 +276,8 @@ $ ./bin/uxnasm hello.tal bin/hello.rom && ./bin/uxnemu bin/hello.rom
we will see an output that looks like the following: we will see an output that looks like the following:
``` ```
Assembled bin/hello.rom(5 bytes), 0 labels, 0 macros. Assembled bin/hello.rom in 0.00kb(0.40% used), 0 labels, 0 macros.
Loaded[bin/hello.rom]. Loaded hello.rom
h h
``` ```
@ -333,10 +334,11 @@ in uxntal we can only write numbers that are 2 or 4 hexadecimal digits long. if,
## assembled rom ## assembled rom
we can see that the assembler reported that our program is 5 bytes in size: we can see that the our assembled program is 5 bytes in size:
``` ```
Assembled bin/hello.rom(5 bytes), 0 labels, 0 macros. $ wc --bytes bin/hello.rom
5 bin/hello.rom
``` ```
for the curious (like you!), we could use a tool like hexdump to see its contents: for the curious (like you!), we could use a tool like hexdump to see its contents: