summary refs log tree commit diff stats
path: root/lib/posix/inotify.nim
Commit message (Collapse)AuthorAgeFilesLines
* fixes #20526; use `nimPreviewSlimSystem` for documentation build (#20714)ringabout2022-11-011-0/+3
| | | | | | | * fixes #20526; use `nimPreviewSlimSystem` for `koch docs` * fixes documentation errors * fixes remaning issues
* Markdown code blocks migration part 7 (#20547)Andrey Makarov2022-10-121-2/+2
|
* Add `iterator inotify_events` which is *almost always* needed logic for (#15152)c-blake2020-08-081-0/+14
| | | | | | | | | | | | | | | | | | | | client code since Linux `inotify` is much like Linux `getdents64`. Expanding on "almost always"..The only time that this `iterator` logic is ***not*** needed on the output of a `read` from inotify fd's is when one passes a length to `read` *guaranteed* to only pass one event struct in the buffer. That unusual circumstance requires (at least!) knowing the length of the delivered filename before an event occurs, and the filename itself is optional for some event types. It is *far* more common to not know lengths in advance which means one passes a buffer big enough for at least one maximum length directory entry (256 bytes) which is then also big enough for *many* "typical" length entries and therefore many events. In such more common scenarios this iterator logic is definitely needed. Further, not using this logic, yet treating the return from read as "the whole answer" can test ok on "thin" event streams (e.g. 1 event per ms), hiding a latent bug of processing only the first event.
* Documentation and Code Style inotify (#13836)Juan Carlos2020-04-021-52/+53
|
* Documentation, add more examples (#13825)Juan Carlos2020-04-011-0/+10
|
* removes deprecated T/P typesAraq2018-11-161-1/+0
|
* remove dead code elimination option (#7669)Jacek Sieka2018-04-231-1/+1
|
* lib: Trim .nim files trailing whitespaceAdam Strzelecki2015-09-041-47/+47
| | | | via OSX: find . -name '*.nim' -exec sed -i '' -E 's/[[:space:]]+$//' {} +
* lib/posix - Dropped 'T' from typespdw2015-06-041-3/+4
|
* Nimrod renamed to NimAraq2014-08-281-1/+1
|
* New concurrency model: next stepsAraq2014-04-191-0/+2
|
* Added fsmonitor module.Dominik Picheta2012-09-021-0/+70