Skip to main content

Using Spell Checking in Vim

Mark Twain has been quoted as saying that he respected a person who could spell a word more than one way. Unfortunately, Twain's enthusiasm for creative spelling isn't widely shared today, at least in the professional world. If you need a little help in the spelling department, but prefer the old school way of editing text, you can turn to Vim's spelling support.
Support for spell checking was added in Vim 7. Before that, a few scripts were available to hack spell checking support into Vim — or you could do what I did and use ispell or aspell, but inline spell checking is much nicer.
If you're new to Vim and/or using Vim in text mode, it's not obvious that Vim even supports spell checking. But it does, and it's easy to use once you turn it on. You'll need to be in command mode and switch to last line mode, then run this:
:set spell spelllang=en_us
You might not want to be that specific, or you might want a different region. The "en_us" specifies English, U.S. style. You might want to use "en_ca" instead, if you're in Canada, or "en_gb" for Great Britain, or "en_au" for Australia. And, of course, this works for other languages as well.
If you're using Vim to write code and prose, you might want to turn spell checking on only in the local buffer. To do that, use:
:setlocal spell spelllang=en_us
Once you've set this, Vim will highlight misspelled words. If you're using Vim in text mode, you should see the entire word highlighted, or if you're using Gvim, you should see a squiggly underline for any word that is misspelled.
Vim does more than just highlight misspelled words, it actually categorizes misspelled words, it also highlights rare words, words that aren't capitalized (but should be), and words that have the wrong spelling for the specified region. For example, I've set Vim to check for U.S. spelling (spelllang=en_us), so it should highlight words that are spelled correctly in another region but might be considered incorrect for the local region.
Vim uses different colors for each type of word. This may vary depending on the colors you have set up in your terminal or how you have Gvim set up, but on my system I see misspelled words highlighted with red, an orange for rare words, blue for words that aren't capitalized, and so on.
Getting tired of seeing the highlighting? You may want to turn spell checking off if you're working with code or something like that. Use the nospell directive to turn this off:
:set nospell

Using Spellchecking

Spell checking wouldn't be very useful if you didn't have any help correcting the misspelled words, or a way to tell the program that the word is actually correct. Let's start with correcting words.
To move to a misspelled word, use ]s and [s. The ]s command will move the cursor to the next misspelled word, the [s command will move the cursor back through the buffer to previous misspelled words.
Once the cursor is on the word, use z=, and Vim will suggest a list of alternatives that it thinks may be correct. For instance, if I highlight autocompletion and then use z=, I see something like figure 1:
 Word suggestions in Vim
Just hit Enter if none of the suggestions work, or enter the number for the correct word.
What if Vim is wrong, and the word is correct? Use the zg command and Vim will add it to its dictionary. Simple as pie. You can also mark words as incorrect using zw.
If you don't want to keep telling Vim explicitly every time you restart to turn on spelling, just add the following to your .vimrc:
set spell spelllang=en_us
Substitute the appropriate region, of course.
Vim's combination of syntax highlighting, autocompletion (using CTRL-p and CTRL-n), abbreviations and mappings, and spell-checking makes it a killer editor to write in. Even when I need to share materials with clients in ODF or Word format, I usually write first in Vim with HTML and then copy and paste into OpenOffice.org, which usually handles the formatting just fine.

Comments

Popular posts from this blog

OWASP Top 10 Threats and Mitigations Exam - Single Select

Last updated 4 Aug 11 Course Title: OWASP Top 10 Threats and Mitigation Exam Questions - Single Select 1) Which of the following consequences is most likely to occur due to an injection attack? Spoofing Cross-site request forgery Denial of service   Correct Insecure direct object references 2) Your application is created using a language that does not support a clear distinction between code and data. Which vulnerability is most likely to occur in your application? Injection   Correct Insecure direct object references Failure to restrict URL access Insufficient transport layer protection 3) Which of the following scenarios is most likely to cause an injection attack? Unvalidated input is embedded in an instruction stream.   Correct Unvalidated input can be distinguished from valid instructions. A Web application does not validate a client’s access to a resource. A Web action performs an operation on behalf of the user without checking a shared sec

CKA Simulator Kubernetes 1.22

  https://killer.sh Pre Setup Once you've gained access to your terminal it might be wise to spend ~1 minute to setup your environment. You could set these: alias k = kubectl                         # will already be pre-configured export do = "--dry-run=client -o yaml"     # k get pod x $do export now = "--force --grace-period 0"   # k delete pod x $now Vim To make vim use 2 spaces for a tab edit ~/.vimrc to contain: set tabstop=2 set expandtab set shiftwidth=2 More setup suggestions are in the tips section .     Question 1 | Contexts Task weight: 1%   You have access to multiple clusters from your main terminal through kubectl contexts. Write all those context names into /opt/course/1/contexts . Next write a command to display the current context into /opt/course/1/context_default_kubectl.sh , the command should use kubectl . Finally write a second command doing the same thing into /opt/course/1/context_default_no_kubectl.sh , but without the use of k

标 题: 关于Daniel Guo 律师

发信人: q123452017 (水天一色), 信区: I140 标  题: 关于Daniel Guo 律师 关键字: Daniel Guo 发信站: BBS 未名空间站 (Thu Apr 26 02:11:35 2018, 美东) 这些是lz根据亲身经历在 Immigration版上发的帖以及一些关于Daniel Guo 律师的回 帖,希望大家不要被一些马甲帖广告帖所骗,慎重考虑选择律师。 WG 和Guo两家律师对比 1. fully refund的合约上的区别 wegreened家是case不过只要第二次没有file就可以fully refund。郭家是要两次case 没过才给refund,而且只要第二次pl draft好律师就可以不退任何律师费。 2. 回信速度 wegreened家一般24小时内回信。郭律师是在可以快速回复的时候才回复很快,对于需 要时间回复或者是不愿意给出确切答复的时候就回复的比较慢。 比如:lz问过郭律师他们律所在nsc区域最近eb1a的通过率,大家也知道nsc现在杀手如 云,但是郭律师过了两天只回复说让秘书update最近的case然后去网页上查,但是上面 并没有写明tsc还是nsc。 lz还问过郭律师关于准备ps (他要求的文件)的一些问题,模版上有的东西不是很清 楚,但是他一般就是把模版上的东西再copy一遍发过来。 3. 材料区别 (推荐信) 因为我只收到郭律师写的推荐信,所以可以比下两家推荐信 wegreened家推荐信写的比较长,而且每封推荐信会用不同的语气和风格,会包含lz写 的research summary里面的某个方面 郭家四封推荐信都是一个格式,一种语气,连地址,信的称呼都是一样的,怎么看四封 推荐信都是同一个人写出来的。套路基本都是第一段目的,第二段介绍推荐人,第三段 某篇或几篇文章的abstract,最后结论 4. 前期材料准备 wegreened家要按照他们的模版准备一个十几页的research summary。 郭律师在签约之前说的是只需要准备五页左右的summary,但是在lz签完约收到推荐信 ,郭律师又发来一个很长的ps要lz自己填,而且和pl的格式基本差不多。 总结下来,申请自己上心最重要。但是如果选律师,lz更倾向于wegreened,