Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make use of FSEvent event pairs to interpret events #4

Open
DivineDominion opened this issue Apr 26, 2017 · 0 comments
Open

make use of FSEvent event pairs to interpret events #4

DivineDominion opened this issue Apr 26, 2017 · 0 comments

Comments

@DivineDominion
Copy link
Contributor

File modifications from TextEdit produce this log output:

texteditfile.txt changed (isFile, renamed, finderInfoModified, xattrsModified)
texteditfile.txt.sb-56afa5c6-SOiDRl changed (isFile, renamed)
texteditfile.txt changed (isFile, renamed, finderInfoModified, inodeMetaModified, xattrsModified)
texteditfile.txt.sb-56afa5c6-SOiDRl changed (isFile, modified, removed, renamed, changeOwner)

At the moment (1.0.2), each of these events is forwarded to the callback independently. But the originate in pairs. This extra information could be useful to interpret events in 2 ways:

  1. Either in the lib itself, reducing 2 renamed events to a single renamed from ... to ...
  2. In the client, when we forward not single events but the original pairs, too

Both ways enable us to interpret

texteditfile.txt changed (isFile, renamed, finderInfoModified, xattrsModified)
texteditfile.txt.sb-56afa5c6-SOiDRl changed (isFile, renamed)

... as "texteditfile.txt is renamed to texteditfile.txt.sb-56afa5c6-SOiDRl".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant