Re: lynx-dev Why use copy and not move when saving 'd'ownloaded files?

[Klaus Weide]

On Sun, 23 Jul 2000, Frédéric L . W . Meunier wrote:

> Hello. Lynx uses copy (syscall or cp(1)?) when 'd'ownloading files.
> I'd suggest using move since you can have problems with space. If an
> user downloads a big file (>=50mb), why waste time copying it again if
> moving it is what the user really wants? I wonder who's going to use
> -rw-------    1 fredlwm  fredlwm    57639 Jul 23 10:58 L24560-3304TMP.html
> and not
> -rw-rw-r--    1 fredlwm  fredlwm    57639 Jul 23 10:58 randim-4.8.tgz
> 
> But as you can see, Lynx is copying it. Say I use Lynx to download an
> .iso with 500mb and only have 700mb left. What's next? Of course, you
> should use EXTERNAL with a tool like GNU Wget, but not all users are
> going to configure lynx.cfg.

Yes, lynx's default "Save to disk" handler uses cp(1) [or whatever
else the lynx function LYCopyFile() uses - which might be different
depending on platform and configuaration].  But you can put whatever
you like in your own DOWNLOADER, and a "mv" should work just fine there.

Except that after that, the temp file is gone, which lynx won't expect -
but that shouldn't cause any real trouble.


   Klaus


; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden