From: Jeff Clough <jeff@chaosphere.com>
To: help-gnu-emacs@gnu.org
Subject: Re: LISP Questions - random, random elements and memory management
Date: Thu, 19 Nov 2009 10:16:14 -0500 (EST) [thread overview]
Message-ID: <20091119.101614.37733655.jeff@chaosphere.com> (raw)
In-Reply-To: <barmar-B0F0B8.08442419112009@nothing.attdns.com>
From: Barry Margolin <barmar@alum.mit.edu>
Date: Thu, 19 Nov 2009 08:44:24 -0500
> How about putting it in a text file that you load into a temporary
> buffer when you need it? Then kill the buffer when you're done with it.
I was thinking about this. The only real issue is with figuring out a
good lifecycle for the buffer that wouldn't leave the user confused
("Hey, where did this buffer come from?") or result in the file being
loaded/unloaded frequently enough to cause delays.
At this point, after dicking around in the Emacs Lisp manual, I'm
going to keep this as a "load" in my .emacs and assume that anyone who
wants to use the code will either do the same, or set up an autoload
expression if they care about memory usage. When I know more about
provide/require, I'll probably revisit it.
Thanks for the suggestion, though!
Jeff
next prev parent reply other threads:[~2009-11-19 15:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 12:54 LISP Questions - random, random elements and memory management Jeff Clough
2009-11-18 13:09 ` Jeff Clough
2009-11-19 2:53 ` Kevin Rodgers
2009-11-19 3:03 ` Kevin Rodgers
2009-11-19 11:56 ` Jeff Clough
[not found] ` <mailman.11040.1258631785.2239.help-gnu-emacs@gnu.org>
2009-11-19 13:44 ` Barry Margolin
2009-11-19 15:16 ` Jeff Clough [this message]
2009-11-20 3:52 ` Kevin Rodgers
[not found] ` <mailman.11114.1258689162.2239.help-gnu-emacs@gnu.org>
2009-11-20 6:28 ` Barry Margolin
[not found] ` <mailman.11056.1258643746.2239.help-gnu-emacs@gnu.org>
2009-11-19 17:40 ` Colin S. Miller
2009-11-19 18:57 ` Jeff Clough
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=20091119.101614.37733655.jeff@chaosphere.com \
--to=jeff@chaosphere.com \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).