From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Bozhidar Batsov <bozhidar@batsov.com>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Package installation messages
Date: Fri, 15 May 2015 00:15:55 +0100 [thread overview]
Message-ID: <CAAdUY-+=4Fg=O41AORK0Kuie+Ta4SJSRquH8WsZhV0166rxpUQ@mail.gmail.com> (raw)
In-Reply-To: <55552452.7050703@yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
> Here's another scenario:
>
> M-x package-install slime RET.
>
> See nothing of interest happening, try to do something else, maybe open a
file. While navigating to it, see Emacs seemingly freeze. Press C-g
instinctively - congrats, you've aborted the installation. Or stopped it in
an interesting place, I've got some sort of "transfer interrupted" message
once this way.
Yes, I've been meaning to mention that for a while now.
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.
1. Keep the feature but disable by default. Async refreshing would still be
enabled.
2. Implement it using a background emacs process. This has been mentioned
here before, it would not cause emacs to hang during the unpacking stage,
and would not be interrupted by C-g.
3. Just revert it. This has the advantage of simplifying the logic. Async
refreshing would still be kept.
[-- Attachment #2: Type: text/html, Size: 1220 bytes --]
next prev parent reply other threads:[~2015-05-14 23:15 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 [this message]
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
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-+=4Fg=O41AORK0Kuie+Ta4SJSRquH8WsZhV0166rxpUQ@mail.gmail.com' \
--to=bruce.connor.am@gmail.com \
--cc=bozhidar@batsov.com \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
/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).