From: Ken McGlothlen <mcglk@itchy.serv.net>
Subject: Ugh! Ack! Argh! Nggh!
Date: Sat, 17 Jul 1999 00:02:30 -0700 (PDT) [thread overview]
Message-ID: <Pine.BSF.4.02.9907162346310.73240-100000@itchy.serv.net> (raw)
In-Reply-To: <vnd1ze8aq2j.fsf@betelgeuse.ccs.neu.edu>
Gnus has really scared me a few times.
Tonight, for example. I've spent the last four days moving 140MB of old mail
from VM to Gnus nnml folders, writing procmail recipes, and so forth. I still
haven't transferred my email delivery to the new system (I have over 3000
messages piled up waiting for Gnus to start running smoothly). And tonight, I
get home to convert the last bit of mail, start up Gnus, and get
Wrong type argument, integerp
Heart attack. Complete heart attack.
Yet, the second time I tried it (identical circumstances---both times, I'd
started Emacs afresh), it worked fine.
But I'm a bit shaky now.
Here's another thing that concerned me. I was dealing with some messages in my
"main" mailbox that I hadn't yet written a procmail recipe for. I got to a
message, hit B m and moved it to a nnml folder that didn't exist. Sure enough,
Gnus asked me if I wanted to create it, I said "yes", and the message got moved
and marked "G".
So where's the group? Ain't there. I even left Emacs and restarted from the
ground up, and it's not there. And yet, it's in the ~/Mail directory; just not
in the .newsrc.eld file. Why not? And what happens if I create it now? Will
it erase the old stuff?
The *promise* is that it's going to get a lot better.
Also, one question: What's a quick way to take an nnml folder and convert it
to an mbox-compliant file so that I can reprocess it with procmail? Or even a
slow way?
Whee! The adventure continues.
next prev parent reply other threads:[~1999-07-17 7:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-15 17:59 Gnus and NoCeM Ken McGlothlen
1999-07-15 19:05 ` Colin Rafferty
1999-07-15 19:32 ` Ken McGlothlen
1999-07-15 20:27 ` Colin Rafferty
1999-07-15 21:51 ` Ken McGlothlen
1999-07-15 22:58 ` David Hedbor
1999-07-16 0:15 ` Dan Christensen
1999-07-17 3:54 ` Justin Sheehy
1999-07-17 7:02 ` Ken McGlothlen [this message]
[not found] ` <wtnu2r3bslp.fsf@licia.dtek.chalmers.se>
1999-07-17 10:15 ` Ugh! Ack! Argh! Nggh! Hans de Graaff
1999-07-17 16:05 ` Michael Cook
1999-07-17 10:17 ` Kjetil Ødegaard
1999-07-17 11:02 ` Kai Großjohann
1999-07-17 12:21 ` Harry Putnam
1999-07-17 11:14 ` Kai Großjohann
1999-07-18 7:10 ` Ken McGlothlen
1999-07-19 10:50 ` Kai Großjohann
1999-07-27 15:37 ` Jack Vinson
1999-07-26 17:14 ` Hrvoje Niksic
1999-07-26 17:45 ` Paul Stevenson
1999-07-26 17:50 ` Paul Stevenson
1999-07-26 19:13 ` François Pinard
1999-07-28 12:15 ` Robert Bihlmeyer
1999-07-28 14:38 ` Paul Stevenson
1999-07-17 10:58 ` Gnus and NoCeM Kai Großjohann
1999-07-19 17:53 ` Sudish Joseph
1999-07-15 20:49 ` Justin Sheehy
1999-07-16 4:50 ` Andrew Hobson
1999-07-16 5:37 ` Ken McGlothlen
1999-07-16 14:02 ` Jack Twilley
1999-07-15 21:32 ` Kai Großjohann
1999-07-16 15:28 ` Wes Hardaker
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=Pine.BSF.4.02.9907162346310.73240-100000@itchy.serv.net \
--to=mcglk@itchy.serv.net \
/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).