From: "T.V Raman" <raman@google.com>
To: "T.V Raman" via "Emacs development discussions." <emacs-devel@gnu.org>
Cc: monnier@iro.umontreal.ca
Subject: Re: Suggest: Byte-Compile package-quickstart on a separate thread?
Date: Mon, 28 Dec 2020 10:38:01 -0800 [thread overview]
Message-ID: <p91lfdhrd2u.fsf@google.com> (raw)
In-Reply-To: <24554.9038.480017.868364@retriever.mtv.corp.google.com> (T. V. Raman's message of "Mon, 28 Dec 2020 10:26:22 -0800")
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 1305 bytes --]
"T.V Raman" via "Emacs development discussions." <emacs-devel@gnu.org>
writes:
Here's a small patch that uses make-thread:
git diff package.el
diff --git a/lisp/emacs-lisp/package.el b/lisp/emacs-lisp/package.el
index bc450b09d0..104c2d8e71 100644
--- a/lisp/emacs-lisp/package.el
+++ b/lisp/emacs-lisp/package.el
@@ -4108,7 +4108,7 @@ package-quickstart-refresh
;; no-update-autoloads: t
;; End:
"))
- (byte-compile-file package-quickstart-file)))
+ (make-thread #'byte-compile-file package-quickstart-file)))
(defun package--imenu-prev-index-position-function ()
"Move point to previous line in package-menu buffer.
> Haven't written the patch yet;-)Stefan Monnier writes:
> > > The faster startup is nice, but one consequence of byte-compiling
> > > package-quickstart after package updates is that emacs blocks for a
> > > while. I myself use package paradox which already does the
> > > download/unpack asynchronously; could we also move the
> > > byte-compilation of package-quickstart to a separate thread?
> >
> > Sounds like a good idea, but you forgot to attach the patch to
> > your message.
> >
> >
> > Stefan ;-)
>
> --
> 7©4Id: kg:/m/0285kf1 0Ü87©4
--
Thanks,
--Raman
7©4 Id: kg:/m/0285kf1 0Ü8
next prev parent reply other threads:[~2020-12-28 18:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 14:49 Suggest: Byte-Compile package-quickstart on a separate thread? T.V Raman
2020-12-28 16:31 ` Stefan Monnier
2020-12-28 17:34 ` Stefan Kangas
2020-12-28 18:26 ` T.V Raman via Emacs development discussions.
2020-12-28 18:38 ` T.V Raman [this message]
2020-12-28 19:19 ` Eli Zaretskii
2020-12-28 19:52 ` T.V Raman via Emacs development discussions.
2020-12-28 19:58 ` Eli Zaretskii
2020-12-28 20:34 ` Andrea Corallo via Emacs development discussions.
2020-12-28 21:50 ` T.V Raman via Emacs development discussions.
2020-12-28 23:47 ` arthur miller
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=p91lfdhrd2u.fsf@google.com \
--to=raman@google.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).