Editing Talk:Command-line arguments (Client)

From FileZilla Wiki
Jump to navigationJump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
==FTPS==
 
 
ftps versus AUTH TLS ?
 
ftps versus AUTH TLS ?
  
==v3 Beta 11==
+
 
 
Where is command line on FZ3 Beta 11?  You can't just scrap that!
 
Where is command line on FZ3 Beta 11?  You can't just scrap that!
:I believe, there's no command line in FZ3 :(
+
- I believe, there's no command line in FZ3 :(
  
==Open directly to site==
+
It's crazy having no command line option to open directly to a given site and folder.  
It's crazy having no command line option to open directly to a given site and folder.  
+
What's the advantage in removing that functionality? That feature alone makes Windows  
What's the advantage in removing that functionality? That feature alone makes Windows  
+
Explorer infinitely more useful than FileZilla, despite any other shortcomings. Surely  
Explorer infinitely more useful than FileZilla, despite any other shortcomings. Surely  
+
you can't allow that?! ;-P   
you can't allow that?! ;-P   
+
(Except that Explorer can't handle a user name which include an '@', something that's  
(Except that Explorer can't handle a user name which include an '@', something that's  
+
compulsory on some sites. :-/  FileZilla would handle that, no problem - except!)
compulsory on some sites. :-/  FileZilla would handle that, no problem - except!)
+
[[Special:Contributions/78.151.111.152|78.151.111.152]] 13:14, 6 May 2008 (UTC)
[[Special:Contributions/78.151.111.152|78.151.111.152]] 13:14, 6 May 2008 (UTC)
 
  
==/?==
 
 
Bad thing: "Unknown option" in FZ3
 
Bad thing: "Unknown option" in FZ3
 
Usage: filezilla [/h] [--verbose]
 
Usage: filezilla [/h] [--verbose]
Line 21: Line 18:
 
Bring back the command line, I use it a lot.
 
Bring back the command line, I use it a lot.
  
==Urlencoded urls==
+
===Using KeePass===
How can I use a password that contains a '@' sign when using sftp:// url ?
 
 
 
==Using KeePass==
 
 
As a frequent user KeePass (and I guess many other password manager with equivalent functionality), I would like to have some Command Line functionality available. By using KP's CMD function I call an application i.e. FileZila and pass the required fields through to the app.
 
As a frequent user KeePass (and I guess many other password manager with equivalent functionality), I would like to have some Command Line functionality available. By using KP's CMD function I call an application i.e. FileZila and pass the required fields through to the app.
  
Line 30: Line 24:
 
[[User:JanEnEm|JanEnEm]]
 
[[User:JanEnEm|JanEnEm]]
  
== defaults for Cmd Line args ==
+
=== defaults for Cmd Line args ===
 
You definitively want to ask for a password when none is given by cmd line (interactive mode?). I can't see why that is not configurable (or default).
 
You definitively want to ask for a password when none is given by cmd line (interactive mode?). I can't see why that is not configurable (or default).
  
== upload from command line ==
+
=== upload from command line ===
 
Could you please bring back all command line options that were in v2 ? especially -u to updload a file from command line.
 
Could you please bring back all command line options that were in v2 ? especially -u to updload a file from command line.
  
Line 46: Line 40:
 
to ease the scripting process?
 
to ease the scripting process?
  
== Need to revert to FZ2 ==
+
=== Need to revert to FZ2 ===
 
Upload from command line is critical.  New versions tend to add features, not remove them.  I guess FZ is taking a different approach.
 
Upload from command line is critical.  New versions tend to add features, not remove them.  I guess FZ is taking a different approach.
  
== Commandline options are crucial for automation ==
+
=== Commandline options are crucial for automation ===
 
Filezilla could be the best FTP backup client available with simply that. Features like threading, fast incremental uploads and /close make it perfect for backups. Bonkey takes 20+ minutes to do an incremental backup to FTP while filezilla can be configured to do it in 21 seconds.
 
Filezilla could be the best FTP backup client available with simply that. Features like threading, fast incremental uploads and /close make it perfect for backups. Bonkey takes 20+ minutes to do an incremental backup to FTP while filezilla can be configured to do it in 21 seconds.
  
 
However without the -u feature we cant make it backup automatically. This is a serious draw back.
 
However without the -u feature we cant make it backup automatically. This is a serious draw back.
  
== Need more than -u anyway ==
+
=== Need more than -u anyway ===
  
 
I'm new to FileZilla but won't be using it. I need to automate FTP uploads. Not only is a lack of command line options crazy, but even -u is not enough. Windows "lame" FTP client lets you put a series of commands in a text file and run them all from a -s command line option. That's what FileZilla needs.
 
I'm new to FileZilla but won't be using it. I need to automate FTP uploads. Not only is a lack of command line options crazy, but even -u is not enough. Windows "lame" FTP client lets you put a series of commands in a text file and run them all from a -s command line option. That's what FileZilla needs.
Line 99: Line 93:
 
If it will not be in main application it must be created from same source as separate command line tool
 
If it will not be in main application it must be created from same source as separate command line tool
  
== Auto-Gen (Macro Recording) of Command Scripts  ==
+
== VzWPnZlLNYTZCRIs ==
 
 
I too was disappointed that there's no command script facility.
 
 
 
I have heap big request though... Which may seem like it's really over the top, but not really, since it's easier than it sounds. Instead of a scripting language, which requires an interpreter and all that, why not just an auto-generated XML file, which consists of settings followed by a set of clicked commands? The rule would be that after starting the record function, no settings can be changed - just clicks like Upload.
 
 
 
Once a user sets up an FTP connection and all the associated options in the GUI are set, really 90% of the command script is stored in all the GUI control values, so a "Record Script" function could write out the settings in an XML or special ini file that is specific to each script. That avoids having to come up with a special language to set each little parameter.
 
 
 
The Record Script would then record command clicks like "Upload" until "Stop Recording" is clicked. Again, it could just be a series of XML entries of the commands clicked, not a real script language. Maybe a couple of upload options might have to be added like "Upload all missing files in folder", so that absolute filenames don't have to be specified.
 
 
 
Then all the command line interpreter would have to do is run the GUI, load the specified XML or ini file, load all the GUI options with settings from the XML file, and then run the array of clicks specified, and return error codes for each step.
 
 
 
A few users may be limited in the things they could do in a normal scripting language or command like interface, but since the script would be auto-generated, 99% of users would probably think it's great to simply record a "missing files" upload that can be scheduled with Windows Scheduler, just by running FZ GUI and specifying a XML / ini filename!
 
 
 
In theory!!! - Which usually gets more complicated when implemented :-)
 
 
 
== FTP Client needs Command Line option ==
 
 
 
Just adding my vote... great GUI,
 
no use at all as no scripting functionality.
 
  
Good night.
+
11. November 2011Hallo Sandra,vielen Dank ffcr diesen insrnetsaeten und nfctzlichen Video-Tipp.Wie Du aus meiner langen Mail von gestern an Dich weidft, bin ich gerade damit befasst, meinen WP-Blog aufzubauen. Das  my category-order -Plugin habe ich gleich installiert und aktiviert.Der Navi-Punkt  Kat.-Reihenfolge  erscheint und die Kategorien lassen sich auch verschieben und neu anordnen.Das Problem dabei ist, dass diese c4nderungen nicht im Frontend zu sehen sind (habe natfcrlich gespeichert) und dort alles unvere4ndert bleibt.Hast Du eine Idee, woran das liegen kf6nnte?LGHarald
Shame.
 

Please note that all contributions to FileZilla Wiki are considered to be released under the GNU Free Documentation License 1.2 (see FileZilla Wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)