> From: Kevin Pacheco <[email protected]> >To: [email protected] >Sent: Thursday, July 11, 2013 8:35 PM >Subject: [Bug-wget] GnuWin32 wget.exe to stdout not working properly > > >Below is a paste of a ticket I opened at SourceForge. My question for >the list is whether there exists a compiled version of wget for >Windows that's not terribly old and doesn't have this problem. (By the >way, I'm using Gmail. I read in a forum that Gmail is causing problems >with some mailing lists because of a line-break issue. If that's the >case here, I apologize. I did switch to plain text mode.) > >I'm using the GetGnuWin32-0.6.3.exe package on Windows 7 64-bit. >Everything seems to be fine, except that wget doesn't direct output to >stdout correctly. If I do the following > >wget -qO- http://heerebout.nl/ > foo > >the output goes to the screen and "foo" ends up as a zero-byte file. >It's not using stderr either; I tried 2>&1 and also 3>&1. No dice. > >More important, when doing something like the line below, the output >is not changed. That means that scripts or batch files must save the >output to a file in order to perform manipulations (as far as I can >tell). > >wget -qO- http://heerebout.nl/ | sed s/Hello// > >Version: > >GNU Wget 1.12.1-dev Mar 04 2010 (mainline-013c8e2f5997) built on Windows-MinGW. >
covered here http://sourceforge.net/p/getgnuwin32/bugs/28/ There is no official windows build of wget so you can either build it yourself or use one of the test builds in that folder, or: On 05.06.2013 22:29, Bykov Aleksey wrote:> Greetings. >I know about three Wget builds for Win32 >1. From TumaGonx Zakkum (He assemble only releases. Don't look at link >name/date - lastest is 1.14) >http://opensourcepack.blogspot.ru/2010/05/wget-112-for-windows.html >2. From Ray Satiro [...] see test builds folder instead >3. From me >http://db.tt/iZxTCfuZ >
