Linux Command Line Editing – The editing possibilities are endless!
For Linux users, the command line editor is one of the essential tools. It can help you edit and process files quickly and improve work efficiency. However, for newbies, learning the command line editor can be somewhat difficult and challenging. Today, we will introduce several of the most popular and useful Linux command line editors to help you quickly master this skill.
If you are using Linux or BSD, you most likely have ed installed by default (the GNU version of ed on Linux, and the BSD version of ed on BSD). However, some minimalist environments may not include ed, and that's okay, your distribution's software repository will most likely have ed available for download. macOS comes with the BSD version of ed installed by default.

This deceptively simple editor provides users with many commands that are easy to learn and use.
The GNU ed command is a line editor. It is considered the standard Unix text editor because it was the first text editor to appear on Unix, and it was once so ubiquitous that you could find it on every POSIX system (generally speaking, you can now Can). In a way, you can easily tell that it was the first text editor because it was so basic in many aspects. Unlike most other text editors, it doesn't open a window or display area of its own. In fact, by default, it doesn't even prompt the user for text. On the other hand, its lack of interactivity can also be an advantage. It is a versatile editor that you can control with short commands, either interactively from the command line or from a shell script.
Install ed
If you are using Linux or BSD, you most likely have ed installed by default (the GNU version of ed on Linux, and the BSD version of ed on BSD). However, some minimalist environments may not include ed, and that's okay, your distribution's software repository will most likely have ed available for download. macOS comes with the BSD version of ed installed by default.
Start ed
When you start ed, your terminal prompt disappears, and it looks like ed has stopped running. Actually it doesn't, it's just waiting for your input.
$ ed
To make ed display more detailed information, you can enter the command p to have it return a prompt:
$ ed p ?
This question mark (?) is the default ed prompt.
Buffer
When ed is activated, you are actually dealing with something called a buffer buffer. A buffer is an area in memory. You're not editing the file directly, you're editing its corresponding buffer. When you exit ed without saving the changes to the file on disk, all changes will be lost because they only exist in the buffer. (This may sound familiar to experienced Emacs users who are used to the initial scratch buffer.)
Use ed to enter text
After starting ed, you are in command mode. This means you can give instructions to the editor, such as having it display a prompt instead of empty space. You can use the a command to start appending text to the current buffer, and use a solid dot . to terminate the input. For example, the following example appends two lines of text ("hello world" and "hello ed") to the buffer:
? a hello world hello ed .
Use dot . After terminating input, you will return to command mode.
View buffer
How to check what is in the current buffer? You can enter the line number you want to check, or you can use the ,p command to display all lines:
? 1 hello world 2 hello ed ,p hello world hello ed
Write to file
If you are now satisfied with the text, you can write the buffer to a file using the w command, followed by the target file name:
? w example.txt 19
The number displayed after the write operation represents the number of characters written to the file.
Read file
In addition to using ed to read text, you can also use the r command to load an existing file into the buffer:
? r myfile.txt
In addition, you can also add the file name you want to load into the buffer after it when starting ed:
$ ed myfile.txt
Edit Buffer
Given that ed is a text editor, you can of course use a special syntax to edit the text in the buffer. Users of sed or vim may find this syntax familiar. Assume that a file is already loaded in the buffer:
$ ed myfile.txt ,p This is an example document. There is some text, but not much. There is some errors, but not much.
If you want to change document in the first sentence to file, you can first select the target line (1), and then use the s command to call the search function, followed by the search text and replacement text:
? 1 This is an example document. s/document/file/ 1 This is an example file.
If you want to edit other lines, the steps are the same, just provide a different line number:
? 3 There is some errors, but not much. s/is/are/ s/much/many/
You can use the ,p command to see your historical editing records of the buffer:
This is an example file. There is some text, but not much. There are some errors, but not many.
Of course, these modifications only exist in the buffer. If you view this file outside of the ed editor, you will only see the original text:
$ cat myfile.txt This is an example document. There is some text, but not much. There is some errors, but not much.
如果你要把这些修改保存回文件中,使用 w 命令即可:
w myfile.txt 258
清空缓冲区
如果想要得到一个新的缓冲区,以此来打开一个新的文件,或者把一个新的文件加载到不同的环境中,你可以使用 c 命令。使用这个清空缓冲区后,什么也不会输出,因为缓冲已经是空的了:
c ,p
退出
如果要退出当前的 ed 会话,你可以使用 q 命令。它并不会给你一个保存缓冲区的机会,所以你要确保自己在这之前执行了保存操作。
尝试一下 ed 吧
ed 还可以做到很多事情,学习 ed 可以让你知道它和部分的 vim 是如何工作的。我并没有尝试使用 ed 来写这篇文章,老实说,我也不认为它是通常意义上的最佳文本编辑器。但是,ed 仍然是一个出色的编辑器。通过阅读它的文档,你可以很轻松地学会它。在 GNU 系统上,你可以使用 info ed 来查看它的操作手册。
总之,Linux 命令行编辑器是 Linux 用户必备的工具之一。在本文中,我们介绍了 Vim、Nano、Emacs 和 Ed 四种常用且优秀的命令行编辑器。每个编辑器都有其特色和用途,你可以根据自己的需求选择其中的一种或几种。希望这篇文章能够对你有所帮助,让你更加熟练地使用 Linux 命令行编辑器。
The above is the detailed content of Linux Command Line Editing – The editing possibilities are endless!. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



How to use Docker Desktop? Docker Desktop is a tool for running Docker containers on local machines. The steps to use include: 1. Install Docker Desktop; 2. Start Docker Desktop; 3. Create Docker image (using Dockerfile); 4. Build Docker image (using docker build); 5. Run Docker container (using docker run).

The key differences between CentOS and Ubuntu are: origin (CentOS originates from Red Hat, for enterprises; Ubuntu originates from Debian, for individuals), package management (CentOS uses yum, focusing on stability; Ubuntu uses apt, for high update frequency), support cycle (CentOS provides 10 years of support, Ubuntu provides 5 years of LTS support), community support (CentOS focuses on stability, Ubuntu provides a wide range of tutorials and documents), uses (CentOS is biased towards servers, Ubuntu is suitable for servers and desktops), other differences include installation simplicity (CentOS is thin)

Troubleshooting steps for failed Docker image build: Check Dockerfile syntax and dependency version. Check if the build context contains the required source code and dependencies. View the build log for error details. Use the --target option to build a hierarchical phase to identify failure points. Make sure to use the latest version of Docker engine. Build the image with --t [image-name]:debug mode to debug the problem. Check disk space and make sure it is sufficient. Disable SELinux to prevent interference with the build process. Ask community platforms for help, provide Dockerfiles and build log descriptions for more specific suggestions.

Docker process viewing method: 1. Docker CLI command: docker ps; 2. Systemd CLI command: systemctl status docker; 3. Docker Compose CLI command: docker-compose ps; 4. Process Explorer (Windows); 5. /proc directory (Linux).

Docker uses Linux kernel features to provide an efficient and isolated application running environment. Its working principle is as follows: 1. The mirror is used as a read-only template, which contains everything you need to run the application; 2. The Union File System (UnionFS) stacks multiple file systems, only storing the differences, saving space and speeding up; 3. The daemon manages the mirrors and containers, and the client uses them for interaction; 4. Namespaces and cgroups implement container isolation and resource limitations; 5. Multiple network modes support container interconnection. Only by understanding these core concepts can you better utilize Docker.

VS Code system requirements: Operating system: Windows 10 and above, macOS 10.12 and above, Linux distribution processor: minimum 1.6 GHz, recommended 2.0 GHz and above memory: minimum 512 MB, recommended 4 GB and above storage space: minimum 250 MB, recommended 1 GB and above other requirements: stable network connection, Xorg/Wayland (Linux)

The reasons for the installation of VS Code extensions may be: network instability, insufficient permissions, system compatibility issues, VS Code version is too old, antivirus software or firewall interference. By checking network connections, permissions, log files, updating VS Code, disabling security software, and restarting VS Code or computers, you can gradually troubleshoot and resolve issues.

VS Code To switch Chinese mode: Open the settings interface (Windows/Linux: Ctrl, macOS: Cmd,) Search for "Editor: Language" settings Select "Chinese" in the drop-down menu Save settings and restart VS Code
