From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Prickliness of the "invalid byte code" stuff Date: Fri, 21 Jun 2019 10:52:26 +0300 Message-ID: <83ef3npe85.fsf@gnu.org> References: <87tvcq9b0w.fsf@igel.home> <83v9x2svmf.fsf@gnu.org> <83fto6sphn.fsf@gnu.org> <83sgs5r20q.fsf@gnu.org> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="248080"; mail-complaints-to="usenet@blaine.gmane.org" Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: "T.V Raman" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jun 21 09:53:13 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1heEMC-0012QI-WD for ged-emacs-devel@m.gmane.org; Fri, 21 Jun 2019 09:53:13 +0200 Original-Received: from localhost ([::1]:55394 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1heEMB-0006Wr-SQ for ged-emacs-devel@m.gmane.org; Fri, 21 Jun 2019 03:53:11 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:47226) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1heELe-0006Wj-Qn for emacs-devel@gnu.org; Fri, 21 Jun 2019 03:52:40 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:47600) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1heELd-0000Th-Nn; Fri, 21 Jun 2019 03:52:38 -0400 Original-Received: from [176.228.60.248] (port=3845 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1heELb-0006L4-Uc; Fri, 21 Jun 2019 03:52:36 -0400 In-reply-to: (raman@google.com) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:237995 Archived-At: > From: "T.V Raman" > Date: Wed, 19 Jun 2019 14:35:18 -0700 > Cc: emacs-devel@gnu.org > > Stefan Monnier writes: > > > After 22 hours, 55 minutes, 40 seconds of Emacs uptime, > RSS: 1738828 > VSize: 2483972 > %Mem: 5.3 > %CPU: 0.4 > > which look fairly normal to what I was seeing in the past with emacspeak > compiled using byte-compile-dynamic. > > I've also not noticed any perceivable lag (desktop and laptop) when > calling autoloaded functions from large modules for the first time, e.g. > https://github.com/tvraman/emacspeak/blob/7957d9c0e6effc9749d027779c36a6cd82c05ebd/lisp/emacspeak-wizards.el > This module has over 4200 lines of code, and functions from it are often > used for the first time many hours after Emacs has been started. > >> I think I'd like to wait with the decision until we hear the > >> emacsspeak results. > > > > There's no hurry on this, indeed. OK, thanks. I did some more tests, and I think it's indeed OK to let this variable do nothing. But I guess we still need to accept its specification in file-local variables without any errors, at least for some time?