Hi,
I tried to load my fileversion-4 database with the current cvs bbdb.
When I start up XEmacs-21.1 abd do M-x bbdb I get:
Symbols function definition is void: bbdb-migration-query
This can be resolved by loading the library bbdb-migrate
beforehand. Nevertheless bbdb-migration-query has a cor
On 14 Apr 2000, Colin Rafferty wrote:
> Sergei Pokrovsky writes:
>
> > That's an occasion to present my feature request. It would be
> > nice if the Supercite's attribution were a searchable key
> > field, like AKA.
> Colin> That's because I had a typo in my code. Here is the corr
Jack Twilley <[EMAIL PROTECTED]> writes:
> That leading 'to' does to, bcc, cc, and sender, according to the docs.
(Side note:) The `b' in bcc means blind. This means that the header
is removed before the mail is actually sent. Thus, you will never
receive a mail with a bcc header in it -- the
Sergei Pokrovsky writes:
>> ">Colin" == Colin Rafferty <[EMAIL PROTECTED]> writes:
Colin> Sergei Pokrovsky writes:
"Colin" == Colin Rafferty <[EMAIL PROTECTED]> writes:
Colin> Sergei Pokrovsky writes:
> That's an occasion to present my feature request. It would be
> nice if
> "Jack" == Jack Twilley <[EMAIL PROTECTED]> writes:
Jack>
Jack> My splits break up into fiveq groups -- warning/spam, 'good' spam,
Jack> lists, people and PBEM diplomacy. The first group is a special case,
Jack> and as such I'm not worried about it, as long as the request for it
Jack> can c
> ">Colin" == Colin Rafferty <[EMAIL PROTECTED]> writes:
>Colin> Sergei Pokrovsky writes:
>>> "Colin" == Colin Rafferty <[EMAIL PROTECTED]> writes:
Colin> Sergei Pokrovsky writes:
That's an occasion to present my feature request. It would be
nice if the Supercite's a
Sergei Pokrovsky writes:
>> "Colin" == Colin Rafferty <[EMAIL PROTECTED]> writes:
Colin> Sergei Pokrovsky writes:
>>> That's an occasion to present my feature request. It would be
>>> nice if the Supercite's attribution were a searchable key field,
>>> like AKA.
Colin> Assuming that the Sup
> "Colin" == Colin Rafferty <[EMAIL PROTECTED]> writes:
Colin> Sergei Pokrovsky writes:
>> That's an occasion to present my feature request. It would be
>> nice if the Supercite's attribution were a searchable key field,
>> like AKA.
Colin> Assuming that the Supercite field is "ci
> "Sergei" == Sergei Pokrovsky <[EMAIL PROTECTED]> writes:
Sergei> Some people address a mailing list in the Cc: field. So you
Sergei> need to split on "to\\|cc"; but normally you can split on
Sergei> "sender".
> Adrian Aichner <[EMAIL PROTECTED]> wrote:
APA> Yep, actually I used "to\\|
> "Sergei" == Sergei Pokrovsky <[EMAIL PROTECTED]> writes:
Sergei> Some people address a mailing list in the Cc: field. So
Sergei> you need to split on "to\\|cc"; but normally you can split
Sergei> on "sender".
> Adrian Aichner <[EMAIL PROTECTED]> wrote:
APA> Yep, actually I used "to\\|c
Sergei Pokrovsky writes:
> That's an occasion to present my feature request. It would be nice
> if the Supercite's attribution were a searchable key field, like AKA.
Assuming that the Supercite field is "cite" and the tag you are
looking for is "Phil":
M-x bbdb RET cite RET Phil
You can t
> "PR" == Peter Riocreux <[EMAIL PROTECTED]> writes:
PR> If we are talking wholesale reforms here, we ought to move away
PR> from the name being the primary index key first I would have
PR> thought, to allow multiple identical names in the DB.
This is or will be done shortly. It still
> "Pete" == Peter Riocreux <[EMAIL PROTECTED]> writes:
Pete> Too much of Jack Twilley's post to respond to, so I won't
Pete> quote. If we are talking wholesale reforms here, we ought to
Pete> move away from the name being the primary index key first I
Pete> would have thought, to all
Jack Twilley <[EMAIL PROTECTED]> writes:
> * Notes
>I wouldn't mind having a private section for notes here -- there's
>some things I wouldn't necessarily want stored in my pilot in a
>public record that may happen to be in a notes section, and this
>would mean the entire record
> "Sergei" == Sergei Pokrovsky <[EMAIL PROTECTED]> writes:
Sergei> Some people address a mailing list in the Cc: field. So
Sergei> you need to split on "to\\|cc"; but normally you can split
Sergei> on "sender".
Yep, actually I used "to\\|cc" thus far.
I learned about sender: ye
Too much of Jack Twilley's post to respond to, so I won't quote.
If we are talking wholesale reforms here, we ought to move away from
the name being the primary index key first I would have thought, to
allow multiple identical names in the DB. This could also allow BBDB
to prompt for new record c
16 matches
Mail list logo
