thac0/vim
1
0
Fork 0
forked from aniani/vim
Code Activity

updated for version 7.3.442

Browse Source 
Problem:    Still read modelines for ":doautocmd".
Solution:   Move check for <nomodeline> to separate function.
This commit is contained in:
Bram Moolenaar
2012-02-12 20:14:01 +01:00
parent bbc98db7c4
commit 60542ac9fd
5 changed files with 36 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
runtime/doc/autocmd.txt
View File

@@ -1072,6 +1072,14 @@ option will not cause any commands to be executed.
argument is included, Vim executes only the matching
autocommands for that group. Note: if you use an
undefined group name, Vim gives you an error message.
*<nomodeline>*
After applying the autocommands the modelines are
processed, so that their settings overrule the
settings from autocommands, like what happens when
editing a file. This is skipped when the <nomodeline>
argument is present. You probably want to use
<nomodeline> for events that are not used when loading
a buffer, such as |User|.
*:doautoa* *:doautoall*
:doautoa[ll] [<nomodeline>] [group] {event} [fname]
@@ -1085,12 +1093,6 @@ option will not cause any commands to be executed.
This command is intended for autocommands that set
options, change highlighting, and things like that.
After applying the autocommands the modelines are
processed, so that their settings overrule the
settings from autocommands, like what happens when
editing a file. This is skipped when the <nomodeline>
argument is present.
==============================================================================
10. Using autocommands *autocmd-use*