Gnus development mailing list
 help / color / mirror / Atom feed
From: lee <lee@yun.yagibdah.de>
To: ding@gnus.org
Subject: getting nndiary to work
Date: Wed, 22 Jun 2011 22:30:59 +0200	[thread overview]
Message-ID: <87wrgdk3r0.fsf@yun.yagibdah.de> (raw)

Hi,

I´m trying to get nndiary to work. I followed the documentation and put
settings for nndiary into ~/.gnus:


,----
| (add-to-list 'gnus-secondary-select-methods
| 	     '(nntp "news1.open-news-network.org")
| 	     '((nndiary "diary") (nndiary-get-new-mail t)))
| 
| (add-hook 'gnus-select-group-hook 'gnus-group-set-timestamp)
| ;;(setq nndiary-get-new-mail t)
| (setq nndiary-mail-sources '((file :path "~/.nndiary")))
| (setq nndiary-split-methods
|       '(("nndiary:diary"
| 	 "")))
| (setq nndiary-week-starts-on-monday t)
`----


After some searching, I found a posting saying that you need to create
the nndiary group manually. After creating it, I have a group
"nndiary:diary". When starting gnus, there´s a message in the minibuffer
about opening the nndiary server.

Unfortunately, nndiary doesn´t do anything. I can send myself nndiary
messages that do get delivered into ~/.nndiary, and nndiary seems to
ignore them. I can copy or move nndiary messages into the nndiary group
and it´s not any different from moving or copying messages to other
groups.

I can enter the group and view the messages just as with other
groups. When starting to write a mail while in the group, the nndiary
headers are inserted automatically.

What am I missing?



             reply	other threads:[~2011-06-22 20:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-22 20:30 lee [this message]
2011-06-23  7:35 ` Didier Verna
2011-06-23 11:21   ` Steinar Bang
2011-06-23 12:33     ` Didier Verna
2011-06-23 17:42       ` Steinar Bang
2011-06-23 18:53         ` Didier Verna
2011-06-23 18:56           ` Didier Verna
2011-06-23 22:21             ` lee
2011-06-23 18:46       ` lee
2011-06-23 19:08   ` lee

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=87wrgdk3r0.fsf@yun.yagibdah.de \
    --to=lee@yun.yagibdah.de \
    --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).