unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: bruce.connor.am@gmail.com, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Async package.el
Date: Wed, 08 Apr 2015 09:32:28 -0400	[thread overview]
Message-ID: <jwv7ftmu4vz.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <55248915.5070707@yandex.ru> (Dmitry Gutov's message of "Wed, 08 Apr 2015 04:49:09 +0300")

> I haven't used PCL-CVS, but VC-Dir is a good counter-example: while it's
> refreshed asynchronously, we don't really expect the user to do much while
> that happens, other than maybe look at the output. It's just nicer to
> have a responsive Emacs during this operation (which could be long in
> certain cases).

I think the issue is that currently, when the async download ends, we
just completely rebuild the package-list, losing all previous info.
This needs to be fixed.  In PCL-CVS and in VC-Dir, when the async
operation ends, we merge the result with the current buffer's content.
So the user can mark/unmark elements which the async operation is in
process and these things aren't lost afterwards (and neither is the
position of point).

> And when vc-dir buffer is initially displayed, we don't have any "stale"
> data about the repository.

In PCL-CVS we did.

>> acceptable to add such a (mis)feature, but it should very clearly be OFF
>> by default, since we don't want Emacs to "call home" in such a way
>> by default.
> Fair enough. I'm also more partial to the option 1 (only refresh
> once a day), because it's more predictable, but the above would be closer to
> how other systems and applications look for updates (in the background,
> without bothering the user), so it should be something to consider.

I'm perfectly OK with changing the "auto-update" so that it's not done
at every call to list-packages (e.g. once a day is perfectly fine,
indeed.  I'd even agree with "never" and just let the user request an
update manually).  What I object to, is to do it even before list-packages
is invoked.


        Stefan



  reply	other threads:[~2015-04-08 13:32 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-06 10:46 Async package.el Artur Malabarba
2015-04-06 13:53 ` Dmitry Gutov
2015-04-06 14:32   ` Artur Malabarba
2015-04-07  1:19     ` Dmitry Gutov
2015-04-07 21:46       ` Stefan Monnier
2015-04-08  1:49         ` Dmitry Gutov
2015-04-08 13:32           ` Stefan Monnier [this message]
2015-04-09  1:49             ` Dmitry Gutov
2015-04-09 14:06               ` raman
2015-04-09 14:22                 ` Rasmus
2015-04-09 14:50                   ` Artur Malabarba
2015-04-09 14:53                     ` Artur Malabarba
2015-04-09 15:19                   ` async message Ivan Shmakov
2015-04-10 14:58                     ` raman
2015-04-10  1:32                   ` Async package.el raman
2015-04-09 18:18                 ` Stefan Monnier
2015-04-10 15:00                   ` raman
2015-04-12  0:46                   ` Artur Malabarba
2015-04-12  3:53                     ` Stefan Monnier
2015-04-07 23:26       ` Artur Malabarba
2015-04-08  2:19         ` Dmitry Gutov
2015-04-08  9:43           ` Artur Malabarba
2015-04-08 16:02             ` Dmitry Gutov
2015-04-08 18:39               ` Artur Malabarba
2015-04-09  2:10                 ` Dmitry Gutov
2015-04-09 10:14                   ` Artur Malabarba
2015-04-09 12:34                     ` Dmitry Gutov
2015-04-12  1:38                       ` Artur Malabarba
2015-04-07  5:31     ` Daiki Ueno
2015-04-07  9:13       ` Dmitry Gutov
2015-04-07  9:59         ` Artur Malabarba
2015-04-07 11:22           ` Robert Pluim
2015-04-07 12:33             ` Artur Malabarba
2015-04-07 14:29               ` Robert Pluim
2015-04-08  2:21                 ` Artur Malabarba
2015-04-07 21:50           ` Stefan Monnier
2015-04-08  5:27           ` Daiki Ueno
2015-04-09  8:38           ` Achim Gratz
2015-04-09 13:09             ` Stefan Monnier
2015-04-07 18:06 ` Stefan Monnier

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=jwv7ftmu4vz.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=bruce.connor.am@gmail.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).