From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (75-164-214-250.ptld.qwest.net [75.164.214.250]) by hurricane.the-brannons.com (Postfix) with ESMTPSA id 5E3D578CF5 for ; Mon, 5 Jan 2015 16:27:50 -0800 (PST) From: Chris Brannon To: Edbrowse-dev@lists.the-brannons.com References: <20150005163335.eklhad@comcast.net> Date: Mon, 05 Jan 2015 16:25:26 -0800 In-Reply-To: <20150005163335.eklhad@comcast.net> (Karl Dahlke's message of "Mon, 05 Jan 2015 16:33:35 -0500") Message-ID: <87zj9weow9.fsf@the-brannons.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Edbrowse-dev] curl things X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jan 2015 00:27:50 -0000 Karl Dahlke writes: > then maybe we shouldn't spend a lot of time tracking it down. > I wasn't asking for the feature in the first place. Me either. I use GNU screen, so if my edbrowse blocks, I just open up another screen window and fire off another browser. The saving directly to disk feature is nice though, since that's what people are usually going to want to do with extremely large files. I do see why some folks would like downloading in the background, so if I can figure out why it barfs on https, I will. Something tells me that it's not ok to use the same curl handle across multiple processes though. More research is required. -- Chris