Usage of GNU Emacs by non-programmers ...... Shell mode 2nd set forward

Why is Shell-mode a good tool for dealing with such complex environments? Let's take a look at the problems in Shell in this environment, and then let's take a look at how Emacs's shell-mode solves these troubles.

 

The first is Shell personalization. Or a configuration problem. Let's just put it this way. Few of them come here in Cu, but they don't change any profile, so they just went naked in shell all day long. Seemingly simple personalized configuration is very troublesome in this complex environment. Obviously, it is impossible for every machine and user to customize a set of personalized and complete profile configurations. Moreover, as tasks change, a large number of non-counting profiles need to be modified, maintained, and transferred between different machines, the relationship with the owner is constantly changing. Think about these changes. Even during normal use, I mean between changes, most of the time, Unix/Linux machines are usually shared by many people. Unlike the development environment, users of these shared machines usually share the same account, especially the root account. Therefore, it is impossible to modify the profile of a shared account in many cases.

So how can we solve this problem? If we give up modifying the nasty profile, isn't that a problem? Let them run naked with a large number of shells, but put an Emacs coat on them and put all the modifications in Emacs. In this way, the original problem is not a problem. Haha, one-time solution .... Go to call. Next time we will talk about how to solve the problem.