Skip to main content

Clear Screen with CSI Sequence

Today, following my previous post, I will explain how to clear the screen using CSI Sequences. There are two sequences in the CSI Sequence for clearing.

The first one is the Erase in Line sequence, called EL. It is composed of CSI # K; it is used to erase lines, as the name suggests. If the # is not provided, the default value is 0, and if a value is provided, it must be one of the three: 0, 1, or 2. The terminal will ignore the sequence if any other value is provided. For example, if you print 0x311b5b334b32(or 1^[3K2), the terminal ignores ^[3K, and the screen displays only 12. The behavior of 0, 1, and 2 can be summarized as follows.

Erases from the cursor to the end of the line.
Erases from the beginning of the line to the cursor.
Erases the entire line, regardless of the cursor's position.

Remember that the EL sequence does not move the cursor's position. Therefore, if you want to erase the current line and write a new line on the current line, you should use the EL sequence together with a carriage return (\r).

The second is the Erase in Display sequence, called ED. It is composed of CSI # J and is used to erase the screen. Like EL, the area of the screen to be erased is determined by the value of #.

Erases from the cursor to the end of the screen.
Erases from the beginning of the screen to the cursor.
Erases the entire screen, regardless of the cursor's position.
Erases the lines stored in the scroll buffer.

As you see, it is the same as EL. The default value is 0, not moving the cursor's position, and ignoring values other than the defined values. The only difference is the number 3, which is not defined in EL.

This sequence is used to erase the values stored in the scrollback buffer. It had not existed in the VT100 specification. At that time, terminals did not have the concept of scrolling. This sequence was added after the appearance of the xterm terminal emulator, which came with the X Window System. So, in the past, many terminal emulators did not support it, but nowadays most environments support CSI 3 J without any problems.

ED and EL are rarely used directly unless you are a fan of a TUI. It is because these sequences are fundamentally for controlling the terminal, and the purpose of most programs we write is not to control the terminal. However, we use ED every day without realizing it. In the next post, we will take a closer look at this topic.


Popular posts from this blog

Type Conversion in Rust

Type conversion is not special in Rust. It's just a function that takes ownership of the value and returns the other type. So you can name convert functions anything. However, it's a convention to use as_ , to_ , and into_ prefixed name or to use from_ prefixed constructor. From You can create any function for type conversion. However, if you want to provide generic interfaces, you'd better implement the From trait. For instance, you should implement From<X> for Y when you want the interface that converts the X type value to the Y type value. The From trait have an associated function named from . You can call this function like From::from(x) . You also can call it like Y::from(x) if the compiler cannot infer the type of the destination type. Into From have an associated function, it makes you be able to specify the destination type. It's why From has an associated function instead of a method, but on the other hands, you cannot use it as a me

Do not use garbage collection to catch memory leak

Garbage collection is a technique that automatically releases unnecessary memory. It's very famous because many programming languages adopted garbage collection after John McCarthy implemented it in Lisp. However, there are a few people who misunderstand what garbage collection does. If you think garbage collection prevents a memory leak, unfortunately, you are one of them. Garbage collection cannot prevent a memory leak. There is no way to avoid all memory leaks if you are using Turing-complete language. To understand it you should know what a memory leak is. Wikipedia describes a memory leak as the following: a type of resource leak that occurs when a computer program incorrectly manages memory allocations in such a way that memory which is no longer needed is not released. Briefly, a memory leak is a bug that doesn't release a memory that you don't use. So it is first to find the memory which will not be used in order to detect memory leaks. Unfortunately, it i

[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