From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] &
Date: Tue, 6 Jan 2015 21:29:26 +0000 [thread overview]
Message-ID: <20150106212926.GF31364@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20150005211926.eklhad@comcast.net>
[-- Attachment #1: Type: text/plain, Size: 1256 bytes --]
On Mon, Jan 05, 2015 at 09:19:26PM -0500, Karl Dahlke wrote:
> A possible compromise for download of large files to disk is:
>
> space pulls into memory like now.
> default file name or entered file name downloads to disk
> with progress dots in foreground.
> file name with & at the end downloads in background, no dots,
> for those who want it and for when it works.
> Like the shell, command &
> & by itself downloads default filename in background.
I'm not sure about this. I've been thinking about the possibility of having a
different command to download in the background rather than a download prompt
like we currently have. For example (I'm using 2 letter commands because I think they're a bit clearer than capitalised versions of existing commands)
something like:
g - downloads the link normally into memory
gd - downloads the link in the foreground to disk (optionally followed by a filename)
gb - same as gd but in the background
This isn't perfect since it doesn't handle if you end up with a file when you're not expecting it, but this shouldn't happen, and you can always hit ^c and try again anyway.
This way we avoid forking mid-download and all the weirdness involved in that.
Any thoughts?
Cheers,
Adam.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-01-06 21:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 2:19 Karl Dahlke
2015-01-06 21:29 ` Adam Thompson [this message]
2015-01-06 22:27 Karl Dahlke
2015-01-07 8:27 ` Adam Thompson
2015-01-07 8:49 Karl Dahlke
2015-08-31 1:10 [Edbrowse-dev] ? Kevin Carhart
2018-01-27 5:20 [Edbrowse-dev] == Kevin Carhart
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=20150106212926.GF31364@toaster.adamthompson.me.uk \
--to=arthompson1990@gmail.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
/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).