Gnus development mailing list
 help / color / mirror / Atom feed
From: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: ding@gnus.org
Subject: Re: road warrior trying to simplify a mail setup
Date: 07 Feb 2003 07:44:54 -0800	[thread overview]
Message-ID: <86smv02iyx.fsf@red.stonehenge.com> (raw)
In-Reply-To: <uhebgv4q5.fsf@axis.com>

>>>>> "Niklas" == Niklas Morberg <niklas.morberg@axis.com> writes:

Niklas> I use gnus for this. Emacs and gnus are always up and running
Niklas> on my constantly connected office machine. I then use the
Niklas> deamon functionality in gnus to get new mails (and do some
Niklas> other stuff):

Niklas>   (gnus-demon-add-handler 'gnus-group-expire-all-groups 90 60)
Niklas>   (gnus-demon-add-handler 'gnus-agent-regenerate 90 60)
Niklas>   (gnus-demon-add-handler 'gnus-agent-fetch-session 90 60)
Niklas>   (gnus-demon-add-handler 'gnus-demon-scan-mail 90 60)

Niklas> Then I can read properly sorted emails on the IMAP server
Niklas> from any client.

Niklas> Maybe this could work for you too?

Ahh, this is starting to sound more and more probable, since I boot
emacs about once every two months, running "screen emacs".  How tough
is it to migrate from 255 nnml groups back into nnimap?  And
what do I have to set up to do that?

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!



  reply	other threads:[~2003-02-07 15:44 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-05 17:04 Randal L. Schwartz
2003-02-05 21:47 ` Vasily Korytov
2003-02-05 21:49   ` Randal L. Schwartz
2003-02-06  9:30     ` James Leifer
2003-02-06 21:37     ` Kirk Strauser
2003-02-06 15:46 ` Kai Großjohann
2003-02-07  1:27 ` Stainless Steel Rat
2003-02-07  2:04   ` Randal L. Schwartz
2003-02-07  2:24     ` Stainless Steel Rat
2003-02-07  5:41       ` Randal L. Schwartz
2003-02-07 16:28         ` Stainless Steel Rat
2003-02-07 16:39           ` David S Goldberg
2003-02-07 18:14             ` Randal L. Schwartz
2003-02-07 18:49               ` David S Goldberg
2003-02-07 18:13           ` Randal L. Schwartz
2003-02-07 19:38             ` Stainless Steel Rat
2003-02-07 19:53               ` Randal L. Schwartz
2003-02-07 20:06                 ` Stainless Steel Rat
2003-02-07 20:18                   ` Randal L. Schwartz
2003-02-07 23:18                     ` Stainless Steel Rat
2003-02-07 21:45             ` Kai Großjohann
2003-02-07  7:18 ` Michel Schinz
2003-02-07  9:07   ` Niklas Morberg
2003-02-07 15:44     ` Randal L. Schwartz [this message]
2003-02-07 16:34       ` David S Goldberg
2003-02-07 15:52   ` Kai Großjohann
2003-02-14 21:53 ` David Wuertele
2003-02-15  5:50   ` Randal L. Schwartz
2003-02-15  6:02     ` Randal L. Schwartz
2003-03-01  0:32       ` David Wuertele
2003-03-03  8:50         ` Bjørn Mork
2003-03-03 17:27           ` David Wuertele
2003-03-04 12:11             ` Bjørn Mork

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=86smv02iyx.fsf@red.stonehenge.com \
    --to=merlyn@stonehenge.com \
    --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).