I just checked and without my inelegant makunbound solution, I get the
same error running with FSF-19 in either tty or X11 mode.
Rick
> "rb" == Rick Busdiecker <[EMAIL PROTECTED]> writes:
rb> Not true. BBDB can deal with gnus 4.1. I use it all the
rb> time.
I don't know if this is the same problem, but anyway...
I get the same error message from bbdb-gnus, but ONLY when I start
EMACS in text mode. In graphics mo
Date: Fri, 22 Apr 94 13:11:30 EDT
From: [EMAIL PROTECTED] (Paul Smith)
Actually, technically this has nothing to do with V19 Emacs; it just so
happens that V19 Emacs ships the newest version of GNUS, which has these
changes, and BBDB is still written to use the older versi
%% Regarding bbdb and fsf19;
%% [EMAIL PROTECTED] (William Murphy) writes:
wm> not easy at all. just another one of those headaches that won't
wm> go away as of v19 our friend RS has decided that he likes
wm> change. you will note that gnus gnus-Subject-* is no
> "Rick" == Rick Busdiecker <[EMAIL PROTECTED]> writes:
Rick> Signalling: (void-variable gnus-Subject-mode-map)
All uppercase words in GNUS have been converted to lowercase in 4.x.
Furthermore, gnus-Subject-* has been changed to gnus-summary-*.
\||| | | | | | | | | ||||
not easy at all. just another one of those headaches that won't go away
as of v19 our friend RS has decided that he likes change. you will
note that gnus gnus-Subject-* is now gnus-summary-*. this causes all sorts
of joy. :)
if you have two versions of emacs you need two versions of bbdb
Bill
From: Rick Busdiecker <[EMAIL PROTECTED]>
Date: Fri, 22 Apr 1994 10:56:53 -0400
If anyone knows of an incredibly easy and trivial way for me to
get past this hurdle, I'd appreciate it.
Well, you dolt, you could try making sure that
gnus-Article-prepare-hook isn't bound.
So,
I've been using fsf18 when I hack from home because I don't have an X
screen at home and I use lemacs (no tty support) at work and because
whenever I've tried to switch to fsf19 at home it's been a big
headache trying to get all of my customizations in line.
Anyway . . . I'm once again trying to
