From: Wes Hardaker <wjhardaker@ucdavis.edu>
Subject: Re: why so many kill-all-local-variables
Date: 01 Sep 1999 09:59:41 -0700 [thread overview]
Message-ID: <x7zoz6pnya.fsf@homestyle.dcn.davis.ca.us> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "27 Aug 1999 23:38:17 +0200"
>>>>> On 27 Aug 1999 23:38:17 +0200, Lars Magne Ingebrigtsen <larsi@gnus.org> said:
Lars> 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?
Lars> [...]
>> kill-all-local-variables 293 4.531 1824
Lars> This function should normally only be called when a new major mode is
Lars> instated, but I guess you don't have 1824 different buffers, huh?
Lars> Is it Gnus that's calling this function all the time?
Why is it needed at the beginning of a major mode? Why kill all the
local variables? Aren't you doing it from new buffers 99% of the
time?
(and, no, I don't, of course)
--
"Ninjas aren't dangerous. They're more afraid of you than you are of them."
next prev parent reply other threads:[~1999-09-01 16:59 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
1999-09-01 16:59 ` Wes Hardaker [this message]
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=x7zoz6pnya.fsf@homestyle.dcn.davis.ca.us \
--to=wjhardaker@ucdavis.edu \
/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).