Acorn Atom escape codes

Every escape that can be typed in Atom source, and the byte it stores. The Atom stores lines as near-plain ASCII, so {0xNN} escapes are recognised everywhere in a line; a {...} that is not an escape is literal text. There is no %c inverse prefix because %A-%Z name the floating-point ROM's variables. Filters can be prefilled with ?q= and ?cat= query parameters.

See also the Atom BASIC reference and file formats.

		Description
{0xNN}	any	Any raw byte as two hex digits - the control codes 0x00–0x1F and delete (0x7F). The Atom stores source as near-plain ASCII, so escapes are recognised everywhere in a line; a {...} that is not an escape is literal text.
{0x80}…{0x9F}	0x80–0x9F	Inverse video digits and punctuation: byte 0x80+c displays character 0x20+c reversed ({0x81} is an inverse !). These have no unicode form of their own, so they stay escapes. There is no %c prefix - on the floating-point ROM %A–%Z name the FP variables, so % stays a literal character. Inverse capitals are not escapes at all: they are the lower-case letters 0x60–0x7E, which the machine displays reversed because it has no lower case.
{0xA0}	0xA0	The blank Semigraphics 6 cell (all six blocks off) - escaped because its glyph would be indistinguishable from a space. The other graphics bytes 0xA1–0xDF are typed as their unicode sextant glyphs (🬀…█), not escapes: PRINTing byte 0xA0+p draws pattern p, and the GRAPHICS palette on the on-screen keyboard inserts them.
{0xE0}…{0xFF}	0xE0–0xFF	The second colour set: these draw the same 32 shapes as 0xC0–0xDF, in the other MC6847 colour pair. Editor text carries shape but not colour, and one glyph cannot stand for two different bytes, so these keep their escapes - a program using them still exports and re-imports exactly.

Showing 4 of 4 escape codes