Skip to main content

Understanding Escape Codes and Control Sequences

The exact term of escape code defined in ISO 6429 is a control function. Escape code is commonly used to refer to the code or sequence that represents control functions. Control codes defined by ISO 6429 are divided into two categories; C0 codes and C1 codes.

C0 codes correspond to non-printing characters in ASCII. These codes are familiar to developers. It includes line feed (\n), carriage return (\r), tab (\t), and null character (\0).

There are 32 codes in C1. They are represented by one-byte values between 0x80 and 0x9F. Unlike C0 codes, C1 codes are not defined in ASCII. They can only be used in terminals that support ASCII. In other words, they are available in 7-bit environments. In modern 8-bit environments, C1 codes cannot be used directly and must be expressed as escape sequences. Therefore, most modern terminals use escape sequences to represent C1 codes when needed.

An escape sequence is a series of characters that begins with ESC (0x1B). Sequences that correspond to C1 codes consist of a first byte of ESC (0x1B) and a second byte from @ (0x40) to _ (0x5F). For example, in a 7-bit environment, IND is represented by 0x84, but in an 8-bit environment, it is represented by ESC D (0x1B 0x44). This second byte is called the "Final character of Escape sequence," or "Fe," and two-byte C1 codes are also referred to as "Fe sequences."

In addition to Fe sequences, ISO 6429 defines other escape sequences. For example, values between `(0x60) and ~(0x7E) are called "Fs," and sequences of ESC and Fs are called "Fs sequences." Unlike C1 codes, Fs sequences are always expressed as escape sequences, regardless of the environment; they are called "independent control functions."

Fe sequences and Fs sequences mostly provide commands for controlling terminal devices. As a result, they are rarely used in modern terminal emulators. Instead, control sequences that begin with CSI (Control Sequence Introducer) are mainly used.

CSI is a value defined in the C1 control code. In a 7-bit environment, it is represented by 0x9B; in an 8-bit environment, CSI is represented by ESC [ (0x1B 0x5B). A series of sequences from CSI to byte between @ (0x40) and ~ (0x7E) are called "control sequences," and they can adjust various aspects of terminals, such as font, color, and cursor position. We will discuss this in more detail in the next article.


Popular posts from this blog

[C++] Handling Exceptions in Constructors

When you use RAII idiom, there are often situations where constructors have to do complex tasks. These complex tasks can sometimes fail, resulting in throwing exceptions. This raises a concern: Is it okay to throw exceptions in constructors? The first concern is memory leaks. Fortunately, memory leaks do not occur. Variables created on the stack are released through stack unwinding, and if an exception occurs during heap allocation with the new operator, the new operator automatically deallocates the memory and returns nullptr . The next concern is whether the destructor of the member variables will be called correctly. However, this is also not a problem. When an exception occurs, member variables can be divided into three categories: fully initialized member variables, member variables being initialized, and uninitialized member variables. Fully initialized member variables have had their constructors called and memory allocations completed successfully. In the example code, t

Iterator Adapters in Rust

An Iterator that takes another iterator and returns a new one is called an iterator adapter . The name "adapter" comes from one of the GoF's design patterns, the adapter pattern . However, in reality, it corresponds more to the decorator pattern , so if you pay too much attention to the name, you might get confused about its purpose. So it's better not to worry too much about the name. Enough complaining about the name, what does an iterator adapter do? An iterator adapter adds a task to be performed when the iterator iterates. This will be easier to understand when you see an example. The map function is one of the famous adapters. The iterator returned by the map function for those who have used functional languages iterates over new values transformed from the original values. Besides, various adapters are already implemented in the standard library. Among them, the most frequently used are those that are convenient to use with loops. Examples include the

What is the size of an empty object?

Consider a class like the one above. Commonly called an "empty class," this class has no internal variables. So, how big is this empty class? At first glance, the size should be 0 since there are no member variables. However, the size is never 0 in any language, whether Java, C#, C (in this case, a struct), or C++. This is to ensure that two different objects never have the same address. Empty classes typically have a size of 1 byte in a 32-bit environment and 2 bytes in a 64-bit environment. However, the exact size cannot be determined. According to the specification, the size just needs to be non-zero. The precise size depends on the implementation. This is a translation of my old Korean post written in 2015. Because the size can vary depending on the implementation, it is now possible to have different sizes (although still not 0). And Languages like Rust have even introduced zero-sized types . We will look at this topic in more detail at a future opportunity.