Loading ...
Sorry, an error occurred while loading the content.

32315RE: bug in explicit :setf behavior?

Expand Messages
  • Vince Negri
    May 1, 2003
    • 0 Attachment
      > Essentially, one can do any number of explicit
      > :setf somefiletype's after the initial filetype setting, but only
      > the first existing

      > ftplugin/somefiletype.vim
      > indent/somefiletype.vim

      > take effect.

      If you look at how the ftplugins work, you will
      see why there is this limitation. The plugins
      are written to assert their settings over a
      blank canvas, and won't necessarily remove
      the settings of a previous ftplugin. Thus, if
      the second ftplugin was allowed to run, you
      would get a mixture of settings.

      To remove this problem, each ftplugin script
      would have to provide an "uninstall" function
      which could be first called by the :setf command
      if it detected there was an already loaded
      filetype.

      Vince



      Legal Disclaimer: Any views expressed by the sender of this message are
      not necessarily those of Application Solutions Ltd. Information in this
      e-mail may be confidential and is for the use of the intended recipient
      only, no mistake in transmission is intended to waive or compromise such
      privilege. Please advise the sender if you receive this e-mail by mistake.
    • Show all 17 messages in this topic