Gnus development mailing list
 help / color / mirror / Atom feed
From: Yagnesh Raghava Yakkala <hi@yagnesh.org>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: Katsumi Yamaoka <yamaoka@jpl.org>,  ding@gnus.org
Subject: Re: gnus downloading mails from pop again and again.
Date: Tue, 13 Aug 2013 11:07:39 +0900	[thread overview]
Message-ID: <87vc3az6l0.fsf@yagnesh.org> (raw)
In-Reply-To: <87fvuel6t8.fsf@yagnesh.org> (Yagnesh Raghava Yakkala's message of "Tue, 13 Aug 2013 10:26:27 +0900")


Hello Lars,

More info.

On Aug 13 2013, Yagnesh Raghava Yakkala <hi@yagnesh.org> wrote:

> Hello Lars,
>
> Thanks for the reply.
>
> On Aug 13 2013, Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
>
>> Yagnesh Raghava Yakkala <hi@yagnesh.org> writes:
>>
>>> │Mail source (pop :server pop.hines.hokudai.ac.jp :user XXXXX :leave
>>> 14) failed: (file-error Opening output file no such file or directory
>>> /home/yagnesh/Mail/Incoming117956Yf)
>>
>> Well, that's the error.  It's either not able to create or read files
>> from your ~/Mail directory.  
>
> 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")
> ╰─────
>
> So why gnus looking into ~/Mail directory now.? :/


So I created ~/Mail directory to see what will happen. Now gnus showing is
showing all it processed (lots of duplicates for each mail as unread mail) for
the last 2/3 days incoming mails.

Is there any option in gnus to hunt down all the duplicates?


And also I noticed that,

╭─────┤ C-h v gnus-article-save-directory RET ├─────
│gnus-article-save-directory is a variable defined in `gnus.el'.
│Its value is "~/News/"
│Original value was "~/gnus/News"
╰─────

The variable initialized properly but some where it get updated (bad code?).
In elisp, is it possible to get an echo of the location where a variable gets
updated (some kind of advise function)?

Seems I going against the wind, I should better stick with default ~/News and
~/Mail.

Sorry for long and verbose mail(s).

Thanks.,
-- 
ఎందరో మహానుభావులు అందరికి వందనములు.
YYR



  reply	other threads:[~2013-08-13  2:07 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 [this message]
2013-08-13  3:33                     ` Katsumi Yamaoka
2013-08-13  3:51                       ` Eric Abrahamsen
2013-08-15  8:34                       ` Yagnesh Raghava Yakkala

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=87vc3az6l0.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).