Skip to main content

Difference Between the clear Command in Linux and Mac

I've been writing a series of posts about CSI Sequences, but we rarely use CSI Sequences directly. However, there is a CSI Sequence that we use unknowingly. It's the clear command that clears the screen.

The clear command basically uses two types of CSI sequences. One is CSI H(Cursor Position, a.k.a CUP); it moves the cursor to the beginning of the screen. The cursor is at the top-left corner after the command ends, thanks to CUP. The second CSI Sequence is CSI 2 J(Erase in Display, a.k.a. ED), which is used to clear the entire screen. Linux and Mac use these two sequences; they behave the same way up to this point. However, Linux's clear and Mac's differ in their subsequent actions.

In a nutshell, Linux's clear clears the scrollback buffer, while Mac's does not. Linux's one prints CSI 3 J after the two sequences. CSI 3 J is an extension of the Escape Sequence introduced by xterm that removes lines stored in the scrollback buffer. Since being named E3 by the Red Hat community in 2011, terminal emulators usually call it the E3 extension. Mac's clear does not print this sequence, leaving the scrollback buffer untouched.

This difference is not as old as one might think. Originally, most terminal emulators did not understand xterm extensions, including the E3 extension. Naturally, the clear command used in Linux also did not use E3, so the scrollback buffer was not cleared. However, as time passed, xterm extensions gradually spread to other terminal emulators, and the E3 extension began to be implemented. From 2007's PuTTY, 2011's Red Hat, 2014's Gnome Terminal, and iTerm2, various terminal emulators started to support CSI 3 J, and today, most terminals support the E3 extension.

Another issue arose as most terminal emulators began to support the E3 extension. The question was how to define the behavior of the clear command. Opinions were divided between two groups of people. One group wanted the clear command to only clear the visible display, insisting that deleting the scrollback buffer is the task of the reset command, which literally resets the terminal. The other group believed that the scrolling area is also part of the screen, clear should delete the scrollback buffer as well. The latter won in the Linux community. Eventually, E3 was added to the clear command, and those who disliked this decision had to use the clear command with a -x option like clear -x.

However, this change has not yet been propagated to the Mac community. Therefore, Mac uses the program implemented before E3 was added. There isn't even an option to choose. It seems that there is no discussion related to this issue. So, if you want Linux-like clear behavior on Mac, you need to create an alias like alias clear='printf "\033[H\033[2J\033[3J"'. Conversely, if you want the original behavior on Linux, you must set an alias like alias clear=clear -x or alias clear='printf "\033[H\033[2J"'.

Labels:

Comments

Post a Comment

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...
Post a Comment
Read more

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 ...
Post a Comment
Read more

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.
Post a Comment
Read more