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: Wed, 19 Jun 2019 18:36:35 +0300 Message-ID: <83zhmdr3i4.fsf@gnu.org> References: <87tvcq9b0w.fsf@igel.home> <83v9x2svmf.fsf@gnu.org> <83ef3qsp3x.fsf@gnu.org> <23817.16756.555983.544329@retriever.mtv.corp.google.com> <83d0jas3lo.fsf@gnu.org> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="220844"; mail-complaints-to="usenet@blaine.gmane.org" Cc: eggert@cs.ucla.edu, monnier@iro.umontreal.ca, rms@gnu.org, emacs-devel@gnu.org To: "T.V Raman" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 19 17:44:20 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 1hdcl2-000vK3-2q for ged-emacs-devel@m.gmane.org; Wed, 19 Jun 2019 17:44:20 +0200 Original-Received: from localhost ([::1]:39594 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hdcl0-0003s6-Nk for ged-emacs-devel@m.gmane.org; Wed, 19 Jun 2019 11:44:18 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45640) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hdcdy-0006i8-FJ for emacs-devel@gnu.org; Wed, 19 Jun 2019 11:37:03 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:39794) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hdcdt-0007xj-Uy; Wed, 19 Jun 2019 11:36:59 -0400 Original-Received: from [176.228.60.248] (port=3486 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1hdcdk-0007iu-Gb; Wed, 19 Jun 2019 11:36:49 -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:237905 Archived-At: > From: "T.V Raman" > Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org, monnier@iro.umontreal.ca, rms@gnu.org > Date: Wed, 19 Jun 2019 06:54:48 -0700 > > this will take some time --- emacspeak has a lot of modules that are > loaded on demand -- and the memory footprint is a function of how long > the session is running -- I consider killing emacs a mortal crime. There's no rush. It's just that emacspeak uses this variable in a lot of Lisp files, so I think it's important to see how such an extreme situation will react to deletion of this variable, before we make the decision. > Will let you know if I feel the running image getting bloated over > time. Thank you.