Ubuntu Desktop Survival Guide (5)-Introduction to commonly used efficiency software for Ubuntu

In the previous series of blogs about commonly used efficiency software in Ubuntu, we have consolidated the basic knowledge required to use the Ubuntu system. In this article, let's talk about this low-key and powerful platform, how to enable the operator to follow the design philosophy of the system and use appropriate software to achieve a human-computer integration environment, so as to bring the potential of this platform to the extreme, and then ten times more, times to improve the operator's production efficiency. Next, let's talk about the commonly used efficiency software in Ubuntu/Linux. On the internet, there are often Linux users learning and using this platform.

Ubuntu efficiency Software Overview

In a series of previous blogs, we have consolidated the basic knowledge required to use the Ubuntu system. In this article, let's talk about this low-key and powerful platform, how to enable the operator to follow the design philosophy of the system and use appropriate software to achieve a human-computer integration environment, so as to bring the potential of this platform to the extreme, and then ten times more, times to improve the operator's production efficiency. Next, let's talk about the commonly used efficiency software in Ubuntu/Linux. On the internet, Linux users are often learning. After using the software on this platform, they will sigh like this: "Almost every Linux software can be written into a book ". This is basically the best bet that Linux software is powerful to awesome. Therefore, it is impossible to cover all aspects of the software within a limited space. What's more, the author's own vision is limited. Therefore, the following text is only an introduction to outline and hope to inspire readers. This article first introduces common software. Considering the role of Linux as a developer system, we will introduce the software required by developers in the next article.

Related reading:

Ubuntu Desktop Survival Guide: Linux philosophy (1) (2) http://www.linuxidc.com/Linux/2012-10/73145.htm

Ubuntu Desktop Survival Guide (3) --- build Ubuntu system infrastructure http://www.linuxidc.com/Linux/2012-11/73450.htm

Ubuntu Desktop Survival Guide (4)-Ubuntu System Backup Recovery upgrade policy http://www.linuxidc.com/Linux/2012-12/75842p4.htm

In general, I will introduce each software as follows:

1. Software background

2. install and configure

3. Introduction and experiences

Editor: GVim

Vi/Vim is the default Standard editor software for Linux machines. Basically, I think you don't need any other software on Linux, but you can't say: "I want to learn Linux, but I don't want to learn Vi/Vim ". Vi/Vim has a high learning curve, but you must learn the following reasons:

1. Text System

Linux is a command-and text-based configuration system, not to mention the killer application of the god of the world's premium editor if you are a developer who needs to write code, in this unfriendly world of GUI, you are actually unable to do anything.

2. ubiquitous

If you use Linux, it means you will not feel at ease using your local desktop. Install the Vi/Vim alternative and pretend that you do not need to learn Vi/Vim, you are more likely to need to remotely log on to a strange environment to operate on another Linux, and 80% of that machine may only have the default Standard Vi/Vim. In this situation, anyone else will feel very uncomfortable, there are also work und: I see that many Windows developers use the ftp client to drag several G log files from a remote machine to the local machine, then, it takes several minutes to use the Windows Editor to load this huge file, which is not over yet. If the problem persists, the painful and laborious process will continue, repeat three times. At this time, I often wonder why they didn't spend the time learning Vi/Vim?

3. Efficient editing

As an editor, Vi/Vim has been developed so far. Combined with excellent plug-in mechanisms, its rich and powerful functions have exceeded the limits that humans can think. Before the appearance of the mouse, humans had to rely on the keyboard to operate computers, code words, especially how to efficiently code words are one of the most important operations, vi/Vim is a tool designed to efficiently use the keyboard code. Therefore, it is divided into three editing modes. In terms of details, it requires that all the key-hitting behaviors only occur in the primary key area: just to avoid the efficiency loss caused by the shift between several centimeters of hands. In order to compromise efficiency, it designs various anti-human operations to achieve various editing functions. In order to pursue Editing efficiency, it imposes operation costs and memory burden on humans. After the mouse appears, the codeword software that should only serve the keyboard is still highly accepted by programmers because of its efficient design. In fact, this phenomenon should allow us to reflect on what problems exist in the man-machine design of common users.

4. once and for all

Learning Vi/Vim is not learning Vi/Vim itself, but learning a set of specifications for using a keyboard to manipulate computers (for example, hjkl indicates upper left and lower right ), as this specification has been accepted by many people and has become a standard specification, it has been grafted to many other software such as Vimperator, w3m, Eclipse, even the dead enemy of GVim, Emacs. It can be seen that, as a standard of convention, the marginal benefits of learning Vi/Vim are considerable. As long as you learn this standard, you can learn it in many places-not just the editor itself, let's take advantage of the power of our learning achievements. We will see many such cases in the following text. Let's talk about a small example and input it in the terminal:

$ Set-o vi

You can enable the bash command with a shortcut key compatible with vi. In this case, you can use Esc on the terminal to switch to the command mode. In command mode, press h and l to move the cursor left and right, and press j, k can switch the previous command to the next one. X can modify the character, "$, ^" can return the end or header of the command, and I can return the editing mode.