From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Artur Malabarba Newsgroups: gmane.emacs.devel Subject: Re: Package installation messages Date: Fri, 15 May 2015 08:51:41 +0100 Message-ID: References: <55552452.7050703@yandex.ru> <55553712.2050608@yandex.ru> Reply-To: bruce.connor.am@gmail.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e013d1ea664dba005161a1d0f X-Trace: ger.gmane.org 1431676312 29101 80.91.229.3 (15 May 2015 07:51:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 15 May 2015 07:51:52 +0000 (UTC) Cc: Bozhidar Batsov , emacs-devel To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 15 09:51:51 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YtAPN-00078v-D7 for ged-emacs-devel@m.gmane.org; Fri, 15 May 2015 09:51:49 +0200 Original-Received: from localhost ([::1]:58273 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YtAPM-0007tJ-QV for ged-emacs-devel@m.gmane.org; Fri, 15 May 2015 03:51:48 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58528) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YtAPI-0007oW-BD for emacs-devel@gnu.org; Fri, 15 May 2015 03:51:45 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YtAPH-0006uw-1J for emacs-devel@gnu.org; Fri, 15 May 2015 03:51:44 -0400 Original-Received: from mail-la0-x236.google.com ([2a00:1450:4010:c03::236]:35388) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YtAPG-0006uj-Oz for emacs-devel@gnu.org; Fri, 15 May 2015 03:51:42 -0400 Original-Received: by labbd9 with SMTP id bd9so107244289lab.2 for ; Fri, 15 May 2015 00:51:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=EW8JaRInBscqHusA+TBq9iFhvRaVw/HdaDi3RF0nRqM=; b=duAGeracS7GjyTIQRtLA9N5Sl9600d5gQfu09yaLsGUyTp+XORjUQMD4i8o7Kh3GVu WCe7ddIK8lcDsX2IbA3JOKJYWraW7nk8gr74G4IpbDcrBFYjBmZyKmoM07tvNYGOsEgc 98Jg3f3YTtkiy43c3FvutIXxVFUB2XYoVsXf8ARc9n5vkkgdzAOP8n7OPx0oXWyuyGZw J0+5Frea4EpQ9/L9TyBxdlAVKSBLqA5CCbBrb/g7WbfbYFFrZE+3dW+2tzneIue7cuWn tTm9uVqPkJjMeXCOg4yb7KJjajrZIaMiks/+vYOjQgXqXEtEib9pCc6eRPo245XdzRvD tfsA== X-Received: by 10.152.5.164 with SMTP id t4mr6231962lat.16.1431676301661; Fri, 15 May 2015 00:51:41 -0700 (PDT) Original-Received: by 10.25.150.1 with HTTP; Fri, 15 May 2015 00:51:41 -0700 (PDT) Original-Received: by 10.25.150.1 with HTTP; Fri, 15 May 2015 00:51:41 -0700 (PDT) In-Reply-To: <55553712.2050608@yandex.ru> X-Google-Sender-Auth: C93F6q09nPzcCfvQStxYahA4tIE X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c03::236 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:186508 Archived-At: --089e013d1ea664dba005161a1d0f Content-Type: text/plain; charset=UTF-8 >> Now that the async features have been out for a few months, I can say I >> like the async refreshing but I'm not a fan of how async installation >> turned out (for the exact reasons you mention above). I see 3 options, >> and I'd like to know what people think. > > Async refreshing has grown on me too, but it still needs to implement retaining the marks set by the user. Yes, it needs to be done, and it's on my "next time I have time" list. >> 3. Just revert it. This has the advantage of simplifying the logic. >> Async refreshing would still be kept. > > IIUC, async installation also performs downloads concurrently, right? That would be a useful trait to keep. No, it performs the downloads in sequence. It would be nice if someone made it concurrent (with or without async). --089e013d1ea664dba005161a1d0f Content-Type: text/html; charset=UTF-8

>> Now that the async features have been out for a few months, I can say I
>> like the async refreshing but I'm not a fan of how async installation
>> turned out (for the exact reasons you mention above). I see 3 options,
>> and I'd like to know what people think.
>
> Async refreshing has grown on me too, but it still needs to implement retaining the marks set by the user.

Yes, it needs to be done, and it's on my "next time I have time" list.

>> 3. Just revert it. This has the advantage of simplifying the logic.
>> Async refreshing would still be kept.
>
> IIUC, async installation also performs downloads concurrently, right? That would be a useful trait to keep.

No, it performs the downloads in sequence. It would be nice if someone made it concurrent (with or without async).

--089e013d1ea664dba005161a1d0f--