From: Yagnesh Raghava Yakkala <hi@yagnesh.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>, ding@gnus.org
Subject: Re: gnus downloading mails from pop again and again.
Date: Thu, 15 Aug 2013 17:34:45 +0900 [thread overview]
Message-ID: <87haerxsgq.fsf@yagnesh.org> (raw)
In-Reply-To: <b4mpptiqn7s.fsf@jpl.org>
Hello Yamaoka-san,
On Aug 13 2013, Katsumi Yamaoka <yamaoka@jpl.org> wrote:
> Yagnesh Raghava Yakkala <hi@yagnesh.org> wrote:
>> Ouch. I don't have "~/Mail" at all. I intentionally deleted that
>> long time ago.
>> I have following setup in my .emacs to make use of "~/gnus" folder
>> for all my mail/news.
>
>> ╭─────
>> │(setq gnus-home-directory "~/gnus")
>> │(setq gnus-startup-file "~/gnus/.newsrc")
>> │(setq gnus-directory "~/gnus/News")
>> │(setq message-directory "~/gnus/Mail")
>> ╰─────
>
> Are those setq's really in the ~/.emacs file?
Hmm.. actually not. They were in .gnus.el file.
>
>> So why gnus looking into ~/Mail directory now.? :/
>
> When fetching mails, the value of `mail-source-directory' will
> be used as the mail directory. It defaults to the value of
> `message-directory' (defaults to "~/Mail/"); the value you
> customized will be reflected if and only if it is set in
> the ~/.emacs file and no Gnus' el(c) module is loaded before it
> is set.
Thats it, Thanks. after all, I see, it is already mentioned in doc of
`gnus-directory' variable.
> A workaround may be:
> (setq mail-source-directory "~/gnus/Mail/")
>
> But I don't recommend customizing such variables of Gnus' basic.
> I think it may cause an unexpected influence that even the author
> doesn't know. :)
After moving relevant parts from .gnus.el to .emacs, Every thing seems work
fine. I will keep the current way. I will follow if I hit any problem again.
Thanks for help.
--
ఎందరో మహానుభావులు అందరికి వందనములు.
YYR
prev parent reply other threads:[~2013-08-15 8:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 6:32 Yagnesh Raghava Yakkala
2013-08-12 0:33 ` Katsumi Yamaoka
2013-08-12 1:21 ` Katsumi Yamaoka
2013-08-12 2:13 ` Yagnesh Raghava Yakkala
2013-08-12 2:39 ` Yagnesh Raghava Yakkala
2013-08-12 2:43 ` Yagnesh Raghava Yakkala
2013-08-12 3:49 ` Katsumi Yamaoka
2013-08-12 5:21 ` Yagnesh Raghava Yakkala
2013-08-12 14:10 ` Yagnesh Raghava Yakkala
2013-08-12 17:12 ` Lars Magne Ingebrigtsen
2013-08-13 1:26 ` Yagnesh Raghava Yakkala
2013-08-13 2:07 ` Yagnesh Raghava Yakkala
2013-08-13 3:33 ` Katsumi Yamaoka
2013-08-13 3:51 ` Eric Abrahamsen
2013-08-15 8:34 ` Yagnesh Raghava Yakkala [this message]
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=87haerxsgq.fsf@yagnesh.org \
--to=hi@yagnesh.org \
--cc=ding@gnus.org \
--cc=larsi@gnus.org \
--cc=yamaoka@jpl.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).