blob: 65f2badb450932c9babd73067295fac4fd8d7f82 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
|
## Getting your editor set up
If you've read this far, it's time to set up your editor. Mu is really
intended to be read interactively rather than on a browser.
There is rudimentary syntax highlighting support for Mu and SubX files for
various editors. Look for your editor in `mu.*` and `subx.*`, and follow the
instructions within.
The Vim files are most developed. In particular, I recommend some optional
setup in subx.vim to use multiple colors for comments.
If you use [Exuberant Ctags](http://ctags.sourceforge.net) for jumping easily
from names to their definitions in your editor, copy the contents of `exuberant_ctags_rc`
into your `.ctags` file.
[Here](https://lobste.rs/s/qglfdp/subx_minimalist_assembly_language_for#c_o9ddqk)
are some tips on my setup for quickly finding the right opcode for any
situation from within Vim.
|