From: Richard Riley <rileyrg@googlemail.com>
To: nognus <ding@gnus.org>
Subject: Errors with archive methods
Date: Sat, 26 Mar 2011 10:21:59 +0100 [thread overview]
Message-ID: <7xvcz6dyo8.fsf@news.eternal-september.org> (raw)
I finally decided to see if I could get rid of the the ~/Mail link which
links to my "real" Mail in ~/.emacs.d
I had my suspicions it was linked to archiving.
Reading the manual I see I can specifiy the archive method thus:-
,----
| gnus-message-archive-method is a variable defined in `gnus.el'.
| Its value is (nnfolder "archive"
| (nnfolder-inhibit-expiry t)
| (nnfolder-active-file "~/.emacs.d/Mail/archive/active")
| (nnfolder-directory "~/.emacs.d/Mail/archive/"))
|
| Original value was "archive"
`----
From my understanding the original value of "archive" expands to
,----
|
| (nnfolder "archive"
| (nnfolder-directory "~/Mail/archive")
| (nnfolder-active-file "~/Mail/archive/active")
| (nnfolder-get-new-mail nil)
| (nnfolder-inhibit-expiry t))
`----
(is ~/Mail really hardcoded? As opposed to being based on the
gnus-directory setting which I have set to ~/.emacs.d ?)
My value of gnus-method-group is
,----
| gnus-message-archive-group is a variable defined in `gnus.el'.
| Its value is ((if
| (message-news-p)
| nil
| (concat "mail-"
| (format-time-string "%Y"))))
`----
When I try to send an email plugged or unplugged I get this backtrace
,----
| Debugger entered--Lisp error: (wrong-type-argument stringp nil)
| file-name-as-directory(nil)
| nnheader-concat(nil "active")
| (defvar nnfolder-active-file (nnheader-concat nnfolder-directory "active") ("/home/shamrock/.emacs.d/nognus/lisp/nnfolder.elc" . 1827))
| require(nnfolder)
| gnus-server-opened((nnfolder "archive" (nnfolder-inhibit-expiry t) (nnfolder-active-file "~/.emacs.d/Mail/archive/active") (nnfolder-directory "~/.emacs.d/Mail/archive/")))
| gnus-check-server((nnfolder "archive" (nnfolder-inhibit-expiry t) (nnfolder-active-file "~/.emacs.d/Mail/archive/active") (nnfolder-directory "~/.emacs.d/Mail/archive/")))
| gnus-inews-do-gcc()
| gnus-agent-possibly-do-gcc()
| run-hooks(message-sent-hook)
| message-send(nil)
| message-send-and-exit(nil)
| call-interactively(message-send-and-exit nil nil)
`----
Something obvious?
regards
r.
--
☘ http://www.shamrockirishbar.com, http://splash-of-open-sauce.blogspot.com/ http://www.richardriley.net
next reply other threads:[~2011-03-26 9:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-26 9:21 Richard Riley [this message]
2011-03-26 10:31 ` Antoine Levitt
2011-03-28 16:40 ` SOLVED " Richard Riley
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=7xvcz6dyo8.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).