A general setting for ignoring files

[faridnsh]

I'm using vim. When I edit a file like a.js.coffee , I'll get another file beside it .a.js.coffee.swp . And in this case docpad copies them too. We should have a setting similar to .gitignore for matching file names that needs to be ignored.

[balupton]

Hrmmm, well if we do /^\./ then .htaccess files won't be copied. It's a real annoying thing, as some editors will prefix with ~ too.

Perhaps what we need is to ignore /^(\.|\~)/ then have a whitelist.

[faridnsh]

Well what I'm saying is to make it configurable rather than hardcoding.

[tobiash]

I have the same issue using Vim. When using docpad watch, it refreshes every time I type a character (as vim's buffer file gets updated). Is there any workaround for this apart from disabling Vim's buffer files completely?

[balupton]

Happy to have this done. Is anyone willing to do a pull request?

[sfrdmn]

Looks like the best fix for this would be to pass user configuration to balUtil.scandir. There's a problem, though. 'scandir' takes an option ignorePatterns, which if true uses a default "common ignore patterns" regexp, or if given a RegExp object, uses that given RegExp object instead of the common ignore patterns.

Thing is, when specifying a custom regexp in Docpad (and probably in general), we want to concatenate that regexp to the defaults, not override them.

So I can either modify scandir's API such that there are two options: one boolean option which dictates whether to use the common ignore patterns and another option which specifies custom ignore patterns (which can, btw, be done in a backward compatible way), or I could modify Docpad such that it concatenates custom ignore patterns with the default ones and then passes that to 'scandir' for 'ignorePatterns'. The former seems cleanest.

Also, where would I stick a regexp concatenation function?

[balupton]

In v6.8.3 (just published) you can now specify your own ignorePatterns regex via the docpad configuration. Thanks to @Delapouite for this.

[balupton]

As of v6.19 we now have the configuration options ignoreCommonPatterns and ignoreCustomPatterns