Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Cc: ding@gnus.org
Subject: [bbdb]Give me a break..
Date: 12 Jul 2000 07:29:12 -0700	[thread overview]
Message-ID: <m2vgybe81z.fsf@reader.ptw.com> (raw)


[posted to bbdb list and ding list because of the many knowledgable
bbdb users on ding]

I've updated from bbdb-2.00.06 in an effort to get clear away from
bbdb's nasty habit of gabbing incessantly about mismatched names.
I've reset:
 (setq bbdb-quiet-about-name-mismatches t)  from t to nil / nil to t
approximately  572 times : ).  bbdb refuses to just shut up.

So upgraded to bbdb-2.2  Still the incessant blabber but worse, if I
try to search for something by pressing:
M-x bbdb <RET> and giving a string  I only get:
 
  Wrong type argument: stringp, 49

This is after saying yes to the initial prompt that asks if I want to
update my database to the new format.

Fortunately I saved the original .bbdb so can return to the old format.

I'm retreating to 2.00 but would like some code that silences bbdbs
blabbering.

I don't want to know about mismatched names, mismatched addresses or
any kind of mismatch.  Nor when or what bbdb is `frobnicating', or any
other of bbdb's (hyper) activities unless I ask about it.

I don't want a pause when opening messages as bbdb makes corrections
it thinks I need.   I want to make that decision.  Bbdb is over active
in my opinion and a constant source of aggravation with various pauses
etc.

The defaults should be resounding silence unless a variable like:

`bbdb-nag-me-until-I-would-rather-set-my-hair-on-fire-than-start-bbdb'

Is set to `t' by the user.




             reply	other threads:[~2000-07-12 14:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-12 14:29 Harry Putnam [this message]
2000-07-14 12:22 ` Ronan Waide
2000-07-14 13:43   ` Ronan Waide

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=m2vgybe81z.fsf@reader.ptw.com \
    --to=reader@newsguy.com \
    --cc=ding@gnus.org \
    /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).