Bug 54075 - gnus and flim both have mailcap.el
Summary: gnus and flim both have mailcap.el
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: xemacs   
(Show other bugs)
Version: roswell
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact: Aaron Brown
Depends On:
TreeView+ depends on / blocked
Reported: 2001-09-26 21:30 UTC by Richard Maine
Modified: 2007-04-18 16:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-09-26 21:30:06 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Richard Maine 2001-09-26 21:30:02 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010809

Description of problem:
Gnus occasionally gives a message saying that the definition of
mailcap-parse-mailcaps as a function is void.

Tracing this down, I find that mailcap-parse-mailcaps is defined in
the file mailcap.el in the xemacs-packages/lisp/gnus subdir.  But there is
also a mailcap.el file in the flim subdir.  Apparently gnus
ends up loading the wrong file.  If I explicitly load the gnus/mailcap.el
file by full pathname, things work.

As a workaround, I moved the lisp/flim subdir to bug/flim to get
it out of the way (as I don't use flim, whatever it is).  That
fixed it.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.emacs -f gnus     (assuming you've got usenet access set up)
2."j comp.lang.fortran"  then "=" to enter the newsgroup
3. ctrl-S to start a search, then type (w/o quotes)
   "How to get Intel"
4. hit return twice to try read the article you just found
(I've selected one particular recent article that triggers it;
many others do also).

Actual Results:  Symbol's function definition is void: mailcap-parse-mailcaps

Expected Results:  See the article

Additional info:

Comment 1 Trond Eivind Glomsrxd 2001-09-27 01:48:46 UTC
We removed the file from semi 1.14.3-6 mid-August.

Note You need to log in before you can comment on or make changes to this bug.