This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of
computers,
computing, and
information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join
the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
This article has been
automatically rated by a
bot or other tool as Stub-class because it uses a
stub template. Please ensure the assessment is correct before removing the |auto= parameter.
This article is within the scope of WikiProject Apple Inc., a collaborative effort to improve the coverage of
Apple,
Mac,
iOS and related topics on Wikipedia. If you would like to participate, please visit the project page, where you can join
the discussion and see a list of open tasks.Apple Inc.Wikipedia:WikiProject Apple Inc.Template:WikiProject Apple Inc.Apple Inc. articles
This article has been
automatically rated by a
bot or other tool as Stub-class because it uses a
stub template. Please ensure the assessment is correct before removing the |auto= parameter.
Does not watch file system?
> **Until Mac OS X 10.7, FSEvents did not "watch" the filesystem…**
Yes, that's a confusingly written sentence. Basically, OS X 10.7 added the flag
kFSEventStreamCreateFlagFileEvents, which lets you receive file-level events, rather than directory-level events.
In 10.5, when the user changed file "Documents/GroceryList.doc", fsevents reported "something in the Documents/ folder was modified". In 10.7 and later, when this flag is used, then fsevents will report "the file Documents/GroceryList.doc was modified". — Preceding
unsigned comment added by
73.109.61.123 (
talk)
01:40, 18 April 2017 (UTC)reply
It does not help that the the citation has long since expired.