Okay, these are certain points that do not come instantly to me. However, I never intended to break these. The above functionality would remain for backward compatibility with old scripts. I am simply debating on how to implement this as a new feature.
On Thu, Mar 7, 2013 at 10:07 AM, Steven M. Schweda <[email protected]>wrote: > > Also, is the --post-file command really needed? Even if one does really > > need to use POST data from a file, one could always cat the file inside > > backticks as: > > > > > wget --options=POST `cat POSTdata` URL > > > > > > > Why not go with that? > > Apparently "always" means something to you which is different from > what it means to me. > > It may be hard to believe, or you may not care, but some folks use > this program on non-UNIX(-like) systems (VMS, for example), where such > UNIX(-like) shell tricks are not available. Even on UNIX(-like) > systems, some old shells may have limited command-line length. Some > users might not want the contents of their file exposed to every user on > the system who can run "ps". > > How many reasons do you need not to wreck existing functionality? > > ------------------------------------------------------------------------ > > Steven M. Schweda sms@antinode-info > 382 South Warwick Street (+1) 651-699-9818 > Saint Paul MN 55105-2547 > > -- Thanking You, Darshit Shah Research Lead, Code Innovation Kill Code Phobia. B.E.(Hons.) Mechanical Engineering, '14. BITS-Pilani
