From: Jari Aalto <jaalto@tre.tele.nokia.fi>
Cc: ding@ifi.uio.no
Subject: Re2: gnus-cache redux
Date: Fri, 8 Dec 1995 18:18:33 +0200 [thread overview]
Message-ID: <199512081618.SAA08528@aapo.tele.nokia.fi> (raw)
|7.12.95, Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
| Or whatever.
|
| Anyways, I've added an active file to gnus-cache, which means that
| Gnus startup with the cache won't be noticably slower than starting
| Gnus without the cache.
|
| While I'm revising gnus-cache, I wonder whether I should do more. I'm
| not really satisfied with the method Gnus uses for entering/removing
| stuff from the cache -- it's all based on the article marks, and it
| feels a bit kludgy. I'm also wondering how to fit that "persistent
| article" thingie into the scheme.
|
| I'm open to ideas. If you've given gnus-cache some thought, speak now
| or forever hold your tongue. (Ick!)
I haven't got the slightest idea of what/how it does
caching... but maybe you could use the hash array as I do in
my rcs package? Something like this...(Ick, untested)
tirc = tinyrcs.el
(defvar tirc-:hash-table
"Cache for file's information.")
;;; ............................................................ &hash ...
(defun tirc-init-hash ()
"Clears hash table."
(setq tirc-:hash-table (make-vector 60 nil)))
(defmacro tirc-hash-get (file &optional allocate)
"Gets hash table entry for file."
(` (if (, allocate)
(intern (, file) tirc-:hash-table)
(intern-soft (, file) tirc-:hash-table))))
(defun tirc-hash-prop (file prop &optional put-value)
"Gets property PROP for FILE. If FILE is not a bucket, signal error.
Optionally replaces PROPERTY contents with PUT-VALUE.
"
(let* (sym)
(if (null (setq sym (tirc-hash-get file)))
(error "No bucket for file.")
(if put-value
(put sym prop put-value)
(get sym prop)))
))
reply other threads:[~1995-12-08 16:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199512081618.SAA08528@aapo.tele.nokia.fi \
--to=jaalto@tre.tele.nokia.fi \
--cc=ding@ifi.uio.no \
--cc=jari.aalto@ntc.nokia.com \
/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).