You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, TCP sends full paths, e.g. /home/user/project/foo, which makes no sense for TCP broadcasting if that exact path doesn't exist on another machine.
Ideally, TCP broadcaster should always send paths relative to current directory, unless custom directories are given with the '-d' option.
The text was updated successfully, but these errors were encountered:
This would solve this problem on VMs: guard/guard#751
Currently, TCP sends full paths, e.g.
/home/user/project/foo
, which makes no sense for TCP broadcasting if that exact path doesn't exist on another machine.Ideally, TCP broadcaster should always send paths relative to current directory, unless custom directories are given with the '-d' option.
The text was updated successfully, but these errors were encountered: