Where is vimrc in linux
The location of the vimrc file in Linux: 1. The global vimrc file is placed in the directory where Vim is installed. You can use the "echo $VIM" command to find the directory. The location is "/usr/share/vim/vimrc" ;2. The user version of the vimrc file is placed in the home directory, located at "/home/kim/.vimrc".
#The operating environment of this tutorial: linux7.3 system, Dell G3 computer.
Where is vimrc in Linux
vimrc
This is the main configuration file of Vim. It has two versions,
Global version (global)
User version (personal))
The global vimrc file is placed in your Vim installation directory. You can open vim and enter the following command in normal mode to find out the location of this directory
:echo $VIM
The result should be like this:
Linux: /usr/share/vim/vimrc Windows: c:\program files\vim\vimrc
Place the user version of vimrc file In your home directory. The location of your home directory depends on your operating system. Vim was originally provided for Unix and Unix-like operating systems, so user versions of vimrc files are created by adding a dot at the beginning of the file name. Set as a hidden file. This is a method of setting hidden files on Unix-like systems, but it does not apply to Microsoft Windows. Therefore, the vimrc file is related to the operating system. It should be like this:
Linux: /home/kim/.vimrc Windows: c:\documents and settings\kim\_vimrc
No matter how you change the user version of the vimrc file, the settings in which overwrite the contents set in the global vimrc file. This means that you do not need to change the global vimrc file to configure Vim.
You can configure Vim in Vim's Enter the following command in normal mode to find out where Vim thinks your system's home directory is:
:echo $HOME
The vimrc file contains ex (the predecessor of vi) commands, one command per line. And the vimrc file contains It is also the default way to add Vim configuration information.
Your vimrc can use other files (containing configuration information) as external resources. In the vimrc file, you can use the source command to achieve this:
source /path/to/external/file
This will keep your vimrc file clean and your settings will be more structured
Expand knowledge
gvimrc
The gvimrc file is a configuration file specially designed for Gvim. It is very similar to the vimrc file mentioned above, and is placed in the same directory (also divided into user version and global version), such as:
Linux: /home/kim/.gvimrc /usr/share/vim/gvimrc Windows: c:\documents and settings\kim\_gvimrc c:\program files\vim\
This file is used to set GUI settings that can only be used by Gvim.
exrc
This file is used for backward compatibility with vi or ex. It is also used with The vimrc file is placed in the same directory, and of course it is divided into user version and global version). However, unless you want to use Vim in vi-compatible mode, you will not use this file at all.
Recommended learning: Linux video tutorial
The above is the detailed content of Where is vimrc 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

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



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)

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

CentOS has been discontinued, alternatives include: 1. Rocky Linux (best compatibility); 2. AlmaLinux (compatible with CentOS); 3. Ubuntu Server (configuration required); 4. Red Hat Enterprise Linux (commercial version, paid license); 5. Oracle Linux (compatible with CentOS and RHEL). When migrating, considerations are: compatibility, availability, support, cost, and community support.

CentOS installation steps: Download the ISO image and burn bootable media; boot and select the installation source; select the language and keyboard layout; configure the network; partition the hard disk; set the system clock; create the root user; select the software package; start the installation; restart and boot from the hard disk after the installation is completed.

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.

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.

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)
