From: dave-mlist@bfnet.com
Subject: Can you use :prescript with maildir?
Date: 17 Jan 2003 17:36:48 -0800 [thread overview]
Message-ID: <m3bs2fck7j.fsf_-_@bfnet.com> (raw)
In-Reply-To: <m3lm1l21cq.fsf@defun.localdomain>
It doesn't work for me. I have the following in my .gnus:
(setq gnus-secondary-select-methods '((maildir :path "~/mail/Incoming/"
:prescript "/path/to/script-that-fetches-into-maildir")))
And this results in the following error:
Debugger entered--Lisp error: (wrong-type-argument sequencep :path)
gnus-read-active-file-1((maildir :path "~/mail/Incoming/" :prescript "echo 'poll a.mx.wuertele.com port 993 protocol IMAP username wuertele-com-test2 password fragfrag ssl' | fetchmail --nodetach -vv -n -f - -m '/usr/local/bin/maildir ~/mail/Incoming'") nil)
gnus-read-active-file(nil nil)
gnus-setup-news(nil nil nil)
byte-code("..." [dont-connect did-connect gnus-startup-file gnus-current-startup-file gnus-slave gnus-use-dribble-file gnus-group-quit gnus-run-hooks gnus-startup-hook gnus-make-newsrc-file gnus-dribble-read-file bbb-login add-hook gnus-summary-mode-hook gnus-grouplens-mode gnus-setup-news nil gnus-setup-news-hook gnus-start-draft-setup gnus-group-list-groups gnus-group-first-unread-group gnus-configure-windows group gnus-group-set-mode-line gnus-started-hook gnus-use-grouplens level] 4)
gnus-1(nil nil nil)
gnus(nil)
* call-interactively(gnus)
execute-extended-command(nil)
call-interactively(execute-extended-command)
It seems like it didn't like the :prescript being there after the path.
Dave
next prev parent reply other threads:[~2003-01-18 1:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 8:34 Can't print MIME part Kai Großjohann
2003-01-16 3:57 ` Jesper Harder
2003-01-16 7:53 ` Kai Großjohann
2003-01-17 5:22 ` Jesper Harder
2003-01-18 1:36 ` dave-mlist [this message]
2003-01-21 6:03 ` Can you use :prescript with maildir? Lars Magne Ingebrigtsen
2003-01-21 18:35 ` dave-mlist
2003-01-21 20:12 ` Kai Großjohann
2003-01-21 19:36 ` dave-mlist
2003-01-21 20:47 ` 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=m3bs2fck7j.fsf_-_@bfnet.com \
--to=dave-mlist@bfnet.com \
/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).