mirror of
https://github.com/mhinz/vim-galore.git
synced 2025-02-24 01:59:28 +08:00
Autocmds: use less technical wording
Closes https://github.com/mhinz/vim-galore/issues/144
This commit is contained in:
parent
8a4cb44704
commit
85489f9a7f
12
README.md
12
README.md
@ -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-=:#
|
||||||
|
Loading…
x
Reference in New Issue
Block a user