On Sat, Nov 5, 2011 at 14:40, <sta...@cs.tu-berlin.de> wrote: > * Étienne Faure <tinou...@gmail.com> [2011-11-05 14:29]: >> I'm afraid not. I tested it quickly for the same vim.org issue: >> >> webkit_download_get_suggested_filename(o) >> returned "download_script.php" instead of, in this case, >> "TagmaBufMgr.zip". > > I'm afraid, then curl won't do either.
As a matter of fact, it does: curl -JO 'http://www.vim.org/scripts/download_script.php?src_id=16808' downloads to a file named 'TagmaBufMgr.zip' (curl version 7.22.0) > To be honest, while I admit it is not beautiful, I never cared about > that. I land in a ${SHELL} after download finishes, see which file has > been downloaded, and can immediately rename it to what I consider sane. > File type is usually known from context, so ... it doesn't bother me > actually. Renaming the file afterwards can lead to failure: if the list of arguments after the ".php" is too long, the file won't be created, and the rename will fail. In such cases wget returns: Cannot write to `...' (File name too long).
