From: Bill <wsharris13@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: IMAP problems
Date: Thu, 29 Nov 2007 09:35:20 -0800 (PST) [thread overview]
Message-ID: <cd82386d-7738-4c66-980a-3e4d9d8f5265@i29g2000prf.googlegroups.com> (raw)
In-Reply-To: <16960e98-b1c8-4693-9bf9-fb22691b254c@s8g2000prg.googlegroups.com>
On Nov 29, 9:08 am, Bill <wsharri...@gmail.com> wrote:
> If I can figure out how to point Gnus to my old mail structure, is
> it safe to subscribe to these cygwin structures (G d?) and then move
> or respool the files into my traditional structure?
A bit more reading (the *info* page called General Variables in 22.1
and 21.3.1) showed that Emacs changed the meaning of HOME between the
two versions. In the older one, it seems to default to C:/; in 22.1,
it has a different default. In the *info* page "G.4 HOME Directory on
MS-Windows," it seems to look for a HOME variable first, and that is
already set by cygwin. Since there's no .emacs there, it fails and
moves on without loading a .emacs, I presume (if it hadn't found HOME,
it would have done what I wanted and checked for .emacs in C:/).
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?
Thanks,
Bill
next prev parent reply other threads:[~2007-11-29 17:35 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 [this message]
2007-11-29 22:45 ` Bill
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=cd82386d-7738-4c66-980a-3e4d9d8f5265@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).