unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org, miles@gnu.org
Subject: Re: CVS directories in completion-ignored-extensions
Date: Wed, 19 Jan 2005 12:34:43 +0100	[thread overview]
Message-ID: <m3r7khhcto.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <200401060300.MAA01945@etlken.m17n.org> (Kenichi Handa's message of "Tue, 6 Jan 2004 12:00:25 +0900 (JST)")

Kenichi Handa <handa@m17n.org> writes:

> I agree that, for the moment, the current size of
> REGEXP_CACHE_SIZE (== 20) is good enough.  But, for
> instance, regular expression is heavily used for displaying
> such complicated script as Indic to genarate composition.
> Gnus also uses regexp frequently.  If they are mixed
> (i.e. for people reading Devanagari mails in Gnus), I'm sure
> the size 20 is not enough.
>
> But, hmmm, perhaps 40 is enough.  I have to estimate it.

Did you make some conclusion here?

To me it seems like the regexp cache could be improved by
keeping a usage counter and a lru timestamp so frequently
used regexps could be kept in the cache -- and the cache
could grow dynamically to always hold the most frequently
used regexps [with some hard upper limit of course].

E.g. if I have a large number of regexps to split mail in gnus,
it would be nice to keep all of those in the cache.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2005-01-19 11:34 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-30  8:01 CVS directories in completion-ignored-extensions Eli Zaretskii
2003-12-30 23:44 ` Eric Hanchrow
2003-12-31  1:08   ` Luc Teirlinck
2003-12-31  1:34     ` Miles Bader
2003-12-31  5:51       ` Eli Zaretskii
2004-01-01  5:49       ` Eli Zaretskii
2004-01-01 21:10         ` Richard Stallman
2004-01-02  0:31           ` Miles Bader
2004-01-02  1:06           ` Kim F. Storm
2004-01-02  9:21             ` Eli Zaretskii
2004-01-03 11:52             ` Eli Zaretskii
2004-01-04 18:53               ` Richard Stallman
2004-01-04 23:17                 ` Stefan Monnier
2004-01-04 23:59                   ` Miles Bader
2004-01-05 17:56                     ` Richard Stallman
2004-01-06  0:08                       ` Miles Bader
2004-01-06  0:52                         ` Kenichi Handa
2004-01-06  1:54                           ` Miles Bader
2004-01-06  3:00                             ` Kenichi Handa
2005-01-19 11:34                               ` Kim F. Storm [this message]
2005-01-19 14:57                                 ` Stefan Monnier
2005-01-19 15:52                                   ` Kim F. Storm
2005-01-19 16:07                                     ` Stefan Monnier
2004-01-06  5:55                         ` Eli Zaretskii
2004-01-06  6:26                           ` Miles Bader
2004-01-07  2:40                         ` Richard Stallman
2004-01-01 21:27         ` Kim F. Storm

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=m3r7khhcto.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@gnu.org \
    --cc=miles@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).