> To keep vimb close to vim, we could try to built something like the `autocmd`.
> That allows to run various commands on a named event and a matched pattern on
> the opened file or in our case a URL to be opened.
> 
>     :au[tocmd] UrlLoadCommied *.example.com :set 
> scripts=on|cookie-accept=origin
> 
> Other useful events could be 'UrlLoadFinished', 'UrlLoadFailed',
> 'DownloadStarted', 'DownloadFinished' and 'WinCreate'.  In this was this could
> make vimb really flexible for many users and I think the auto commands can be
> used later for various other useful things too.  Because this would be the
> first event-based feature. Maybe this will also allow to inform external tool
> about finished downloads like requested on [github][65].

I agree, `autocmd` is better than "per domain settings" since it is more
powerful and may be of some use in the long run. 

I read that issue on github about custom commands for downloads. I
think that support for an external download tool is a good idea. 

First of all, vimb doesn't support some nice features of download managers,
for example, retrying failed download or parallel downloads. It is very
useful if you were downloading a big file and the download was interrupted 
for some reason. Then you don't need to redownload the whole file.

Also, it solves the problem of opening files after downloading. With a 
custom script you can easily open appropriative program depending on
mime-type/extension of downloaded file. You could achieve the same result
with ':au[tocmd] DownloadFinished :sh /path/to/script.sh %f', where %f
is a placeholder for the path to downloaded file.

There is no need to remove the `:save` feature from vimb. Why not just
make an external download tool optional?

------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
vimb-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vimb-users

Reply via email to