github/vim-galore
1
0
Fork 0
mirror of https://github.com/mhinz/vim-galore.git synced 2025-11-04 20:05:36 +08:00
Code Issues Packages Projects Releases Wiki Activity

Autocmds: use less technical wording

Browse Source 
Closes https://github.com/mhinz/vim-galore/issues/144
This commit is contained in:
Marco Hinz
2019-05-06 00:42:02 +02:00
parent 8a4cb44704
commit 85489f9a7f
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@@ -746,17 +746,17 @@ See `:h text-objects` for all available text objects.
## Autocmds ## Autocmds
On many occasions, Vim emits events. You hook into these events by using You can trigger an action after many events in Vim, such as a buffer being
autocmds. 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 Vim relies extensively on autocmds. Don't believe me? Check `:au`, but don't let
if you don't notice it. Don't believe me? Check `:au`, but don't let the output the output overwhelm you. These are all the autocmds that are in effect right
overwhelm you. These are all the autocmds that are in effect right now! now!
See `:h {event}` for a quick overview of all available events and `:h See `:h {event}` for a quick overview of all available events and `:h
autocmd-events-abc` for more details. autocmd-events-abc` for more details.
A typical example would be setting filetype-specific settings: A typical example would be filetype-specific settings:
```vim ```vim
autocmd FileType ruby setlocal shiftwidth=2 softtabstop=2 comments-=:# autocmd FileType ruby setlocal shiftwidth=2 softtabstop=2 comments-=:#