Gnus development mailing list
 help / color / mirror / Atom feed
From: wmperry@aventail.com (William M. Perry)
Cc: ding@gnus.org
Subject: Re: Request for opinions as to feasibility of a Gnus application.
Date: 08 Nov 1999 07:04:19 -0500	[thread overview]
Message-ID: <8666zdfav0.fsf@megalith.bp.aventail.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "08 Nov 1999 09:37:17 +0100"

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Lloyd Zusman <ljz@asfast.com> writes:
> 
> > However, I'd like to give the users the means within Gnus to download
> > these large files to their local machines, if desired.  To do so, I'd
> > like to create a new decoding command within Gnus which, for any
> > selected articles, would create an asynchronous process which uses FTP
> > or HTTP or rsync or something similar (yet to be decided and possibly
> > even configurable at run time) to download the associated large files
> > to a user-specified location on the local machine.
> 
> I think I don't grok what you're trying to do, as you can see from the
> following stupid question: why don't you put a URL in the article and
> then use W3 to download the URL?

You'd still want to hack something up to start it asynchronously.  By
default Emacs/W3 does not do asynch downloads.  And to get asynch fetches
with efs/ange-ftp, you would need to use copy-file intead of find-file.

-bp


  reply	other threads:[~1999-11-08 12:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-07 20:04 Lloyd Zusman
1999-11-08  8:37 ` Kai Großjohann
1999-11-08 12:04   ` William M. Perry [this message]
1999-11-13 23:00     ` Lloyd Zusman
1999-11-11  4:20   ` Lars Magne Ingebrigtsen
1999-11-16 20:34     ` Lloyd Zusman
1999-12-01 15:37       ` Lars Magne Ingebrigtsen
1999-12-01 16:07         ` William M. Perry
1999-11-13 22:48   ` Lloyd Zusman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8666zdfav0.fsf@megalith.bp.aventail.com \
    --to=wmperry@aventail.com \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).