Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Jarmo Hurri <jarmo.hurrigarbage@syk.fi>
To: info-gnus-english@gnu.org
Subject: Multiple nnfolder+archive instances
Date: Tue, 07 Sep 2010 17:28:11 +0300	[thread overview]
Message-ID: <m3sk1l1vd0.fsf@syk.fi> (raw)


Greetings.

After having updated my system to Fedora 13 I bumped into a new Gnus
problem.

I have the following archive settings in .gnus:

---------------------------------------------------------------------------
(setq gnus-message-archive-method
      '(nnfolder "archive"
	(nnfolder-directory (expand-file-name "~/Mail/archive"))
	(nnfolder-inhibit-expiry t)
	(nnfolder-active-file (expand-file-name "~/Mail/archive/active"))))
---------------------------------------------------------------------------

When I (try) to move a mail from my inbox into an archive (typing B m),
Gnus does the following:
1. If I have read or updated the archive folder so that Gnus knows its
   status exactly (e.g., # of messages is shown), then Gnus nicely moves
   the mail to the right archive.
2. Otherwise it complains that the archive file does not exists and
   tries to create a new one. This happens even though Gnus will happily
   auto-fill the right archive name with TAB, suggesting that Gnus knows
   the existence of the archive file. If I allow Gnus to create the new
   file, the new file is created into directory ~/Mail , not the
   specified directory ~/Mail/archive . After this I see two
   nnfolder+archive lines in the server mode (which is accessed from the
   Group buffer with ^). From one of these I can get two the new
   "archive" under ~/Mail , and from one to the old archive under
   ~/Mail/archive .

Any ideas on how to make Gnus understand that under no circumstances do
I want any archive files in ~/Mail ? I am running No Gnus v0.11.

-- 
Jarmo Hurri

Remove all garbage from header email address when replying, or just
use firstname.lastname@syk.fi .

                 reply	other threads:[~2010-09-07 14:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=m3sk1l1vd0.fsf@syk.fi \
    --to=jarmo.hurrigarbage@syk.fi \
    --cc=info-gnus-english@gnu.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).