From: Lars Tobias Borsting <larstobi@idi.ntnu.no>
Subject: Re: How to use own newer version of gnus at $HOME
Date: 03 May 2004 13:38:37 +0200 [thread overview]
Message-ID: <8jfoep54u6a.fsf@eos.idi.ntnu.no> (raw)
In-Reply-To: <87pt9mudyy.fsf@naia.homelinux.net>
Chris Hall <hall.cj@verizon.net> writes:
> I use fetchmail piped to procmail *outside* of Emacs, and have procmail
> split my mail into separate groups, so I'm not using an Emacs-related
> program, but from recent reading of the Gnus Info (I just last week set
> all this up under Gnus 5.10), I think that the default program is
> supplied by Emacs, and called 'movemail', oddly enough ;-). If you are
> on an *nix box, 'which movemail' or 'locate movemail' might help.
OK, thanks! Somehow it just worked after changing my mail source from
maildir to mbox format. I guess the gnus nnml-backend v5.10 had problems
with the source being in maildir format.
One other strange thing though, if I remove the files from
$HOME/Mail/mail/misc/ and move in mail from my gnus v5.6 after using the
directory with v5.10, the Summary Buffer still displays the new list of
articles/mails. That is kinda strange, because I just deleted them and
replaced them with some other ones, it must hence be cached somewhere.
Where does gnus store its Summary Buffer cache? I haven't been able to
locate where it caches the mail summary. And how can I force gnus to
re-read the folder and generate a new Summary Buffer?
Regards,
Lars Tobias Borsting
prev parent reply other threads:[~2004-05-03 11:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8jfekq8jd21.fsf@kamel.stud.ntnu.no>
[not found] ` <m3oepcm40w.fsf@defun.localdomain>
[not found] ` <8jfhdv3w3gk.fsf@kamel.stud.ntnu.no>
2004-04-30 1:15 ` Jesper Harder
[not found] ` <8jfpt9pjx0i.fsf@kamel.stud.ntnu.no>
2004-05-01 12:40 ` Jesper Harder
2004-05-01 19:30 ` Lars Tobias Borsting
2004-05-03 8:12 ` Chris Hall
2004-05-03 11:38 ` Lars Tobias Borsting [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=8jfoep54u6a.fsf@eos.idi.ntnu.no \
--to=larstobi@idi.ntnu.no \
/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).