


What are the methods of editing file commands in Linux?
This article is not only written for novices to learn, but also for me to learn Linux. When I write this article, I am also learning and understanding Keep these basic commands for future reference.
sed command to view/edit file content
Introduction parameters:
##-i: After the operation, the application is saved to the original file (if this parameter is not added, any modification will not affect the content of the original file, only the result will be output) -e: Only display the processed results# To be written...# More commands You can use sed --help to view it. use:
# View the content of line 3 of log.txtsed -n '3p' log.txt# View the contents of lines 2-8 of log.txtsed -n '2,8p' log.txt# Delete line 1 (first line) of log.txt sed -i '1d' log.txt# Delete log .txt Lines 3-7sed -i '3,7d' log.txt# Delete the last line of log.txt (Last line) sed -i '$d' log.txt# Delete all blank lines in log.txtsed -i '/^$/d' log.txt Delete the line starting with doubi in log.txtsed -i '/^doubi/'d log.txt Delete the line ending with doubi in log.txtsed -i '/doubi$/'d log.txt Delete all lines containing 233 content in the log.txt filesed -i '/233/d' log.txt# Delete the first 233 text in the log.txt file sed -i 's/233//' log.txt# Delete all 233 text in the log.txt file (g represents the text that operates all matching rules)sed -i 's/233//g' log.txt Delete all the fifth 233 text in the log.txt file (5g represents the Text of five matching rules)sed -i 's/233//5g' log.txt# Replace log.txt The first 233 in the file is 666##sed -i 's/233/666/' log.txt# replace log. All 233 in the txt file are 666 (g represents the text of all matching rules in the operation)sed -i 's/233/666/g' log.txt # Replace all /ver in the log.txt file with doubi/. Because there are slashes, you need to use \ to escape. However, single quotes will make it impossible to escape, so you need to change them to double quotes.sed -i "s/\/ver/doubi\//" log.txt# Display the log.txt file Odd or even linessed -n 'p;n' log.txt #Odd linessed -n 'n;p ' log.txt #Even numbered lines# You can use sed --help to view more commands.
##VI, VIM, Nano Edit file content
VI Introduction:
VI is a great text editor for Linux, but it also has some shortcomings, such as troublesome operation. . Vim is equivalent to an enhanced version of VI, mainly introducing VIM.
VIM Introduction
# Open the log.txt file in the current directory. If there is no log.txt file, a new log.txt file will be created (after installing vim, there is no difference between using vi and vim to open the file) vi log.txtvim log.txt# In command line mode, directly enter the following Symbols and letters (case sensitive)## Enter edit mode (insert mode, press Esc key to return to command line mode)i## Delete the line where the cursor is currently located dd## Delete All contents in the filedddG## Copy the line where the cursor is currently locatedyy ## Paste the line you just copiedp## Undo the previous one Operation (misoperation can be restored with this) u## Save the current file ( : is an English colon) :w## Save the current file content as log2.txt:w log2.txt## Exit the current file :q## Do not save and force exit the current file File:q!## Save and exit the current file:wq# You can use vi --help / vim --help to view more commands.
#Nano Introduction
Nano is more suitable for novices than VIM.
# Open the log.txt file in the current directory. If there is no log.txt file, a new log.txt file will be created. nano log.txt# After entering, you can directly enter and modify the text content. After modification, we can use this key to save the contentCtrl O# If you no longer need to edit, you can use this key to exit the current file Ctrl X If you If you have modified but not saved before exiting, you will be prompted whether to save. If you want to save, enter y. If not, enter n# and then you will be asked to enter the file name to be saved. (The default is the original file name, so just press Enter, unless you want to save as another file name) Enter# Update Many commands can be viewed by pressing the F1 key in the nano editing interface.
For more Linux-related technical articles, please visit the Linux Tutorial column to learn!
The above is the detailed content of What are the methods of editing file commands in Linux?. 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

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

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).

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).

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.

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 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)

VS Code is available on Mac. It has powerful extensions, Git integration, terminal and debugger, and also offers a wealth of setup options. However, for particularly large projects or highly professional development, VS Code may have performance or functional limitations.

VS Code is the full name Visual Studio Code, which is a free and open source cross-platform code editor and development environment developed by Microsoft. It supports a wide range of programming languages and provides syntax highlighting, code automatic completion, code snippets and smart prompts to improve development efficiency. Through a rich extension ecosystem, users can add extensions to specific needs and languages, such as debuggers, code formatting tools, and Git integrations. VS Code also includes an intuitive debugger that helps quickly find and resolve bugs in your code.

How to back up VS Code configurations and extensions? Manually backup the settings file: Copy the key JSON files (settings.json, keybindings.json, extensions.json) to a safe location. Take advantage of VS Code synchronization: enable synchronization with your GitHub account to automatically back up all relevant settings and extensions. Use third-party tools: Back up configurations with reliable tools and provide richer features such as version control and incremental backups.
