From: Johnny <yggdrasil@gmx.co.uk>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: ding@gnus.org
Subject: Re: BBDB integration - add sender in Summary buffer
Date: Thu, 16 Dec 2010 20:27:45 +0000 [thread overview]
Message-ID: <878vzpsbsu.fsf@gmx.co.uk> (raw)
In-Reply-To: <87sjxxwlea.fsf@member.fsf.org> (Tassilo Horn's message of "Thu, 16 Dec 2010 20:46:53 +0100")
Tassilo Horn <tassilo@member.fsf.org> writes:
> I'm using it that way, too.
Ok, maybe I got some concepts almost right after all ...
>
> I don't even have that variable!
I am pretty sure this is identical to bbdb-ignore-most-messages-alist.
>
> Ah, I see. Then I cannot help you, sorry.
>
I am not sure the issue is the version, alas it could be... Thanks anyhow!
--
Johnny
next prev parent reply other threads:[~2010-12-16 20:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 17:57 Johnny
2010-12-16 18:43 ` Tassilo Horn
2010-12-16 19:43 ` Johnny
2010-12-16 19:46 ` Tassilo Horn
2010-12-16 20:27 ` Johnny [this message]
2010-12-16 21:10 ` Tassilo Horn
2010-12-16 21:29 ` Ted Zlatanov
2010-12-17 7:01 ` Tassilo Horn
[not found] ` <qh62uta46w.fsf@news.eternal-september.org>
2010-12-16 20:50 ` Johnny
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=878vzpsbsu.fsf@gmx.co.uk \
--to=yggdrasil@gmx.co.uk \
--cc=ding@gnus.org \
--cc=tassilo@member.fsf.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).