Help tracing this error

Help tracing this error

[reader]

I get news and mail in a batch fetch.  I log its output to a log file.

I've recently upgraded my machine, and all the concommittant trial
and tribulations that go with moving from an old machine to new one.
An newly installed version of the OS (Redhat 7.3) cvs emacs and cvs
gnus of last few days.  

I've imported most of my old setup.  .news* files .gnus .emacs and
the scripting that runs the batch fetches from cron.

The output contains an error at the end that I cannot identify.

  Jun 05 2002 17:04:03 Symbol's function definition is void:
  font-lock-unfontify-buffer

Just after readin .mailrc.  This is running in a batch fetch run by
hand in a shell script.  It error out before the nntp fetching gets
done.

Anyone recognize where this is comming from?.   A grep like this:
reader $ grep 'font-lock-unfontify-buffer' ~/.gnus ~/.emacs \
  ~/.site-start.el ~/scripts/fetchall
Turns up nothing.

Jun 05 2002 17:03:56 Loading ~/.emacs-custom...
Jun 05 2002 17:03:57 Reading /home/reader/.newsrc-enews.newsguy.com.eld...
Jun 05 2002 17:03:57 Reading active file from enews.newsguy.com via nntp...
Jun 05 2002 17:04:03 Reading active file via nnml...
Jun 05 2002 17:04:03 Opening nnml server...
Jun 05 2002 17:04:03 Opening nnml server...done
Jun 05 2002 17:04:03 nnml: Reading incoming mail from directory...
Jun 05 2002 17:04:03 nnml: Reading incoming mail (no new mail)...done
Jun 05 2002 17:04:03 Reading active file via nnml...
Jun 05 2002 17:04:03 Reading active file via nnml...done
Jun 05 2002 17:04:03 Reading active file from archive via nnfolder...
Jun 05 2002 17:04:03 Opening nnfolder server on archive...
Jun 05 2002 17:04:03 Opening nnfolder server on archive...done
Jun 05 2002 17:04:03 Reading active file from archive via nnfolder...
Jun 05 2002 17:04:03 Reading active file from archive via nnfolder...done
Jun 05 2002 17:04:03 Subscribe newsgroup: nnml:bugzilla
Jun 05 2002 17:04:03 2 new newsgroups have arrived
Jun 05 2002 17:04:03 Checking new news...
Jun 05 2002 17:04:03 Opening nndir server on /anex/mail.bk/backup...
Jun 05 2002 17:04:03 Opening nndir server on /anex/mail.bk/backup...done
Jun 05 2002 17:04:03 Opening nndraft server...
Jun 05 2002 17:04:03 Opening nndraft server...done
Jun 05 2002 17:04:03 Checking new news...done
Jun 05 2002 17:04:03 Parsing /home/reader/.mailrc...
Jun 05 2002 17:04:03 Parsing /home/reader/.mailrc... done
Jun 05 2002 17:04:03 Symbol's function definition is void: font-lock-unfontify-buffer
-- 

Re: Help tracing this error

[Paul Jarc]

reader@newsguy.com wrote:
> I get news and mail in a batch fetch.  I log its output to a log file.
...
> The output contains an error at the end that I cannot identify.
>
>   Jun 05 2002 17:04:03 Symbol's function definition is void:
>   font-lock-unfontify-buffer

Can you reproduce the error interactively?  If so,
toggle-debug-on-error.


paul

Re: Help tracing this error

[reader]

reader@newsguy.com writes:

> The output contains an error at the end that I cannot identify.
>
>   Jun 05 2002 17:04:03 Symbol's function definition is void:
>   font-lock-unfontify-buffer

Sorry about the noise, it turned out to be that I had kept a default
install of emacs 21.2 when installing a new OS (redhat 7.3).  Decided
to keep it on hand to compare to a newly installed cvs emacs.

Rpm installs with prefix=/usr  and the cvs is installed
prefix=/usr/local.   So to shorten the story, there existed some
shadow problems.  Not really sure what they were exactly but 
rpm -e (erase) of the rpm emacs packages cured it. 

Re: Help tracing this error

[reader]

prj@po.cwru.edu (Paul Jarc) writes:

> reader@newsguy.com wrote:
>> I get news and mail in a batch fetch.  I log its output to a log file.
> ...
>> The output contains an error at the end that I cannot identify.
>>
>>   Jun 05 2002 17:04:03 Symbol's function definition is void:
>>   font-lock-unfontify-buffer
>
> Can you reproduce the error interactively?  If so,
> toggle-debug-on-error.

No, an interactive fetch doesn't show it, but no need to pursue, it
turned out to be somekind of shadow problem arising from retaining a
default install of emacs (redhat rpm versioin 21.2) and installing a
cvs emacs in /usr/local.  Not sure of the details but removal of the
rpm packages has cured it.