Given a software project which has (for whatever reason) some copies of 3rd-party code in some subdirs. Such 3rd-party code copies often should stay untouched from optimizations, to keep the diff to the original code as small as possible.

So it would be useful to be able to exclude those subdirs from clazy runs, to both not spend time on code which should not be changed as well as keep the result lists clean from uninteresting results (and fixes).


Example:
KDevelop codebase which has some copies of subversion code, astyle code and qtcreator's qml parsing code. Those copies are in their own special subdirectories  (all named 3rdparty/) and should be often ignored when running clazy on the whole project, like with performance checks.

Sp it would be useful to have an additional listing in the Clazy project config UI where one could lists project subfolders which should be excluded. Either by patterns or by explicit listing of existing subfolder paths, not sure yet what is more useful.

Subdirectories excluded here would then also mean the respective actions are not shown in the context menus on folders and files in those subdirs.

(Cmp also https://bugs.kde.org/show_bug.cgi?id=397885 filed for clazy-standalone with a similar reqzest, whose implementation though might not be relevant here, given kdevclazy does its own processing of the commands database and collection of source files to run clazy on).