Conversation
Make the template a little clearer. SSH commands are for connecting to remote hosts, not the remote hosts+path combination going by $REMOTE in the main script. Bitpocket is handy for syncing music players and flash sticks, so hint at some good flags to use with FAT filesystems.
Allow $REMOTE_PATH to contain spaces (hosts too, I guess). Make an error message quote $REMOTE too, for a little more clarity when there are spaces in the path.
Allow init to be passed an empty hostname argument. The config file allows it already, referring to local file access for the remote end. Update usage instructions accordingly.
|
I really like this one. As I merged it into my own fork I took the liberty of modifying the tests so they always use paths with spaces, under the assumption that a path without spaces will work if one with spaces did. In the process a few problems with spaces within the tests themselves where uncovered and fixed. Feel free to merge the changes from my branch, patch-remote-path, into this pull request. |
|
Just FYI- I added support for empty hostname (local syncs) in #66 and released it in v0.2 |
|
@achadwick @runar0 would it be acceptable to add the FAT hints as a wiki page here or as a commented-out line in the default configuration? |
|
@greezybacon |
3 participants
A few minor fixes and user hints to make setup for syncing to transiently mounted USB devices with funny mountpoint names just a little smoother. FAT filesystems are pretty much a standard on these things; spaces in the names are common, and the things are almost always found locally attached. It's a use case which unison fails spectacularly badly at, to the extent of forcing a full comparison the first time on each new mount. rsync is dumber, so bitpocket seems to handle it better, given the right options.