As a non-programmer and software quality control personnel, the most common task in daily work is to conduct software quality testing. During software quality testing, you need to frequently set up a test environment, configure test tools, run test cases, and so on, therefore, in my work, it is inevitable to deal with a lot of shells. Therefore, the most frequently used mode in my Emacs career is the shell-mode of Emacs.
Of course, the programmer will also use shell in his work. However, it can be seen from a large number of articles on the Internet that many programmers either directly use terminal (including xterm, rxvt, etc.) to run shell, or use the term-mode of Emacs (including various variants, for example, ANSI-term, multi-term, and so on ). I prefer shell-mode. This is closely related to the nature of my work.
First of all, there will be a lot of shell work in software testing. A lot of work will inevitably require a time-saving and labor-saving way of work to improve work efficiency, including reducing or even eliminating mistakes. Secondly, there will be a large number of different testing machines in the software testing work. These machines not only bring a large number of different systems, different configurations, and a large number of different shell environments, at the same time, these many differences will continue to change as the work progresses. In these aspects, I think it may be the biggest difference between the working environment we face as software quality control personnel and programmers.
In such a large variety of different and frequently changing environments, we need to find or construct a common place that can be stable, or even form standardization, in order to truly improve efficiency, reduce errors. The shell-mode of GNU Emacs is an ideal tool to achieve this goal.