Matthew Dawkins napsal(a):
> Jeff,
> 
> David Smid from Unity Linux recently patched two bugs around
> filetriggers that fixes the .
> 
> - added
> extra_nl_chars_in_patterns_and_filenames patch
> see http://issues.unity-linux.org/index.php?do=details&task_id=281
> <http://issues.unity-linux.org/index.php?do=details&task_id=281>
> 
> - added
> trigger_cannot_be_applied_to_multiple_files patch
> see http://issues.unity-linux.org/index.php?do=details&task_id=282
> <http://issues.unity-linux.org/index.php?do=details&task_id=282>

The second patch is actually wrong and should be reverted. It comes from my
misunderstanding how filetriggers are supposed to work.

The first patch enables firing file triggers again but breaks passing of file
name entries through pipe.

You can find more info here:
http://issues.unity-linux.org/index.php?do=details&task_id=282


Here's a better patch: http://issues.unity-linux.org/index.php?getfile=39

This one doesn't break passing of file name entries through pipe, adds safety
check for valid pipe FD, adds few more debug messages to make debugging less
confusing and matches file name without ending NL character.

There's one think I don't like on current implementation:
Only the first match is passed on the script's command line. Calling script with
all the matched entries passed as parameters gives more sense.

Sorry for any inconvenience.

Regards,

David