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 09:49:20 +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=001a1133bb468d6cad05161aeb1e X-Trace: ger.gmane.org 1431679770 27188 80.91.229.3 (15 May 2015 08:49:30 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 15 May 2015 08:49:30 +0000 (UTC) Cc: Kaushal , Dmitry Gutov , Stefan Monnier , emacs-devel To: Bozhidar Batsov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 15 10:49:29 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 1YtBJB-0002LU-5v for ged-emacs-devel@m.gmane.org; Fri, 15 May 2015 10:49:29 +0200 Original-Received: from localhost ([::1]:58597 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YtBJA-0007Pw-ER for ged-emacs-devel@m.gmane.org; Fri, 15 May 2015 04:49:28 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47310) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YtBJ5-0007Mg-3k for emacs-devel@gnu.org; Fri, 15 May 2015 04:49:23 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YtBJ3-0006CY-QR for emacs-devel@gnu.org; Fri, 15 May 2015 04:49:23 -0400 Original-Received: from mail-la0-x229.google.com ([2a00:1450:4010:c03::229]:33247) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YtBJ3-0006By-JX for emacs-devel@gnu.org; Fri, 15 May 2015 04:49:21 -0400 Original-Received: by lagr1 with SMTP id r1so27513371lag.0 for ; Fri, 15 May 2015 01:49:20 -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=GkzkBwSublZwtCE735w/+06xOfMvhtJJqyPY5grmtlk=; b=RfPXgFJX2I9Vc9gdPRrCmK/eFokXNl0wxgd8NWLSYvXREG16SIYTpYpejEb4TicCTF qEB87P2xHxDNZqLFB4OSw3/wpOIxWd5U5b5lSI6Yu/QBQRE93Na21WikZAuGDZF9hkuL JzAcmtIAUs9n1bxnwiymFRnJXg6ZIA6Zk+cOVERPAHlE9usgdvnZwfCJu688mK7ld/Em V9m2gTBAfSzCIL9zuFUHYWz+yaOufkLe/jlXE6iOuDAX6Whb5kvIVOn2JofbRm8R94C7 GsUDncRX2CSkW7CL1WSGLpcN/KWq878NJDEc73eSyH7tZTx71XDGwtbv55aZE4O8sdAJ NheA== X-Received: by 10.112.50.74 with SMTP id a10mr1435978lbo.4.1431679760426; Fri, 15 May 2015 01:49:20 -0700 (PDT) Original-Received: by 10.25.150.1 with HTTP; Fri, 15 May 2015 01:49:20 -0700 (PDT) Original-Received: by 10.25.150.1 with HTTP; Fri, 15 May 2015 01:49:20 -0700 (PDT) In-Reply-To: X-Google-Sender-Auth: Xo5veMmZ5M52UacepFZHhrdm0ME X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c03::229 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:186512 Archived-At: --001a1133bb468d6cad05161aeb1e Content-Type: text/plain; charset=UTF-8 On May 15, 2015 5:49 AM, "Bozhidar Batsov" wrote: > > While I can live without the compilation warnings (and many users are scared by them) I've found and fixed a ton of compilation warnings in various packages, because they we're displayed so prominently. Maybe this should be an optional behaviour or they should simply be dumped into **Messages*. Once the whole thing is done, we could say how many warnings occurred along with the finished message. Not sure what's the appropriate way to count them though, since they happen between bytecomp and warnings.el. > As for the messages themselves - yeah, anything featuring a summary of the operation that started and ended would do IMO. Some progress indicator would be awesome (maybe counting down the operations that are remaining or something). A progress indicator is certainly doable, though its implementation will have to wait until we decide how to do the installation process. --001a1133bb468d6cad05161aeb1e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On May 15, 2015 5:49 AM, "Bozhidar Batsov" <bozhidar@batsov.com> wrote:
>
> While I can live without the compilation warnings (and many users are = scared by them) I've found and fixed a ton of compilation warnings in v= arious packages, because they we're displayed so prominently. Maybe thi= s should be an optional behaviour or they should simply be dumped into **Me= ssages*.

Once the whole thing is done, we could say how many warnings= occurred along with the finished message. Not sure what's the appropri= ate way to count them though, since they happen between bytecomp and warnin= gs.el.

> As for the messages themselves - yeah, anything featuri= ng a summary of the operation that started and ended would do IMO. Some pro= gress indicator would be awesome (maybe counting down the operations that a= re remaining or something). =C2=A0

A progress indicator is certainly doable, though its impleme= ntation will have to wait until we decide how to do the installation proces= s.

--001a1133bb468d6cad05161aeb1e--