Re: Question about b:did_ftplugin

2007-04-02 Thread Andy Wokula
Thomas schrieb: Now, when I do set ft=X from the command line, it happens that the ftplugin X doesn't get loaded because it finishes when b:did_ftplugin is set. What I actually meant by this was: the ftplugin X doesn't get loaded when a filetype was already set before, i.e. when a filetype plu

Re: Question about b:did_ftplugin

2007-04-02 Thread Thomas
Now, when I do set ft=X from the command line, it happens that the ftplugin X doesn't get loaded because it finishes when b:did_ftplugin is set. What I actually meant by this was: the ftplugin X doesn't get loaded when a filetype was already set before, i.e. when a filetype plugin already def

Re: Question about b:did_ftplugin

2007-04-02 Thread Andy Wokula
Thomas schrieb: Hi, When I set a filetype for a buffer the variable b:did_ftplugin is set. The help says: If you are writing a filetype plugin to be used by many people, they need a chance to disable loading it. Put this at the top of the plugin: > " Only do this when not done yet for

Question about b:did_ftplugin

2007-04-02 Thread Thomas
Hi, When I set a filetype for a buffer the variable b:did_ftplugin is set. The help says: If you are writing a filetype plugin to be used by many people, they need a chance to disable loading it. Put this at the top of the plugin: > " Only do this when not done yet for this buffer