From: larsi@ifi.uio.no (Lars Magne Ingebrigtsen)
Subject: Re: group-name symbols and obarrays
Date: 18 Nov 1995 07:49:55 +0100 [thread overview]
Message-ID: <w8s68gito18.fsf@surt.ifi.uio.no> (raw)
In-Reply-To: Ken Raeburn's message of Tue, 14 Nov 1995 17:02:16 -0500
Ken Raeburn <raeburn@cygnus.com> writes:
> Is there a reason why functions like gnus-group-list-groups and
> gnus-group-insert-group-line intern the group names in the default
> obarray instead of using one of the gnus hash tables?
No. So in September 0.14 they're all interned in
`gnus-active-hashtb', which is a hash table where most the group name
symbols already exists, so this should be a majorish improvement. If
you list 5000 groups, you would get 5000 new symbols interned in
September 0.12.
> Lots of gnus menu entry strings clutter the obarray too, and I have
> menus disabled using menu-bar-mode in my .emacs file.
Yup. The menus are created even when `menu-bar-mode' is nil, which is
a bug, I guess. Fix in 0.15. But that means that the menus won't
appear as advertised if the user toggles `menu-bar-mode' a lot...
--
Home is where the cat is.
prev parent reply other threads:[~1995-11-18 6:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-14 22:02 Ken Raeburn
1995-11-18 6:49 ` Lars Magne Ingebrigtsen [this message]
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=w8s68gito18.fsf@surt.ifi.uio.no \
--to=larsi@ifi.uio.no \
/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).