APress Pro Vim：深度探索Vim配置与高级技巧指南

需积分: 10 153 浏览量更新于2024-07-22 收藏 8.33MB PDF 举报

"APress Pro Vim"是一本专注于Vim编辑器的详尽指南，适合那些希望深入理解和提升Vim使用技能的专业人士。这本书将Vim的基本概念、安装与配置、核心功能直至高级特性逐一剖析，为读者提供了一个全面的学习路径。在本书的开篇，"Vim Primer"章节作为入门导引，旨在让初学者快速熟悉Vim的基本操作和工作模式，如命令行界面、文本编辑基础等。随后的章节逐步推进，包括如何安装和配置Vim以适应个人偏好，确保用户能够在不同的环境中无缝使用。 "Fundamentals"章节涵盖了Vim的基础操作，如查找与替换、光标移动、复制粘贴等，这些都是高效编程的基石。"Files"章节则探讨了如何管理文件和目录，这对于在大型项目中保持组织至关重要。 "Commands"和"Registers"章节详细解释了Vim的强大命令集和工作区存储机制，这对于编写复杂脚本和进行文件操作非常有用。接下来的"Folding"部分介绍代码折叠功能，有助于提高代码阅读和维护的效率。进入"VISUAL-BLOCK Mode"，读者将学习如何在Vim中实现多行和区块选择，这是处理代码块时必不可少的能力。"Bulk Command Processing"章节探讨批量操作，进一步提升工作效率。"Editing Workflow"章节则关注如何优化工作流程，确保用户能够高效地完成任务。 "Search and Replace"章节专门讲述搜索和替换功能，包括正则表达式和高级搜索策略。"Buffer/Window/Tab Management"部分则帮助读者理解Vim的窗口和标签页系统，这对于多任务处理和代码比较很有帮助。 "Automation"章节介绍自动化工具，如宏和脚本编写，以减少重复性劳动。"Lists"和"Marks"章节涉及列表处理和标记定位，对于处理数据和定位重要位置极其关键。 "Sessions"功能的讲解有助于保存和恢复工作状态，而"Plug-ins"章节则展示了如何利用丰富的Vim插件来扩展其功能。"Diffing"章节教你如何进行文件对比，对于代码审查和版本控制非常重要。 "Custom Commands and Bindings"允许用户自定义Vim的快捷键和命令，提升个性化体验。"Terminal Integration"部分讨论了Vim在终端中的集成，使其成为跨平台的开发工具。最后的"Working with Code"章节着重于Vim在代码编辑中的应用，包括语法高亮、代码折叠、智能提示等功能。全书的结尾部分，"Practical Tips and Tricks"提供了许多实战建议，帮助读者将所学知识转化为实际生产力。 "APress Pro Vim"不仅是一本技术手册，也是一本深度学习Vim的实用指南，适合任何希望提升Vim技能的开发者和程序员。无论是初次接触Vim的新手还是寻求进阶技巧的资深用户，都能从中获益匪浅。

CHAPTER 2 ■ INSTALLATION AND CONFIGURATION

Pretty, huh? Now take a look at Figure 2-2, which demonstrates how we will be tweaking the terminal.

Figure 2-1. Standard terminal interface

Figure 2-2. Enhanced terminal interface

CHAPTER 2 ■ INSTALLATION AND CONFIGURATION

OK, so it might not look that impressive right now, but trust me, in a short while, when we come to configuring

the terminal, you’ll see we’ll be making fundamental improvements that add lots of useful features to the shell.

Note ■ in the top right corner of the terminal you’ll see some text coloured red, which is the version number of the

Ruby programming language available (at that moment) to the terminal. The Ruby version is acquired and inserted by our

custom configuration (Listing 2-1), which we’ll look at shortly.

Shell Commands

Throughout this book, I’ll be using shell commands to do such things as creating files and folders, changing

directories, cloning Git repositories, downloading files, etc. I do this so it limits the need to move between the terminal

and your operating system’s GUI.

Note ■ Anytime I tell you to “run a command,” it is implied that I mean to either type the command (or copy and paste it)

into your terminal and press the carriage return/Enter key to run the command.

You should be fine to just run the commands as and when I instruct you to do so. Although I’ll explain each and

every command I ask you to run, if you’re interested to know more about the command and the options available, you

can view the relevant documentation for a command either online or within the operating system’s built-in manual.

To access the shell manual, you have to run the following command from your terminal (remember to substitute

{command} for the actual command):

man {command}

For example, imagine I tell you to run the following command:

ls -la | grep vimrc

In the preceding example, what we have are two commands separated by a pipe |. ls is the first command, and

-la are the options. The result of the ls command is then passed over to the grep command, where we also pass in

vimrc as an argument to the grep command.

Again, you should be fine just running the commands as and when I instruct. But it can be helpful to understand

how to read shell commands and where to find help.

To understand the preceding command, you’ll have to learn to break it down into its component parts (the

individual commands and options/flags). Commands can be constructed from multiple other commands (much like

connecting bits of Lego pieces together). Whenever you see the pipe character |, that is effectively telling us that we’re

passing the result of the command to the left of it as input for the command to the right of it.

If we consider the preceding command ls –la | grep vimrc, we can see that this command is made up of two

sub-commands. The first part of the command is ls –la, and the second part of the command is the grep vimrc part.

Commands are typically made up of the command itself (in this case, the commands are ls and grep), followed

by optional “flags” and then a parameter (or multiple parameters). In the preceding example, only the ls command

has specified some flags to alter the behavior of the command. You can tell when a flag is provided, because it is

prefixed by a hyphen (–). Here, we’ve passed in two flags, –l and –a, but we’ve used a shorthand version, –la, which

combines both flags into one, to save on space. In this case, providing an argument to the ls command is optional

(the command by default will list any files in the current, or specified, directory) The flags provided to the ls

command determine how the results are displayed.

CHAPTER 2 ■ INSTALLATION AND CONFIGURATION

The grep command, on the other hand, doesn’t have any flags specified, but it does have a single parameter,

which indicates to the command what it should do. In this case, the grep command is used to search files for a specific

phrase. We’re taking the list of directory files and telling grep to filter the results by any that contain the word vimrc.

Now that we know how to roughly interpret the structure of a command, we can use another command to

help us figure out what they do. I’ve already explained what the ls and grep commands do, but if you wanted extra

information about them and to see what flags they provide, then you could ask the terminal to display the official

documentation for the command.

By executing the command man ls, we’re asking the terminal to display the manual/documentation for the ls

command. Similarly, by executing the command man grep, we’ll be shown the documentation for the grep command.

Reminder ■ For any shell commands that I provide throughout the book, I’ll explain what they do, so don’t worry too

much if you’re not a command-line wizard.

Configuring Your Terminal

Before we begin configuring our terminal’s appearance, let’s take a brief detour to change our terminal from its default

shell, which will likely be Bash (see http://en.wikipedia.org/wiki/Bash_shell) to another shell called Zsh

(see http://en.wikipedia.org/wiki/Z_shell).

Zsh is a drop-in replacement for Bash and can be thought of as an improvement to the features found in the Bash

shell (much like Vim is an extension/improvement on top of the original Vi editor).

If you intend on using the ProVim shell configuration files (which I’ll show you in just a moment), it’s worth being

aware that they take advantage of some of Zsh’s extended features, which aren’t available within Bash. A short list of

Zsh features include more advanced and efficient auto-completion for typing and tabbing, command prompt color

settings, and intelligent handling of ambiguous commands (among other things). The ProVim .zshrc file is heavily

commented, so if you wish to see what else is preconfigured for you, I suggest taking some time to read through it

(although that’s not required).

Note ■ You can happily run Vim and tmux using the Bash shell. Nothing in our Vim configuration will rely on Zsh, but

our terminal environment and configuration uses a few Zsh-specific settings.

Changing Shells

Before you can actually install Zsh, you must know if you have it available. To check what shells are installed on your

system, open your terminal application and run the following command:

cat /etc/shells

Note ■ The preceding command displays all shell binaries available on the current system.

CHAPTER 2 ■ INSTALLATION AND CONFIGURATION

I hope that you’ll see something similar to the following output:

 cat /etc/shells

# List of acceptable shells for chpass(1).

# Ftpd will not allow users to connect who are not using

# one of these shells.

/bin/bash

/bin/csh

/bin/ksh

/bin/sh

/bin/tcsh

/bin/zsh

As you can see from the preceding output, we have /bin/zsh listed. This means we can indeed switch to the Zsh

shell. To change to the Zsh shell, run the following command:

chsh -s /bin/zsh

Dotfiles

Dotfiles are software/system files whose file name begins with a period (dot) character. The majority of settings for

your computer and installed software can be configured from specific dotfiles.

Dotfiles are also hidden by default. This is because any file that starts with a period character (e.g., .zshrc) is

considered to be a system file and should be hidden to protect general users from accidentally changing or deleting

those files, which could cause preinstalled software to break.

If you want to see the hidden files on your system, the easiest way to do so is to run the following command:

ls –a ~/

The preceding command lists (ls) all (-a) files (and by “all,” we mean including hidden files) within your home

directory (~/). Following is the output from my own home directory:

. .filezilla .node-gyp .viminfo Downloads

.. .fop .npm .viminfw.tmp Dropbox

.Box Sync .forever .npmrc .viminfz.tmp Justinmind

.CFUserTextEncoding .gem .php_history .vimrc Library

.DS_Store .gist-vim .phpsh .vmail Movies

.NERDTreeBookmarks .gitconfig .profile .weechat Music

.Trash .gitignore_global .pry_history .zcompcache Pictures

.atom .gitk .psysh .zcompdump Public

.bash_history .guard_history .rnd .zcompdump.zwc VirtualBox VMs

.cache .heroku .rubies .zhistory bin

.config .ievms .sqlite_history .zsh-update db

.cups .irb_history .ssh .zsh_history lib

.dbshell .lein .subversion .zshrc man

.distlib .lesshst .task Applications npm-debug.log

.dnc .local .taskrc Box Documents (backup) src

.docx4all .m2 .tmux.conf Box Sync

.docx4j .mongorc.js .vagrant Code

.dropbox .nave .vagrant.d Desktop

.dropbox-master .netrc .vim Documents

CHAPTER 2 ■ INSTALLATION AND CONFIGURATION

As you can probably tell at the moment, the terminal can be a pretty bland environment—a white background

and a black ominous $ prompt flashing back at you. It would be good if we could make our terminal look a bit nicer

and display some more useful information.

Editing .zshrc

To configure what our terminal looks like, we have to edit a dotfile for that specific environment. In this case, as

we’re using the Zsh shell, we’ll want to edit a .zshrc configuration file (which should be placed within your home

directory).

Note ■ If you were using the Bash shell, you would edit a .bashrc file instead. The ProVim repo is configured

specifically for the Zsh environment, so if your Linux distribution doesn’t have the Zsh shell installed by default, you can

install it manually, using the command apt-get install zsh.

Let’s start by looking inside your home directory and make sure you actually have a .zshrc file (if you don’t, we’ll

have to create one). To do that, run the following command:

ls -a ~/ | grep zshrc

If the preceding command doesn’t output anything to the terminal, then the file .zshrc doesn’t exist, and if that’s

the case, we’ll have to run the following command to create it:

touch ~/.zshrc

We now have to open up the .zshrc file and add some configuration settings that will allow us to configure our

terminal shell to look like Figure 2-2. I would use Vim to edit this dotfile, but as you’ve not yet learned how to use Vim,

I would suggest, for now, editing the file with the default text editor on your system.

If you’re on a Mac, the standard text editor is the TextEdit application (see

http://en.wikipedia.org/wiki/TextEdit). Running the following command will open the .zshrc file in TextEdit:

open -a TextEdit ~/.zshrc

Note ■ If you’re using a Linux-based machine, you’re either already comfortable using Vi/Vim or you can use the Nano

editor nano ~/.zshrc instead. If you’re on Windows and are using Cygwin, you should be able to run cygstart

{filename}

; however, as Windows is not a naturally Unix-based environment, I don’t cater for its configuration. If you

wish to configure your terminal on Windows, I would suggest using a script such as “Oh-my-cygwin” instead

(see https://github.com/haithembelhaj/oh-my-cygwin).

The file should now be open within your default editor, ready for you to start making some configuration

changes. Add Listing 2-1 into the .zshrc file (an easier to read online version can be found at https://github.com/

Integralist/ProVim/blob/master/.zshrc and will make it simpler for you to copy and paste from).

剩余405页未读，继续阅读

勤奋的猴子

粉丝: 0
资源: 1

APress Pro Vim：深度探索Vim配置与高级技巧指南

Apress Pro AngularJS 随书源代码

Pro Vim(Apress,2014)

Pro Vim by Mark McDonnell

关于springboot的英文文献

springboot参考文献

列举几个SpringBoot相关的技术文献,以文献引用的格式展示

spring boot项目英文文献

最近6年的C#参考书写在此处。要求序号、作者、书名、出版社、出版时间。

推荐5本sql server的书籍，并且说明书籍的ISBN号，出版社，作者，出版日期

javascript相关外文文献

最新资源