Gnus development mailing list
 help / color / mirror / Atom feed
From: Richard Riley <rileyrg@googlemail.com>
To: nognus <ding@gnus.org>
Subject: Errors installing a clean gnus setup
Date: Sun, 27 Mar 2011 17:50:00 +0200	[thread overview]
Message-ID: <ukd3lc36mv.fsf@news.eternal-september.org> (raw)


I decided to bin my .newsrc.eld as it (a) huge and (b) suspect in some
funny article handling (c) editing it with emacs was impossible since
the article count alist thingy is a single line and takes about 3-6
seconds to cursor down a visual line.  At the same time I removed all
custom settings for things like archive methods, archive backend etc
ditto for drafts.

My init settings for file locations are pretty much the following

 (setq gnus-init-file nil
        gnus-home-directory "~/.emacs.d/"
        mail-default-directory "~/.emacs.d/"
        message-directory "~/.emacs.d/Mail/"
        )
 
which I borrowed from Antoine.

I removed all old draft, archive and Mail directories assuming gnus
would create them as defaults.

Upon starting Gnus afresh I got this:-

1) Drafts

Warning: Opening nndraft server...failed: No such file or directory: ~/.emacs.d/drafts/; Denied server nndraft

So it seems to fail to create the draft directory itself. I then looked into my
server list and get this:-

 
,----
|    {nndraft:} (denied)
`----

Hmm. I then looked into my .emacs.d and Gnus *had* created
~/.emacs.d/drafts. But *after* issuing the failure messages and denying
access it seems. I would think this a bug?

2) Archive

,----
|    {nnfolder:archive} (error)
`----

There is no indication of why the archive failed even if I turn up
gnus-verbose.

This is using the default gnus-message-archive-group and default
gnus-message-archive-method.
  
This was the case with HEAD and n0-15.

Can I debug this further somehow? 



             reply	other threads:[~2011-03-27 15:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-27 15:50 Richard Riley [this message]
2011-03-29 17:46 ` Lars Magne Ingebrigtsen

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=ukd3lc36mv.fsf@news.eternal-september.org \
    --to=rileyrg@googlemail.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).