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

Re: Problem opening a file named ".in"

Expand Messages
  • Bram Moolenaar
    ... Thanks for the patch. At first I thought I would include it. Thinking about this again, a simpler solution would be to use a pattern ? +.in instead of
    Message 1 of 6 , Sep 25, 2005
      Christian Robinson wrote:

      > Today (Sat, 24 Sep 2005), Stefan Karlsson wrote:
      >
      > > When opening a file named ".in" I get error E218 (autocommand
      > > nesting to deep). If the file is renamed to, for instance, "a.in" I
      > > don't get this error message.
      >
      > This patch for filetype.vim should fix it, and other potential
      > problems (made against 6.3, but it should work with 7.0 as well):

      Thanks for the patch. At first I thought I would include it. Thinking
      about this again, a simpler solution would be to use a pattern "?\+.in"
      instead of "*.in".

      That might actually be used for many more patterns. Perhaps all?

      --
      Proofread carefully to see if you any words out.

      /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
      /// Sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
      \\\ Project leader for A-A-P -- http://www.A-A-P.org ///
      \\\ Buy LOTR 3 and help AIDS victims -- http://ICCF.nl/lotr.html ///
    Your message has been successfully submitted and would be delivered to recipients shortly.