From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: why so many kill-all-local-variables
Date: 27 Aug 1999 23:38:17 +0200 [thread overview]
Message-ID: <m37lmg29bq.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Wes Hardaker's message of "22 Jul 1999 15:32:06 -0700"
Wes Hardaker <wjhardaker@ucdavis.edu> writes:
> Not surprisingly, searching came out high on top (no surprise), but
> garbage collection and kill-all-local-variables dominated the scene.
> This made me wonder why killing the local variables was needed so
> much? I would think that you merely add to them or don't? I'm
> wondering if this is a major source of the garbage collection that is
> taking place (doubt it) and if they can be reduced?
[...]
> kill-all-local-variables 293 4.531 1824
This function should normally only be called when a new major mode is
instated, but I guess you don't have 1824 different buffers, huh?
Is it Gnus that's calling this function all the time?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1999-08-27 21:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-22 22:32 Wes Hardaker
1999-08-27 21:38 ` Lars Magne Ingebrigtsen [this message]
1999-09-01 16:59 ` Wes Hardaker
1999-09-25 7:52 ` Lars Magne Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m37lmg29bq.fsf@quimbies.gnus.org \
--to=larsi@gnus.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.
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 NNTP newsgroup(s).