Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
Questions about the creation, usage and debugging of filetype plugins.
1
vote
pluging value to override vimrc
At best I guess you want to cache the previous user choice, that could have been done in the ftplugin or the user .vimrc.
get(g:, 'varname', defaultvalue) may help here. …
1
vote
How to combine identical ftplugin files?
May be you could move that code into a plugin file and in the autocommand, you test for the existence of &ft key in your g:plugins_some_var global variable. If so, you call the function.
1
vote
How to test ftplugins?
If your plugin isn't in the runtimepath, how could your ftplugin also be in the runtimepath. Without it, it can't be loaded automatically. …
1
vote
Setting variables in file in ftplugin directory
Filetype plugins are meant to set buffer local stuff. All your variables are global. IMO, It doesn't make sense to set, and reset, and reset them again and again every time you open a new C file.
Even …