aboutsummaryrefslogtreecommitdiff
path: root/src/tracking
AgeCommit message (Collapse)Author
2016-02-19Rename some functions to match overall naming schemeAdrian Kummerlaender
2016-02-15Add support for commenting ignore patterns fileAdrian Kummerlaender
All lines starting with `#` are interpreted as comments
2016-02-14Implement support for excluding arbitrary paths from trackingAdrian Kummerlaender
The library may be provided with a new-line separated list of regular expressions via the newly introduced `CHANGE_LOG_IGNORE_PATTERN_PATH`. Any proposed tracking path that is matched by any of the provided patterns is excluded from change reporting. This functionality uses the Standard's regular expression parsing functionality and as such doesn't introduce any new dependencies. If no file path is provided or the provided file path is unreadable all paths will be tracked. `change` was adapted to set `CHANGE_LOG_IGNORE_PATTERN_PATH` to `.change_log_ignore` which means that it will by default exclude any patterns provided via this file in the current working directory. An example for such a file customized for hiding _vim_'s internal write logic may look as follows: [0-9]+ [^~]*~ [.*\.viminfo .*\.swp Note that this is implemented in a fashion where it is not guaranteed that the full _canonical_ path is checked against the patterns. It remains to be decided if this is enough for all common use cases of this new functionality. `tracking::PathMatcher` lacks any explicit thread synchronization - according to my current knowledge this should not be necessary as we are only ever reading the private `std::vector<std::regex>` instance. If invalid regular expressions are provided they are silently ignored.
2016-02-14Reduce `ChangeTracker` public _interface_ to `track`Adrian Kummerlaender
2016-02-13Add filesystem exception handling where requiredAdrian Kummerlaender
2016-02-11Extract child emplacement into thread safe memberAdrian Kummerlaender
2016-02-06Prevent deleted files from being displayed using `diff`Adrian Kummerlaender
2016-02-06Preserve pre-change file content as tracking stateAdrian Kummerlaender
Relying on `diff` for storing the pre-change content did not work out as it opens the file descriptors to soon and only reads the first block of pre-change file content until the remaining content is actually required. This obviously led to problems when tracking actually changing files.
2015-12-27Introduce thread synchronization for tracking init and loggingAdrian Kummerlaender
This obviously leads to synchronizing syscalls that would otherwise happen in parallel. Luckily the goal of this library is to monitor file changes performed by single, user facing applications and as such it doesn't matter if some operations are slightly slower.
2015-12-24Prevent the libraries own log writes from being trackedAdrian Kummerlaender
2015-12-24Add path label for the file provided via standard inputAdrian Kummerlaender
2015-12-24Use full path for change trackingAdrian Kummerlaender
Prevents the same file being tracked multiple times due to relative input paths.
2015-12-24Add support for changing the `diff` command via an environment variableAdrian Kummerlaender
While the file arguments remain fixed the actual `diff` application and its output style can be changed using the `CHANGE_LOG_DIFF_CMD` environment variable.
2015-12-24Match namespace and directory structureAdrian Kummerlaender