I don't use FTP anymore to transfer files.. However today I *had* to. This is the day I realise that I still haven't found the perfect FTP client.
The LFTP problem:
Don't get me wrong, I like this program, however it's when I need to "get" recursively that I start to have to think.. is it "mirror" or "mirror -R" ? .. knowing that one of the options will delete stuff remotely I have taken the habit of simply not using this tool. It does seem completely stupid to have such an option when most people are used to the "-r" switch.. . why would "get file" become "get mirror directory/" ? So close yet, no. (And yes, I know, I can be that way : ] ).
The NCFTP issue:
hmm, well, it's actually the program I've used the most, it has bookmarks and stuff, uses the normal "-R" syntax, it also has some neat features useful when scripting. However it does not support any form of encryption, so it can only be considered private if used in 1855. Another issue I encountered today, is when I finally was going to recursively get a directory I got this new and neat error:
tar: This does not look like a tar archive
Yes, directories are not tar archives, thanks for the heads up.
Yet another FTP client, YAFC:
This one seems cool, I'm sure it's the best one for me EXCEPT (of course) that whoever develops this program does not seem to care about the users enough to leave a help file or something. There is a manual, but say you copy a file that already exists, you get a nice prompt:
Overwrite? [yncauR, ? for help]
And yes, the "?" has no effect (in my case at least). Even the "help" command does not work. So this could be the one, but I might never know. To be fair, I met this program only recently so maybe when we get to know each other better things will work out... .
I think that the 3 developers need to get into some threesome and bring to this earth a decent, simple, functional command line GNU FTP client that works..