From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: registry question
Date: 5 Nov 2004 11:17:17 -0500 [thread overview]
Message-ID: <4nis8kl182.fsf@lifelogs.com> (raw)
In-Reply-To: <76bredegn4.fsf@newjersey.ppllc.com> (Jake Colman's message of "Thu, 04 Nov 2004 11:13:51 -0500")
On Thu, 04 Nov 2004, colman@ppllc.com wrote:
> I use the gnus registry as a convenient way of having replies filed in the
> same folder to which the original email was filed. This works alot of the
> time, not all of the time, and I've never worried much about it.
>
> I also use 'gnus-message-archive-group' which adds a gcc to the
> message header so that all outgoing email is filed in an archive
> folder. I just discovered than an incoming reply was auto-filed
> into the archive folder for the outgoing email. This has never
> happened before (AFAIK) and is NOT something I want. The archive
> folder is just used so that I track what I sent. I really only want
> the registry to track messages that I either manually move somewhere
> or, more typically, for folders for which I have a manual gcc-self
> setting.
Maybe gnus-registry-ignored-groups will help?
I haven't had the time to write a manual section on the registry, sorry.
Ted
next prev parent reply other threads:[~2004-11-05 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 16:13 Jake Colman
2004-11-05 16:17 ` Ted Zlatanov [this message]
2004-11-05 20:31 ` Jake Colman
2004-11-16 21:49 ` Ted Zlatanov
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=4nis8kl182.fsf@lifelogs.com \
--to=tzz@lifelogs.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).