On 17 Apr 2011, Roland Winkler verbalised:
> On Sun Apr 17 2011 Nix wrote:
>> (Actually I went further and had it work for each message *for each
>> function*, so if you put it on the hook a dozen times it still only got
>> called once. But this is a useless and arguably con
On 17 Apr 2011, Roland Winkler spake thusly:
> On Sun Apr 17 2011 Nix wrote:
>> We could do the same job with a new hook which is called only once per
>> record, no matter how many times it is spotted by a given call to
>> bbdb-update-records, or with a new guarantee that
On 17 Apr 2011, Roland Winkler stated:
> On Sun Apr 17 2011 Nix wrote:
>> >> (I'll also see if bbdb-expire works with v3.0x and make it work if
>> >> it doesn't.)
>> >
>> > I believe this was some kind of add-on for BBDB.
>>
>>
On 17 Apr 2011, Roland Winkler told this:
> On Mon Apr 11 2011 Nix wrote:
>> (I'll also see if bbdb-expire works with v3.0x and make it work if
>> it doesn't.)
>
> I believe this was some kind of add-on for BBDB.
It was, making heavy use of advisements to do its
On 11 Apr 2011, Roland Winkler told this:
> - Finally, I fixed various bugs and improved the documentation.
I just noticed that BBDB development has restarted. Unfortunately
BBDB 3.0 has removed a good few features, including one I definitely
rely on: bbdb-canonicalize-net-hook, which is crucial t
On 14 Feb 2007, Len Trigg told this:
> * Allow bbdb-readonly-p to be a function that takes a record as a
> parameter, e.g.
This seems the most Lispish and most generic of approaches. (You'll
still want to allow it to be t-or-nil as well, of course.)
You'll need to do some extra work, because ma
On 13 Feb 2007, Len Trigg told this:
> I had a bit of a hack and this is what I came up with (bits were
> copied from the beginning of bbdb-annotate-message-sender). Basically
> it sets bbdb-readonly-p to true if there's a field called readonly
> associated with the record (if any). Please show m
On 25 Oct 2006, David Kågedal verbalised:
> Reiner Steib <[EMAIL PROTECTED]> writes:
>
>> For this scenario it would be nice to have an option allowing a
>> multi-line bbdb file format instead of the one-line-per-person format:
>
> I'd claim the opposite. The single-line format is ideal for CVS-st
On Sun, 05 Feb 2006, Adrian Aichner moaned:
> Dan Jacobson <[EMAIL PROTECTED]> writes:
>
>> This message is not understandable:
>> bbdb-complete-name: only exact matching record unhas net field
It's perfectly ordinary Newspeak. (There are `doubleplusungood's lurking
in there, too.)
> How about:
On Wed, 30 Mar 2005, Surendra Singhi mused:
> There might be duplicate entries in the Outlook and Netscape address books,
> will bbdb take care of removing such duplicates?
I don't know about the Outlook stuff, but `bbdb-show-duplicates' will
show you the dups so you can vape whichever one seems u
; the symptoms would have
been that something that should auto-update (last-accessed times,
add-only-once trackers, and so on) simply did nothing.
It should shortly appear in the usual place,
<http://www.esperi.demon.co.uk/nix/downloads/bbdb-expire-1.9.tar.gz>.
--
> ...Hires Root B
On Fri, 25 Feb 2005, Uwe Brauer prattled cheerily:
>> "Ted" == Ted Zlatanov <[EMAIL PROTECTED]> writes:
> Ted> Uwe: you should start reading the Emacs Lisp manual (usually
> Ted> reachable with C-h i, then select "Elisp") now.You are
> Ted> definitely ready for it :)
>
> Th
On Mon, 11 Oct 2004, Dan Jacobson stated:
> What to do when getting mail from
> From: "Brent Royal-Gordon via RT" <[EMAIL PROTECTED]>
> From: "Blob Dlobs bla bla via RT" <[EMAIL PROTECTED]>
> bbdb asks over and over about changing this and that.
> I was going to send you just what BBDB asked me, bu
On Tue, 3 Aug 2004, Ronan Waide said:
> On June 26, [EMAIL PROTECTED] said:
>> This is, IMHO, a bug in BBDB: if a record has a dozen addresses on it and
>> all dozen match some email you just read, the bbdb-notice-hook should
>> still only be called once for that message.
>
> It's not a bug, it's
On Mon, 02 Aug 2004, Uwe Brauer said:
> On 2 Aug 2004, [EMAIL PROTECTED] wrote:
>
>>
>> With the rise of the spam plague, I've been finding it difficult to
>> figure out how to configure BBDB's auto-address snarfing.
>>
>> My problem is the following: if I use bbdb-ignore-most-messages,
>> then I
On Fri, 02 Jul 2004, Dave Goldberg said:
>>>>>> On Fri, 02 Jul 2004 22:07:30 +0100, Nix <[EMAIL PROTECTED]> said:
>> There is none, as far as I can tell: the header structure used doesn't
>> store all headers, only some of them, and there's no way to
On Fri, 02 Jul 2004, Wes Hardaker stipulated:
>>>>>> On Fri, 02 Jul 2004 22:07:30 +0100, Nix <[EMAIL PROTECTED]> said:
>
> nix> There is none, as far as I can tell: the header structure used
> nix> doesn't store all headers, only some of them, and there
On Thu, 01 Jul 2004, Wes Hardaker yowled:
>>>>>> On Thu, 01 Jul 2004 21:43:18 +0100, Nix <[EMAIL PROTECTED]> said:
>
> nix> Alas, I can't do that: BBDB is triggered immediately *after* Gnus
> nix> prepares the article buffer and hides the headers, foll
On Fri, 02 Jul 2004, Alex Schroeder moaned:
> Nix <[EMAIL PROTECTED]> writes:
>
>> What I'd often like is for fields which are in the
>> gnus-ignore-header-alist to be dumped into the BBDB in some form
>> (particularly useful for face and x-face fields, where
On Thu, 1 Jul 2004, Ronan Waide spake:
> On June 30, [EMAIL PROTECTED] said:
>> I've been wading through the manual attempting to find the right hook, but
>> can't figure this out:
>> [adding context to records]
>
> This is pretty much what the BBDB is supposed to be all about. Check
> out the doc
On Sat, 26 Jun 2004, [EMAIL PROTECTED] moaned:
> I've just released
> <http://www.esperi.demon.co.uk/nix/downloads/bbdb-expire-1.7.tar.gz>,
... and again as of 1908 GMT; this one might actually work.
(oops.)
--
`We in no way believe that this Christ
match some email you just read, the bbdb-notice-hook should
still only be called once for that message.
I've just released
<http://www.esperi.demon.co.uk/nix/downloads/bbdb-expire-1.7.tar.gz>,
with a workaround for this bug, the feature you asked for (which I think
is nifty too), and so
On Tue, 22 Jun 2004, Jochen Küpper said:
> I attach the file I have around (and use), there might be newer
> versions.
Nope, that's the newest to date.
A tarball with readmes and such is available from
<http://www.esperi.demon.co.uk/nix/downloads/bbdb-expire-1.6.tar.gz>.
e mail archives for bbdb-expire to see the
>> discussion, and grab Nix's code here:
>> http://www.esperi.demon.co.uk/nix/
>
> Without looking at the code ... IMHO bbdb-expire does
> something different.
It does, but I've been meaning to extend it to handle expiry of *parts
On Wed, 30 Jul 2003, Ronan Waide moaned:
> On July 29, [EMAIL PROTECTED] said:
>> Yes, but that collides with caching sometimes (I hear; I use Gnus
>> so don't `benefit' from the caching).
>
> Not to be picky about it, but I'd prefer "it does" or "it doesn't"
> rather than "I hear". There's enough
On Tue, 29 Jul 2003, Ronan Waide moaned:
> One other thing that occurred to me that operates in this space is
> bbdb-notice-hook.
Yes, but that collides with caching sometimes (I hear; I use Gnus
so don't `benefit' from the caching).
--
`We cannot get a new line down the pipe due to a blockage a
he newsgroups
> line, I'd prefer it if it were to use the current group? or does it not
> know the group name?
Is there something in bbdb to do this automatically? I have
(defun nix-gnus-newsgroup-name (field)
"Get the current newsgroup name."
gnus-newsgroup-name)
(se
On Mon, 20 Jan 2003, Ronan Waide stated:
> It probably helps if you keep your BBDB file size down. I know that my
> own 400-odd entries parse pretty quickly, and to be honest I could
> probably prune it further.
400?
And I thought I was a pathetic no-hoper with no friends with 7000-odd
entries.
On 30 Oct 2002, Laura Conrad stated:
>> "sb" == Sridhar Boovaraghavan <[EMAIL PROTECTED]> writes:
>
> sb> For this reason, I have the following in my .emacs
>
> sb> (global-set-key (quote [C-tab]) (quote bbdb-complete-name))
>
> sb> Maybe needs a little getting used to, but works
same
thing --- I think it's the `display' property.)
The patch is rolled against the copy of bbdb in the XEmacs CVS repository,
hence the silly paths. Again, I'm happy to reroll if anyone thinks this
change is worthwhile.
2002-09-24 Nix <[EMAIL PROTECTED]>
* li
On Mon, 23 Sep 2002, Alex Schroeder spake:
> Mario Mommer <[EMAIL PROTECTED]> writes:
>
>> Maybe I misunderstood something, but... bbdb's usual modus operandi is
>> that it starts gathering information, like when I'm reading e-mail it
>> saves the addresses, etc. Am I right on this?
>
> No, the
On Tue, 17 Sep 2002, Ronan Waide yowled:
> On September 17, [EMAIL PROTECTED] said:
>>
>> *cheer*
>>
>> And my last local patch bites the dust...
>
> You had a local patch? Can't see it in my mail queue... I'm not
> psychic, you know ;)
It was much too crap to submit; it didn't bother catering
On Tue, 17 Sep 2002, Ronan Waide said:
> Hi folks,
>
> I'm finally doing something about the above to make it an actual
> hook. I've just commited code that converts it from a single function
> to a hook list on-the-fly before using run-hooks on it, and it seems
> to be working okay.
*cheer*
An
On Thu, 22 Aug 2002, Jack Twilley stated:
> I'd like to remove the last-access field from all records currently in
> my bbdb. What's the best way to do that?
(watch: the users desert! ;} )
I'd do something like
(mapc
#'(lambda (record)
(bbdb-record-putprop record 'last-access nil))
(bbd
On Wed, 29 May 2002, Kai said:
> Nix <[EMAIL PROTECTED]> writes:
>
>> I don't know whether this matters here, but XEmacs doesn't respect
>> coding tags (and never will, IIRC: the XEmacs developers hate them).
>
> Amazing.
Er, sorry, I misremembered
On Tue, 28 May 2002, Kai moaned:
> When reading, have BBDB apply the normal Emacs machinery for decoding
> the file contents. Take note of any "coding:" tag in the file. If it
> is there, just preserve it on write. But if there is no "coding:"
> tag, invoke the migration machinery as follows:
emner.
Bug fixes against bbdb-expire 1.5:
- bbdb-expire now actually calls the function that updates the
`bbdb-display-layout-alist'. (Whoops.)
The code is available at
<http://www.esperi.demon.co.uk/nix/downloads/bbdb-expire-1.6.tar.gz>.
--
`Unless they've moved it since I last
bbdb-com.el fsets a bunch of stuff inside an `eval-when-compile';
unfortunately, this is of little use, because while fset calls are
byte-compiled, these aren't, so the file byte-compiles without error and
then falls over at runtime.
Patch:
2002-01-29 Nix <[EMAIL PROTECTED]>
here to get it from. Serves me right for doing announcements at 2am...
If any confused people are reading this far down, bbdb-expire's
available from the usual place, <http://www.esperi.demon.co.uk/nix/>.
Oops.)
--
`However, if you want to detect whether (say, 1 in 1000) cars are being
It's that time again, for yet another version of the flexible expiry
package for overfull BBDB databases.
This is pretty much unchanged functionality-wise since the 1.4 release.
The release has had entire minutes of testing, but it's going to work
better with BBDB-2.34 than the last release did.
On Fri, 18 Jan 2002, Robert Fenk stipulated:
> But you can interrupt BBDB during formatting which results
> in a "corrupt" *BBDB* buffer.
Well, you could bind inhibit-quit, but that might annoy users more than
slightly (as C-g is supposed to *always* work; binding inhibit-quit for
a long time is
On Tue, 01 Jan 2002, Chris Beggy stated:
> Nix <[EMAIL PROTECTED]> writes:
>
>> I wish it could auto-expire, but alas, by the time it can hook into the
>> bbdb, it is too late for automatic expiry, as we're inside
>> `bbdb-records', which forbids r
On Sat, 29 Dec 2001, Chris Beggy stipulated:
> bbdb-expire helps to auto-expire non-permanent, not recently
> accessed records:
I wish it could auto-expire, but alas, by the time it can hook into the
bbdb, it is too late for automatic expiry, as we're inside
`bbdb-records', which forbids recursio
On 06 Nov 2001, [EMAIL PROTECTED] stated:
> On Tue, 6 Nov 2001, Ronan Waide gibbered:
>> On November 6, [EMAIL PROTECTED] said:
>>> This one is Gnus-related; it comes and goes seemingly at random. It
>>> turns up when populating a Summary buffer in Gnus:
>>
>> Two things:
>>
>> 1. does it happen
On Mon, 19 Nov 2001, Kai Großjohann stipulated:
> Note that different patch installations seem to use
> different default values for "-p". So on some installations, "patch
> < foo" is the same as "patch -p0 < foo", whereas on others, it's
> "patch -p1 < foo". Strange. So maybe you jus
On Mon, 6 Aug 2001, Colin Rafferty spake:
> Robert Fenk wrote:
>> bbdb-one-line-display-fields (bbdb-elided-display-fields)
>> list of fields which should be displayed in one-line display
>
> This is the exact opposite of the -elided- version, and a bad choice.
> If I add a new field interac
On Fri, 03 Aug 2001, David S. Goldberg gibbered:
> DG> I want a full listing, in multiple lines, minus a couple fields.
> DG> Robert's patch does this. bbdb-elided-display does not.
>
>> Yes, it does...
>
> Thanks! Is that new in the 2.3* versions? I don't recall that being
> possible p
On Tue, 31 Jul 2001, Alex Schroeder spake:
> Doug Alcorn <[EMAIL PROTECTED]> writes:
>
>> Is there any way to have an alist of fields to display or fields to
>> ignore? Maybe something with the elided display? How does all that
>> work?
>
> Here's an example from my .emacs:
>
> (setq bbdb-pri
hange recording too. But I don't think the method I've used to do that
is too terribly ugly, maybe, perhaps.)
ChangeLog entry for this change:
2001-07-18 Nix <[EMAIL PROTECTED]>
* lisp/bbdb.el (bbdb-suppress-changed-records-recording): New variable.
(bbdb-delete-
ation-functions'.
There is a macro `bbdb-expire-field-foo-p' which creates predicates to put
on these hooks to force expiry or preservation if specific fields are
present.
- Records with a "notes" field are no longer expired.
The code is available at
<http://www
On 04 May 2001, Colin Rafferty said:
> On the other hand, I remember someone posting a module that had a
> 'last-seen field, that only got filled in if it popped up because of
> VM or Gnus. This avoids the Heisenberg problem.
Yep (but it's called `last-accessed').
I've at *last* got around to g
On 07 Apr 2001, Jack Twilley yowled:
> One of the posters to one of my favorite newsgroups has an annoying
> approach to antispam. Here's his bbdb record:
>
> Dan Birchall
> net: [EMAIL PROTECTED], [EMAIL PROTECTED],
>[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED],
>[EMAIL
On 26 Feb 2001, Daniel Pittman gibbered:
> On 26 Feb 2001, [EMAIL PROTECTED] wrote:
>> On 26 Feb 2001, Daniel Pittman yowled:
>>> So, I would suggest that, for this one file, you make an exception.
>>> It
>>
>> You get lots of CVS conflicts if you do this, in my experience.
>
> The rest of the
On Sun, 25 Feb 2001, Ronan Waide stipulated:
> Ah, my bad. `Nix' has a chunk of code called BBDB expire which will
> nuke items from your BBDB that are 'not in use' for a period of time,
> which might help. However, it's not been ported to BBDB 2.2.
It has now; I&#x
On 26 Feb 2001, Daniel Pittman yowled:
> So, I would suggest that, for this one file, you make an exception. It
You get lots of CVS conflicts if you do this, in my experience.
Require testers to have autoconf installed, and provide a little shell
script (conventionally called `bootstrap' or `aut
On Sun, 25 Feb 2001, Ronan Waide stated:
> Well, no. I tend to work on the idea that the crud shouldn't get in
> there in the first place. I have a hook that checks that the mail is
> actually addressed to me, which catches a whole bunch of spam, and
> then a fairly well-defined filter list that c
On Fri, 23 Feb 2001, Ronan Waide spake:
>are simply "does it not break anything" and "is it useful".
Does `cleaning up the unreadable ugly crap' count as `useful'? We all
know that BBDB has quite a lot of that (although it has nothing anywhere
near as bad as `c-guess-basic-syntax' in cc-mode,
On Wed, 21 Feb 2001, Ronan Waide stated:
> That's correct, nor do I want one. I do my best to keep all manner of
> crud out of my bbdb!
I *must* get that BBDB expiry hack updated for BBDB-2.2 so you don't
have to do that anymore...
--
`I put "Update To-Do List" on my to-do list. I'm never sure
On Wed, 21 Feb 2001, Ronan Waide stated:
> On February 20, [EMAIL PROTECTED] said:
>> Would you want the behaviour of your XEmacs to change just because you
>> looked at a menu --- didn't do anything there, mind you, just looked at
>> it?
>>
>> Hence the policy.
>
> Right, and policies are fine
On Mon, 19 Feb 2001, Ronan Waide said:
> On February 19, [EMAIL PROTECTED] said:
>> GNU Emacs "official philosophy" is that "loading a file should not
>> change Emacs' behaviour". Maybe we could comply with it by removing
>>
>> (add-hook 'bbdb-list-hook 'bbdb-fontify-buffer)
>>
>> from
On 23 Jan 2001, Didier Verna gibbered:
>| cvs update: move away bits/bbdb-filters/COPYING.LIB; it is in the way
This is a client issue, not a server-side one. (Rare, really; most of
the annoyances I get with CVS crop up on the server, where mortals
cannot fix them. I've never had any problems wit
Ronan Waide <[EMAIL PROTECTED]> writes:
> On October 28, [EMAIL PROTECTED] said:
> > that should be useful; does the bleeding-edge BBDB implement this yet?
> > If it does I'll pull it down and rewrite the BBDB expiry and sorting
> > code for it.
>
> I'd appreciate if you could code the bbdb-expi
Sam Steingold <[EMAIL PROTECTED]> writes:
> > OBARRAY_SIZE is 16411 in XEmacs, which is more than large enough; but
> > I hear that it is only 1511 in GNU Emacs, so you'll be having some
> > overhead for bucket searching with a 6000-element db on GNU Emacs.
>
> both XEmacs 21 and Emacs 21 have n
Ernst Taumberger <[EMAIL PROTECTED]> writes:
> I have a bbdb file with more than 2000 entries and I don't see any slow down
> in the use of bbdb (I added the bulk of it in one go -- imported company
> phonebook).
You won't see it for some time; the bbdb-hashtable is an obarray, so
lookup of entr
ere is the new bbdb-expire.el:
;;; bbdb-expire.el --- expiry and expire-proof entries for the BBDB
;;; Copyright (C) 2000 Nix <[EMAIL PROTECTED]>.
;; Author: Nix <[EMAIL PROTECTED]>
;; Created: 2000-09-17
;; Last modified: 2000-10-28
;; Keywords: mail news
;; Version: $Revision: 1.3
Nix <[EMAIL PROTECTED]> writes:
> Benjamin Rutt <[EMAIL PROTECTED]> writes:
>
> > Well thanks everyone for the responses. Nix, I'll wait for your
> > generically kludgy machinery to play with the additional bbdb fields,
> > (I'll be eagerly monitor
Benjamin Rutt <[EMAIL PROTECTED]> writes:
> Well thanks everyone for the responses. Nix, I'll wait for your
> generically kludgy machinery to play with the additional bbdb fields,
> (I'll be eagerly monitoring gnu.emacs.sources :)) and I'll take a look
I'
[EMAIL PROTECTED] (David S. Goldberg) writes:
> Ask yourself: "of all the addresses I am automatically snarfing, what
> percentage do I really want to keep?" If that number is low, then
> turn off automatic snarfing of addresses and just add the ones you
> want by hand (in gnus type a colon (:)
The docstring for `bbdb-notice-hook' states
,
| Also note that bbdb-change-hook will NOT be called as a result of any
| modifications you may make to the record inside this hook.
`
As far as I can see, this is incorrect. It *should* be correct, because
it is very annoying to have the cha
Nix <[EMAIL PROTECTED]> writes:
>the notice hook gets called a
> lot --- e.g., when updating records, as well as when looking at them,
No, it doesn't. Oops. (It even explicitly mentions that case in the
docstring.)
--
`Normally, we
hear from infrequently are near the end
> (where "frequent" is defined as how often bbdb notices the net
> address). That way, it will still be useful to browse the bbdb.
H *thinks*
> Any suggestions here? Is there any way to specify the sort order of
> bbdb recor
A new, more flexible version of the BBDB expiry hack `expire-bbdb.el'
has just been posted to gnu.emacs.sources.
You can now choose to expire records, and preserve records through
expiry, in arbitrarily complex ways; thanks to Toby Speight for the idea.
--
`Normally, we don't do people's homew
Nix <[EMAIL PROTECTED]> writes:
> (add-hook 'bbdb-mode-hook 'bbdb-expire-bbdb)
Oops.
Dump this, unless you like having your bbdb expired between each article
you read.
Is there a variant of `bbdb-after-read-db-hook' that is *not* called
from within `bbdb-records'
-- begin
;;; expire-bbdb.el --- expiry and expire-proof entries for the BBDB
;;; Copyright (C) 2000 Nix <[EMAIL PROTECTED]>.
;; Author: Nix <[EMAIL PROTECTED]>
;; Created: 2000-09-17
;; Keywords: lisp
;; Version: $Revision$
;; This file is not part of XEmacs.
;; This library is free softw
74 matches
Mail list logo
