unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Artur Malabarba <bruce.connor.am@gmail.com>
To: raman <raman@google.com>
Cc: Bozhidar Batsov <bozhidar@batsov.com>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Package installation messages
Date: Wed, 20 May 2015 16:58:31 +0100	[thread overview]
Message-ID: <CAAdUY-JHc2zVWWB2VsHAsPR=ezeM=Ob5Wt7RVB=N2aWr5LXQEw@mail.gmail.com> (raw)
In-Reply-To: <p91siar2rdg.fsf@google.com>

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

On May 20, 2015 4:36 PM, "raman" <raman@google.com> wrote:
>
> Actually it would be sad to see the async package bits go -- it's
> *almost* working. Can we live with silenced messages as at present, and
> a slightly more descriptive message for "transaction ..." rather than
> losing the async goodness?

The messaging stuff is mostly independent of this. The problem is the fact
that it's not really async. After the download is done emacs hangs between
0.5 and 5 seconds while the installation is happening. And that happens for
each download. So it's essentially not really achieving anything, but it
carries the coat of code complexity.

But just to be clear. This is just for package installation. Async
refreshing is much smoother and won't be removed (though it's still due for
a bit of polishing).

[-- Attachment #2: Type: text/html, Size: 990 bytes --]

  parent reply	other threads:[~2015-05-20 15:58 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-14 21:23 Package installation messages Bozhidar Batsov
2015-05-14 22:38 ` Artur Malabarba
2015-05-14 22:40 ` Dmitry Gutov
2015-05-14 23:15   ` Artur Malabarba
2015-05-15  0:00     ` Dmitry Gutov
2015-05-15  2:00       ` Stefan Monnier
2015-05-15  2:24         ` Kaushal
2015-05-15  4:49           ` Bozhidar Batsov
2015-05-15  5:45             ` Thierry Volpiatto
     [not found]             ` <CAAdUY-K8h41cY0e1XB30rzoYOmuM2sFctAxhcF2B2D3R54V8Tw@mail.gmail.com>
2015-05-15  8:49               ` Artur Malabarba
2015-05-20 13:45                 ` Artur Malabarba
2015-05-20 15:36                   ` raman
2015-05-20 15:53                     ` Bozhidar Batsov
2015-05-20 15:58                     ` Artur Malabarba [this message]
2015-05-20 16:39                       ` T.V Raman
2015-05-20 19:59                         ` Artur Malabarba
2015-05-20 20:02                           ` Artur Malabarba
2015-05-20 20:05                             ` Dmitry Gutov
2015-05-21  0:15                               ` Kaushal
2015-05-21  9:03                             ` Artur Malabarba
2015-05-21 14:35                               ` Kaushal
2015-05-21 14:46                                 ` Kaushal
2015-05-21 14:49                                   ` Kaushal
2015-05-15  8:01           ` Artur Malabarba
2015-05-15  7:56         ` Artur Malabarba
2015-05-15  8:20         ` Dmitry Gutov
2015-05-15  7:51       ` Artur Malabarba

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to='CAAdUY-JHc2zVWWB2VsHAsPR=ezeM=Ob5Wt7RVB=N2aWr5LXQEw@mail.gmail.com' \
    --to=bruce.connor.am@gmail.com \
    --cc=bozhidar@batsov.com \
    --cc=emacs-devel@gnu.org \
    --cc=raman@google.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).