Re:Transfer.sh – File sharing from the command line
by LukeShu on Wednesday June 20, 2018 @12:41PM
(#17356981)
After all these years, I still can't keep straight when I need a trailing slash in rsync, and when I need to not have it.
Re:Transfer.sh – File sharing from the command line
by coatmatter on Wednesday June 20, 2018 @07:54PM
(#17360965)
If you think of it in terms of archives and whether you want to "extract" into the current directory, or a new directory within the current one; that might help.
rsync source destination will plonk the entire source directory and put it inside destination as a neat bundle.
rsync source/ destination will take the contents of source (but not the directory source itself) and plonk it in destination
I found the info page a little dry but it does describe it succintly:
rsync -av /src/foo /dest
rsync -av /src/foo/ /dest/foo
For some reason though, my head freaks out when it sees "foo" and "bar", but all they're saying is that it does the same thing.If in doubt though, just chuck everything into the destination ~/temp/ or ~/asdf/ and sort it out later.
To be honest though, most of the time I just use fish shell's autosuggestions to guide me along.
rsync -n -avh --progress source destination:~/asdf/ for a dry run followed by ctrl-p, ctrl-a, alt-f, alt-d, alt-d to remove the -n flag and then execute that for the real thing.
Occasionally though, I'll also use sftp if I'm just pulling one thing - perhaps even after sshing to the remote machine.
For all of these, SSH keys should be set up (and desktop logins secured) to make life easier.
As for Android, adb push and adb pull -a seems to work better than mtp:// or AirDroid in my experience.