edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] &
Date: Wed, 7 Jan 2015 08:27:39 +0000	[thread overview]
Message-ID: <20150107082739.GG31364@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20150006172749.eklhad@comcast.net>

[-- Attachment #1: Type: text/plain, Size: 2246 bytes --]

On Tue, Jan 06, 2015 at 05:27:49PM -0500, Karl Dahlke wrote:
> > I've been thinking about the possibility of having a different command
> I would really rather not clutter the space with more commands.
> We already have too many as it is.
> And more will come if we work on imap.
> Besides this, I don't always know what I want until I am there.
> Particularly when traversing an ftp file system
> or clicking on a link.
> Is it the actual download, or is it another html page
> that is full of legal crap that I have to agree to?
> I just can't know in advance what to do.
> On an ftp link I hit g for go and if it turns out to be a directory I want to
> see that page, download into memory.
> If it turns out to be a file I want to be presented with the file name,
> which can be very long, but relevant, with version numbers in it
> and the proper suffix for compression and archive type etc,
> so I want it to offer me that file name and I just hit return if I like it,
> and don't have to type it all in again perfectly,
> and retain the option of typing in something else,
> but I don't usually know what I want until I am presented with the file name.
> And maybe another optional character like & if I want to differentiate between
> foreground download and background download,
> which I really think is a good idea, the more I think about it,
> to give people the options.
> It's only one more character to type to put it it in the background.

Yeah, as I said, I wasn't entirely sure about this idea.
I'm trying to avoid having to fork mid-download and all the issues that causes.
> I know you don't use mail client but this is consistent with how mail works,
> so people will be use to that.
> When you get mail it prints the default name of the attachment, which once
> again could be long, with version numbers and suffixes etc,
> and could be important, where you wouldn't want to type it all in again,
> so you just hit return and accept it, or type in a new file name
> for the attachment if you want to.
> I want to make this download feature the same way,
> having a common interface.

Fair enough, as you say I don't use the mail client so was unaware of this.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-01-07  8:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 22:27 Karl Dahlke
2015-01-07  8:27 ` Adam Thompson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-01-27  5:20 [Edbrowse-dev] == Kevin Carhart
2015-08-31  1:10 [Edbrowse-dev] ? Kevin Carhart
2015-01-07  8:49 [Edbrowse-dev] & Karl Dahlke
2015-01-06  2:19 Karl Dahlke
2015-01-06 21:29 ` Adam Thompson

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:

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

  git send-email \
    --in-reply-to=20150107082739.GG31364@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \


* 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).