From 85489f9a7faab11d5a88790019646139e9eba728 Mon Sep 17 00:00:00 2001 From: Marco Hinz Date: Mon, 6 May 2019 00:42:02 +0200 Subject: [PATCH] Autocmds: use less technical wording Closes https://github.com/mhinz/vim-galore/issues/144 --- README.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 6bdca2d..89397b5 100644 --- a/README.md +++ b/README.md @@ -746,17 +746,17 @@ See `:h text-objects` for all available text objects. ## Autocmds -On many occasions, Vim emits events. You hook into these events by using -autocmds. +You can trigger an action after many events in Vim, such as a buffer being +saved or Vim having started up, by so-called _autocmds_. -You wouldn't use Vim if there weren't autocmds. They're used all the time, even -if you don't notice it. Don't believe me? Check `:au`, but don't let the output -overwhelm you. These are all the autocmds that are in effect right now! +Vim relies extensively on autocmds. Don't believe me? Check `:au`, but don't let +the output overwhelm you. These are all the autocmds that are in effect right +now! See `:h {event}` for a quick overview of all available events and `:h autocmd-events-abc` for more details. -A typical example would be setting filetype-specific settings: +A typical example would be filetype-specific settings: ```vim autocmd FileType ruby setlocal shiftwidth=2 softtabstop=2 comments-=:#