xaderfos / uxntal-mode Goto Github PK

The roms are now created under /tmp on Linux/OSX (no support for Windows is in my plans currently).

We should be able to export the roms either in the same dir as the .tal file or to a custom path on the filesystem. Variable names: uxntal-local-export (boolean - export in the same dir as the .tal file), uxntal-export-path (string - export to the provided path).

Acceptance criteria:

• without any config uxntal-mode exports the rom to /tmp with a filename of {buffer-name}.rom
• if uxntal-local-export == t export in the same dir as the .tal file
• if uxntal-export-path != nil export to the specified path
• pressidence of config should be: uxntal-export-path > uxntal-local-export > default (no config)

I've noticed the following changes occur in other buffers after loading a .tal file with uxntal-mode

1. Commenting with M-; uses parenthesis on one or both sides (depending on the mode)
2. Pressing return auto indents

I've noticed 1 in python mode + text mode, and 2 in text mode only, but I assume it occurs in every mode where there isn't a mode specific override.

The original assembler for Uxntal is Uxnasm but in the meantime at least one new assembler has emerged: ruxnasm.

We would like uxntam-node to be able to use any of the available assemblers. The default assembler will be Uxnasm and through the configuration we should be able to choose alternative ones.

• The variable for this option can be named uxntal-assembler
• The value for this option must be the name of the assembler's executable
• The executable needs to be available on the PATH and/or exec-path

Acceptance criteria:

• if not otherwise specified uxntal-eval-buffer should use uxnasm
• if uxntal-assembler is defined in the configuration uxntal-eval-buffer should use that assembler instead
• update documentation

Currently execution is not tied to the assemble step so if there is a previous rom assembled the application will launch even if it failed to compile which may lead to misunderstandings. Change this behaviour so that the user is aware of the issue.

Acceptance criteria:

• If the assembler fails the rom should not be launched

For now this purely related to ruxnasm. It's output looks like garbage without support for color codes.
Adding this kind of support is not trivial but it looks doable. Some solutions seem to encode the buffer once the process has finished but that should be avoided. Ideally we need a buffer set up with color codes support out of the box to which we append the output of the assemblers and the emulator.

TODO Refine this issue

Provide users with variables to customise each highlight group. I'm not sure how that works and what one can use instead of the font-lock variables.

TODO: do some research on this and refine ticket

Figure out how to do this...

At the moment eval-buffer runs the assembler against the file on disk, any unsaved changes are not included.

Ideally we should either be able to pipe the buffer to stdin or at least create a tmp file to store the modified buffer and pass that to the assembler.

Acceptance criteria:

• uxntal-eval-buffer evaluates the contents of the buffer and not the contents of the file on disk