unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 75142@debbugs.gnu.org, Philip Kaludercic <philipk@posteo.net>,
	tusharhero@sdf.org
Subject: bug#75142: 31.0.50; package-refresh-contents is not async when using interactively.
Date: Sat, 04 Jan 2025 10:46:05 -0500	[thread overview]
Message-ID: <jwvh66ek2ic.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <867c7aeqnj.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 04 Jan 2025 13:59:12 +0200")

>> When running `M-x package-refresh-contents RET', my Emacs session
>> freezes for a long time. But it is possible to run this async, we need
>> to give it an argument. I think when the function should be async, I
>> understand that when using this in emacs lisp program, that maybe not be
>> desirable. So maybe you can have a separate functions for emacs lisp
>> programs, or have different behavior for interactive use.
>
> Philip and Stefan, any comments?

I guess it would make sense to run it asynchronously when called
interactively, but in that case we should emit messages that clarify
what going on, e.g. a first (synchronous) "Refreshing in the background..."
followed by "Refreshing packages completed" at the end.


        Stefan






      parent reply	other threads:[~2025-01-04 15:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-27  9:45 bug#75142: 31.0.50; package-refresh-contents is not async when using interactively tusharhero--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-04 11:59 ` Eli Zaretskii
2025-01-04 12:11   ` Philip Kaludercic
2025-01-04 15:46   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]

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=jwvh66ek2ic.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=75142@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=philipk@posteo.net \
    --cc=tusharhero@sdf.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).