folder_exclude_patterns doesn't work on sub-directories

[Siyfion]

ie. Assuming I have this in my .sublime-project file:

"settings": {
  "todo": {
    "folder_exclude_patterns": [
      "node_modules",
      "tests/lib"
    ]
  }
}

Only the node_modules folder is excluded, the tests/lib folder still reports all it's todos, etc.

[dpashkevich]

Hm, this may be related to the issue I'm experiencing
#12 (comment)

If you add the same exclude patterns to your global User preferences, does the plugin start excluding tests/lib?

[Siyfion]

@dpashkevich nope, doesn't seem to work either way, no matter where they are defined.

[domdoescode]

Also got this issue, using Ubuntu 12.04

[emero]

+1

[akempes]

The script doesn't allow folder paths but only the folder names. Add just "lib" to the "folder_exclude_patterns".

Sadly this will exclude all lib folder throughout the whole project...

[dpashkevich]

Got it, thanks for clarifying

[redbar0n]

+1

[redbar0n]

@akempes @dpashkevich actually, it does say it allows folder paths:

"The path may be relative to the project directory, or a fully qualified path."

https://www.sublimetext.com/docs/2/projects.html

[redbar0n]

This might help some get the folder_exclude_patterns to work:

http://stackoverflow.com/questions/14203944/sublime-text-folder-exclude-patterns-stopped-working

1. Close the project.
2. delete the .sublime-workspace file.
3. Reopen.

[gpascale]

Looks like this is a pretty issue, but I just ran into it too. I'll work around by renaming my folders but it's pretty annoying to have to do that. I can't seem exclude the folder "js" without also excluding "src/js". I tried putting "./js" as the exclude pattern but that doesn't do anything.

[jonathanrdelgado]

@gpascale, this plugin has been deprecated for https://github.com/jonathandelgado/SublimeTodoReview, just fyi.

[robcowie]

Indeed it has. I still get quite a bit of activity on this repo. I'm not sure what the best course of action is; Delete this repo?

[jonathanrdelgado]

@robcowie I believe you can do a redirect, https://github.com/blog/1508-repository-redirects-are-here

I may be completely wrong about the use though. Nice to see you around, by the way. Hope all is well with you.

[gpascale]

Oh whoops, I thought I was commenting on the main SublimeText repo. I now
see that the issue I'm referring
to wasn't even the main issue here but just a comment in the thread.
Disregard :)
On Fri, Jan 22, 2016 at 6:55 PM Jonathan Delgado [email protected]
wrote:

@robcowie https://github.com/robcowie I believe you can do a redirect,
https://github.com/blog/1508-repository-redirects-are-here

I may be completely wrong about the use though. Nice to see you around, by
the way. Hope all is well with you.

—
Reply to this email directly or view it on GitHub
#44 (comment)
.

[robcowie]

@jonathandelgado I think the opportunity to use a redirect has been missed. I should have transferred ownership of this repo. As it is, there is no implied relationship between this and the new repo and it doesn't seem possible to create arbitrary redirects. Ah well.

All is well thanks; Spending most of my coding time these days with Apache Spark. A blessing and a curse in equal measure!