jdspugh / jp-watch-c Goto Github PK

The results of running jp-watch on Linux and MacOS are currently different. The differences are summarised below with the type of change and the resulting output per OS. Ideally the Linux version should produce output that is the same as the MacOS version which is more correct. Linux usually returns parent directories of changes instead of the actual changed files or directories:

FILE EDIT: echo '123' > <existing file>

Linux

• <existing file>

MacOS

• <existing file>

FILE CREATION: touch <file>

Linux

• Parent Directory: <parent dir>
• File: <file> (should be just <file>)
• Note: b contains FAN_CREATE (ignore the lone create event)
• b2 contains FAN_MODIFY (return this only)

MacOS

• <file>

DIRECTORY CREATION: mkdir <dir>

Linux

• Parent Directory: <parent dir> (should be <dir>)
• Note: b contains FAN_CREATE + FAN_ONDIR

MacOS

• <dir>

FILE/DIRECTORY MOVE: mv <file> <dir> | mv <dir> <dir>

Linux

• Parent Directory: <parent dir> (should be <file>)
• Fix/Hack:
  • Three events will appear in b:
    • b contains FAN_MOVE (src parent path)
    • b contains FAN_MOVE (dst parent path)
    • b contains FAN_MOVE_SELF (the end of this path contains the name of the file moved)
  • Take the file name from FAN_MOVE_SELF and append it to both FAN_MOVE directory paths. Output only the FAN_MOVE directory paths with the appended filename.

MacOS

• Destination: dst <dir/file>
• Source: src <dir/file>

touch a

or

echo '' > a

will results in duplicate paths output by jp-watch

/path/a
/path/a

This is because both a FAN_CREATE and a FAN_ATTRIB event is emitted for the same path. A solution could be storing the last path in the app's main event processing loop and use it to eliminate duplicate paths through loop iterations.