From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Foreign server info?
Date: Thu, 01 Jul 2004 14:14:07 +0900 [thread overview]
Message-ID: <b9ysmccjom8.fsf@jpl.org> (raw)
In-Reply-To: <u8zbrj0dcle.fsf@mm117419-pc.MITRE.ORG>
Well, I'm not familiar with nnimap, so I might be unable to help
you. Here's only a generic information.
>>>>> In <u8zbrj0dcle.fsf@mm117419-pc.MITRE.ORG>
>>>>> David S Goldberg <david.goldberg6@verizon.net> wrote:
> Where is it stored? I created a foreign server to test a new IMAP
> server at work. Everything works fine, but they're changing some of
> the host information so I want to edit the server to fix the address.
> I enter the server buffer and type 'e' over the appropriate line. I
> get an error that I can't edit the server.
If you create a new server by copying of it using the `c'
command, you will be able to edit it. It is stored in the
gnus-server-alist variable and saved in the .newsrc.eld file.
> OK, fine, be that way, I
> thought. I'll just quit Gnus and edit .newsrc.eld by hand. But I
> don't see it defined there, nor do I see it defined anywhere else.
> M-x apropos gnus didn't turn up anything obvious either.
The server made using the B command in the Group buffer is
stored in gnus-opened-servers, but not in gnus-server-alist.
Only gnus-server-alist is stored in the .newsrc.eld file. Even
so, the "nnimap+server:group" entry in gnus-newsrc-alist should
have the server information. However, if you kill the group,
the server information will be lost eternally.
Otherwise, you can also specify a foreign server in the
gnus-secondary-select-methods variable (see the IMAP section in
the Gnus info manual). You can edit it as you like, although it
cannot be edited in the Server buffer.
--
Katsumi Yamaoka <yamaoka@jpl.org>
next prev parent reply other threads:[~2004-07-01 5:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 20:18 David S Goldberg
2004-07-01 5:14 ` Katsumi Yamaoka [this message]
2004-07-01 13:22 ` David S Goldberg
2004-07-14 14:22 ` David S Goldberg
2004-07-01 14:38 ` Mark Plaksin
2004-07-01 23:38 ` Katsumi Yamaoka
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=b9ysmccjom8.fsf@jpl.org \
--to=yamaoka@jpl.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).