Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: must server be loaded to use Gcc ?
Date: Wed, 27 Mar 2002 22:19:23 +0100	[thread overview]
Message-ID: <vafadstpv38.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3eli52692.fsf@multivac.cwru.edu>

prj@po.cwru.edu (Paul Jarc) writes:

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) wrote:
>> prj@po.cwru.edu (Paul Jarc) writes:
>>> 5. Review your whole .newsrc.eld, making similar changes.
>>
>> I think the problem is that .newsrc.eld lists the server as nil for
>> groups coming from gnus-select-method.  But how to find the right
>> occurrences of nil that should be replaced with "nntp:foo"?
>
> That's what the [G e] step was supposed to handle.  Doesn't it?

Ah!  Right.  Sorry for missing this one.

>> And how to find all groups which come from the native server?  One
>> must look for a list where the first element is a string which does
>> not contain the ":" character.  Whee...
>
> Right.  Fixing the top-level group names in gnus-newsrc-alist would be
> easy enough programmatically, but there could be other instance of
> group names - e.g., in group parameters somewhere.

After the previous step this might not be necessary anymore.  Hm.
Along with `G e', one could also change the group name.  Is `G E'
necessary for that or is there another way?

This `G e' thing could even be put in a kbd macro, so it would be
feasible to make it mostly automatic.  Cool.

I think I want to do this migration.

kai
-- 
Silence is foo!


       reply	other threads:[~2002-03-27 21:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87hen3139k.fsf@nomad.consult-meyers.com>
     [not found] ` <m38z8f57mj.fsf@multivac.cwru.edu>
     [not found]   ` <87sn6mph26.fsf@landhaus.consult-meyers.com>
     [not found]     ` <m3it7i2bu5.fsf@multivac.cwru.edu>
     [not found]       ` <vaf663hex2t.fsf@lucy.cs.uni-dortmund.de>
     [not found]         ` <m3eli52692.fsf@multivac.cwru.edu>
2002-03-27 21:19           ` Kai Großjohann [this message]
2002-03-27 22:31             ` Paul Jarc
2002-03-28  0:54           ` Micha Wiedenmann
2002-03-28  0:05             ` Paul Jarc
     [not found]             ` <vaf7knx136p.fsf@lucy.cs.uni-dortmund.de>
     [not found]               ` <87d6xo29yp.fsf@landhaus.consult-meyers.com>
     [not found]                 ` <vafy9gcy3ou.fsf@lucy.cs.uni-dortmund.de>
     [not found]                   ` <m3it7gpne1.fsf@multivac.cwru.edu>
     [not found]                     ` <slrnaa72nl.j2.nospam.look@nomad.consult-meyers.com>
     [not found]                       ` <m3k7rwnvws.fsf@multivac.cwru.edu>
2002-03-29  9:00                         ` A. L. Meyers
     [not found]                           ` <vafu1qzvaq0.fsf@lucy.cs.uni-dortmund.de>
2002-03-29 15:19                             ` A. L. Meyers
     [not found]                       ` <vaf3cyjwpf9.fsf@lucy.cs.uni-dortmund.de>
     [not found]                         ` <87adsrs915.fsf@nomad.consult-meyers.com>
     [not found]                           ` <vafzo0rxfi2.fsf@lucy.cs.uni-dortmund.de>
     [not found]                             ` <87elhvzixw.fsf@landhaus.consult-meyers.com>
2002-04-04 17:09                               ` Paul Jarc
     [not found]                                 ` <k8z1yduof6u.fsf@alcatel.de>
2002-04-05  8:23                                   ` A. L. Meyers

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=vafadstpv38.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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).