Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Bill <wsharris13@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: IMAP problems
Date: Thu, 29 Nov 2007 14:45:58 -0800 (PST)	[thread overview]
Message-ID: <a6235624-a6c6-49f2-ba08-ffa1c801805e@i29g2000prf.googlegroups.com> (raw)
In-Reply-To: <cd82386d-7738-4c66-980a-3e4d9d8f5265@i29g2000prf.googlegroups.com>

On Nov 29, 9:35 am, Bill <wsharri...@gmail.com> wrote:

> Should I give up and move everything into HOME (aka c:/cygwin/home/my
> name/ -- yes, it has a space :-(  ), or is there a way to tell Emacs
> 22.1 that it should look in C:/ even though HOME is defined by cygwin
> as a different location?

Answer: apparently yes.  I renamed the Gnus files v.5.11 had already
put there, copied over the .bbdb, .newsrc.eld, and .nnmail-cache from
C:/ into ~/, and then copied C:/Mail and C:/News into HOME.  When I
fired up Gnus, everything (almost) was there.

Moral of the story (for me, at least):

  1. On Windows, HOME is moved.  Get over it; it's a good idea (or so
it seems).

  2. Read the Emacs NEWS after upgrading; it told me all that.  (It
might have put it in 48 pt. type, though; there were a lot of
changes. :-)

That left one unanswered question: recovering the new email I've
gotten in the last few days. I followed the directions in 6.3.8
Incorporating Old Mail, but it failed.  Perhaps it works only for mbox
files, and my "old" mail is in nnml format.

At any rate, on step 3, Gnus won't let me enter the group, complaining
"No such file or buffer".

After some experimentation, I found that making a directory group (G
d) would let me enter one of the groups I needed to move.

That led to respooling the articles.  I answered nnml as indicated,
but then it wanted a server name.  After a bit of reading, I decided
"What can it hurt if I just press 'Enter'?" It seemed to work; I had
58 messages in the new mail.misc, and 22 of them made it back to the
old mail.misc (presumably the others went to other folders).
Surprisingly, the new mail.misc (the one I was trying to empty) still
had the original 58 articles.  I finally decided to mark each with an
E, to exit the new group, and then to unsubscribe from the new group.
Once I had all the groups respooled, I went back and killed them.

That seemed to work, although there may be an easier way. Sorry for
the long posting, but maybe it will help someone else.  Now that most
of the work is over (except for finding various new elisp packages, I
like what I see in the new version.

Bill

  reply	other threads:[~2007-11-29 22:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-28  5:37 Bill Harris
2007-11-28  6:43 ` Torsten Mueller
2007-11-28 18:54   ` Bill Harris
2007-11-28 21:08     ` Hasse Hagen Johansen
2007-11-28 22:31     ` Reiner Steib
2007-11-29  0:32       ` Bill Harris
2007-11-29 16:39         ` Bill
2007-11-29 17:08           ` Bill
2007-11-29 17:35             ` Bill
2007-11-29 22:45               ` Bill [this message]
2007-11-30 15:44                 ` Bill Harris
2007-11-30 16:02                 ` Bill Harris
2007-11-30 21:22           ` Reiner Steib
2007-12-02  3:26             ` Bill Harris
  -- strict thread matches above, loose matches on Subject: below --
2002-11-22 12:09 imap problems Kester Clegg
2002-11-22 15:03 ` Dan Smith

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=a6235624-a6c6-49f2-ba08-ffa1c801805e@i29g2000prf.googlegroups.com \
    --to=wsharris13@gmail.com \
    --cc=info-gnus-english@gnu.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).