From: sigurd@12move.de (Karl Pflästerer)
Subject: Re: Orphaned symbols?
Date: Thu, 12 Feb 2004 22:03:44 +0100 [thread overview]
Message-ID: <m38yj884jg.fsf@hamster.pflaesterer.de> (raw)
In-Reply-To: <v9r7x0fl81.fsf@marauder.physik.uni-ulm.de>
On 12 Feb 2004, Reiner Steib <- 4.uce.03.r.s@nurfuerspam.de wrote:
> On Tue, Feb 10 2004, Karl Pflästerer wrote:
>> I got nosy and searched for variable names which were not used anywhere
>> in the code. I found 93 names (and some more functions).
> Huh, this number seems quite high.
I thought this also.
>> Before I post all these names in which libraries do I also have to
>> look for usage of variables?
> I'd suggest to post the list, maybe someone has a glue about their
Did you think glueing the vars makes any difference? :-)
> potential usage in other packages.
Okay here we go (there are some version variables; I include them also
just to be complete).
These are 32 variables which are not boundp in my current XEmacs Gnus
session. Maybe if I used some of the backends they would be boundp.
That would make sense at least for the version variables so I think they
can be safely ignored.
The other variables are boundp I write them afterwards; at
least boundp doesn't mean the variable gets used in some way or another.
(I wanted to attach the file but that was not possible; I have to check
why but first have to do a cvs up. XEmacs just seems to be in an
endless loop).
***************************** Not boundp ***************************
binhex-body-line -> binhex.el
binhex-end-line -> binhex.el
gnus-carpal-browse-buffer-buttons -> gnus-salt.el
gnus-carpal-group-buffer-buttons -> gnus-salt.el
gnus-carpal-server-buffer-buttons -> gnus-salt.el
gnus-carpal-summary-buffer-buttons -> gnus-salt.el
gnus-outlook-deuglify-version -> deuglify.el
gnus-picon-setup-p -> gnus-picon.el
gnus-tree-line-format-alist -> gnus-salt.el
gnus-tree-mode-line-format-alist -> gnus-salt.el
gnus-tree-mode-line-format-spec -> gnus-salt.el
gnus-uu-shar-file-name -> gnus-uu.el
mml1991-decrypt-function -> mml1991.el
mml1991-verify-function -> mml1991.el
nnagent-version -> nnagent.el
nnbabyl-version -> nnbabyl.el
nndb-version -> nndb.el
nndir-version -> nndir.el
nndoc-version -> nndoc.el
nneething-version -> nneething.el
nnimap-version -> nnimap.el
nnkiboze-version -> nnkiboze.el
nnmaildir--novlen -> nnmaildir.el
nnmaildir-version -> nnmaildir.el
nnmbox-version -> nnmbox.el
nnrss-version -> nnrss.el
nnsoup-version -> nnsoup.el
nnspool-version -> nnspool.el
nnwarchive-version -> nnwarchive.el
rfc1843-old-gnus-decode-header-function -> rfc1843.el
uudecode-body-line -> uudecode.el
uudecode-end-line -> uudecode.el
********************************************************************
************************* Boundp ***********************************
gnus-agent-file-header-cache -> gnus-agent.el
gnus-article-check-size -> gnus.el
gnus-article-mode-line-format-alist -> gnus-art.el
gnus-article-mode-line-format-spec -> gnus-spec.el
gnus-button-last -> gnus-art.el
gnus-button-regexp -> gnus-art.el
gnus-category-line-format -> gnus-agent.el
gnus-category-line-format-alist -> gnus-agent.el
gnus-category-mode-line-format -> gnus-agent.el
gnus-category-mode-line-format-alist -> gnus-agent.el
gnus-category-mode-line-format-spec -> gnus-agent.el
gnus-cited-closed-text-button-line-format-alist -> gnus-cite.el
gnus-current-copy-group -> gnus-sum.el
gnus-current-crosspost-group -> gnus-sum.el
gnus-current-move-group -> gnus-sum.el
gnus-ephemeral-group-server -> gnus-group.el
gnus-face-0 -> gnus-spec.el
gnus-face-1 -> gnus-spec.el
gnus-face-2 -> gnus-spec.el
gnus-face-3 -> gnus-spec.el
gnus-face-4 -> gnus-spec.el
gnus-group-line-format-alist -> gnus-group.el
gnus-group-mode-line-format-alist -> gnus-group.el
gnus-maintainer -> gnus.el
gnus-mouse-face-0 -> gnus-spec.el
gnus-mouse-face-1 -> gnus-spec.el
gnus-mouse-face-2 -> gnus-spec.el
gnus-mouse-face-3 -> gnus-spec.el
gnus-mouse-face-4 -> gnus-spec.el
gnus-newsgroup-none-id -> gnus-sum.el
gnus-server-line-format-alist -> gnus-srvr.el
gnus-server-mode-line-format-alist -> gnus-srvr.el
gnus-server-mode-line-format-spec -> gnus-srvr.el
gnus-summary-dummy-line-format-alist -> gnus-sum.el
gnus-summary-line-format-alist -> gnus-sum.el
gnus-summary-mode-line-format-spec -> gnus-spec.el
gnus-topic-indentation -> gnus.el
gnus-topic-line-format-alist -> gnus-topic.el
gnus-use-generic-from -> gnus.el
ietf-drums-dot-atext-token -> ietf-drums.el
ietf-drums-qtext-token -> ietf-drums.el
ietf-drums-quote-token -> ietf-drums.el
ietf-drums-specials-token -> ietf-drums.el
mail-source-imap-authenticators -> mail-source.el
mail-source-imap-streams -> mail-source.el
message-mode-syntax-table -> message.el
news-reply-yank-from -> nnheader.el
news-reply-yank-message-id -> nnheader.el
nndraft-version -> nndraft.el
nnfolder-version -> nnfolder.el
nnheader-numerical-full-files -> nnheader.el
nnmh-version -> nnmh.el
nnml-version -> nnml.el
nntp-version -> nntp.el
nnvirtual-version -> nnvirtual.el
pgg-armor-header-lines -> pgg-parse.el
pgg-fetch-key-function -> pgg.el
pgg-messages-coding-system -> pgg-def.el
pgg-status-buffer -> pgg-def.el
smiley-mouse-map -> smiley.el
********************************************************************
KP
--
Mary had a little lambda,
Its syntax white as snow,
And every program Mary wrote,
She wrote in Lisp, you know.
next prev parent reply other threads:[~2004-02-12 21:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 20:28 Karl Pflästerer
2004-02-12 14:03 ` Reiner Steib
2004-02-12 21:03 ` Karl Pflästerer [this message]
2004-02-12 22:02 ` Reiner Steib
2004-02-13 3:24 ` Jesper Harder
2004-02-13 21:25 ` Karl Pflästerer
2004-02-13 22:16 ` Jesper Harder
2004-02-13 23:11 ` Karl Pflästerer
2004-02-14 18:23 ` Kai Grossjohann
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=m38yj884jg.fsf@hamster.pflaesterer.de \
--to=sigurd@12move.de \
/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).